Android

Hosanna supports Android mobile as a native target. Shared Hosanna code provides screens, state, styling, fragments, networking, and business logic while the Android project manages packaging, platform services, lifecycle, and Play Store delivery.

Development Flow

1. Develop shared screens and data flows in Web.
2. Run native Android with npx hst run android dev sim --device "<emulator name>".
3. Run emulator checks for layout, touch, text input, and navigation.
4. Validate on physical Android phones and tablets.
5. Build release artifacts through the Android toolchain.

Runtime Notes

• Touch, keyboard, and system navigation should be normalized before shared views receive input.
• Native Android uses the Android native target, not the legacy Capacitor WebView shell.
• Use npx hst run android dev device --device "<adb serial or device name>" for real-device checks.
• Platform services should live behind adapters so shared code stays portable.
• Use AppConfig fragments and styles as the default source for UI behavior.
• Keep Android-specific layout or lifecycle fixes isolated to the Android target.

Release Checklist

• Confirm package id, signing, version codes, permissions, and Play Store metadata.
• Test orientation, safe areas, keyboard entry, lifecycle resume, networking, and low-memory behavior.
• Validate image and font assets across screen densities.