[android] Kotlinize DI (#14039)

[android] Kotlinize storage (#14018)

[android] Kotlinize ReactNativeActivity and ExperienceActivity (#13870)

[android] Kotlinize kernel (#13685)

[android] lint spotless ktlint and fix CI step (#13662)

[android] Add kotlin spotless ktlint linter (#12545)

[Android] Switch to Android SDK 30 & update gradle (#11647)

# Why

We want to switch to Android SDK 30.

# How

- [x] I've bumped `targetSdkVersion` to `30`
- [x] I've bumped `compileSdkVersi

[Android] Switch to Android SDK 30 & update gradle (#11647)

# Why

We want to switch to Android SDK 30.

# How

- [x] I've bumped `targetSdkVersion` to `30`
- [x] I've bumped `compileSdkVersion` to `30`
- [x] I've fixed nullability issues coming from

# Test Plan

- [x] compiled & run Expo Go on Android SDK 30 simulator
- [x] compiled & run `bare-expo` on Android SDK 30 simulator
- [x] launched `ncl` in Expo Go and played for a while

# CHANGES

- [Android] Update gradle to 6.8 & gradlePlugin to 4.1.1
- [Android] Bump targerSdkVersion and compileSdkVersion to 30
- [Android] Bump kotlin plugin version to 1.4.21
- [Android] Fix & unify ANDROID_NDK_HOME path detection
- [react-native][Android][submodule update] Rename ANDROID_NDK to ANDROID_NDK_HOME

show more ...

[splash-screen][client] Add expo-splash-screen to ExpoClient (#9622)

[android] When Consants.DISABLE_NUX is set then skip the onboarding experience (#8954)

[ios][android][devmenu] Dismiss keyboard when opening dev menu (#7806)

# Why

Fixes #7613

# How

- **Android**: Cleared the focus in the current activity, this automatically dismisses the ke

[ios][android][devmenu] Dismiss keyboard when opening dev menu (#7806)

# Why

Fixes #7613

# How

- **Android**: Cleared the focus in the current activity, this automatically dismisses the keyboard.
- **iOS**: There is no easy way to get the view that is the first responder, so I just made the dev menu view be the first responder, so the other view will lost its focus and the keyboard will be dismissed.

# Test Plan

Tested by opening NCL on the example with text input, pressed on the text input to give him a focus (keyboard shows up) and then shaked the device to open dev menu.
Result: keyboard has been dismissed, dev menu has shown up.

show more ...

[android] Fix issue with setting style props when we try to show onboarding view (#7294)

# Why

Fixes errors and sometimes even crashes when we try to show dev menu for onboarding (it's the only c

[android] Fix issue with setting style props when we try to show onboarding view (#7294)

# Why

Fixes errors and sometimes even crashes when we try to show dev menu for onboarding (it's the only case when we show the dev menu right after the app is loaded and it's still rendering its content).

# How

Added 2s delay when showing up the dev menu if onboarding is needed - it's kind of hacky workaround, but imho it's good from UX perspective since the user can see his app for a while and then he sees how the dev menu appears - which focuses him on the dev menu.
Slightly refactored some code to have just one place where we try to show dev menu for onboarding.

# Test Plan

- Cleared Expo client app cache.
- Opened Expo client and then any experience.
- The dev menu appeared after a while without errors or crashes.

show more ...

[android][home] �� Add DevMenu on Android (#6829)

# Why

Fixes #6521

# How

- Created unversioned `DevMenuManager` class which mostly just delegates calls to versioned `DevMenuModule` module

[android][home] �� Add DevMenu on Android (#6829)

# Why

Fixes #6521

# How

- Created unversioned `DevMenuManager` class which mostly just delegates calls to versioned `DevMenuModule` modules specific for SDK version. These modules are responsible for providing initial props, dev menu options and actions to run when these options are selected. The manager creates a new `ReactRootView` that bases on kernel's (home's) React instance manager and starts `HomeMenu` app which is registered as a second entry point in `home` and then, manager adds this root view to the currently used activity (it must implement `ExperienceActivity`). As I needed to know which experience activity is the current one, I've added `sCurrentActivity` static member to that class and just track it using activity's lifecycle methods.
- Backported `DevMenuModule` to all SDK versions included in the client. Including some changes between them - for example hot and fast reloading.
- Added support for back button and Android's menu press (which can be simulated by `adb shell input keyevent 82`).
- Removed some unused code related to `Nux` and replaced it with new onboarding screen (see #6793).
- Created new `ShakeDetector` which works more like on iOS. The one provided by React Native is annoying in most cases as it actually requires two shakes.
- Updated `ReactAndroidCodeTransformer` to turn off showing React Native dev menu in non-standalone apps.
- **To do after merging:** Rebuild versioned expoviews.

# Test Plan

- [x] Test on experience in debug mode
- [x] Test on experience in production mode
- [x] Test on snacks
- [x] Test on older SDKs
- [x] Test on simulators
- [x] Test that onboarding shows up once you open the experience for the first time or you didn't accept it yet (clicked `Got it` button).
- [x] Test that using dev menu still works once we kill home's activity.

show more ...