What we deliver
Twara Technologies designs and engineers native Android applications for consumers, customers and staff. We build new apps from scratch, modernise existing ones, and create specialised operational apps for field teams, warehouses, retail floors and managed devices.
Android runs on a very wide range of hardware, from flagship phones to budget handsets and rugged scanners. Building well for Android means designing for that diversity from the outset: adaptable layouts, careful memory and battery use, and testing on the devices your users actually own.
Typical scope
- Discovery: users, journeys, device profile of your audience and the features that justify a native app.
- UX and UI design based on Material Design, with an interactive prototype.
- App architecture, data layer and offline strategy.
- Back-end integration, or a new API built by our mobile backend team.
- Platform features: notifications, deep links, background work, camera and barcode scanning, location, Bluetooth, NFC and payments.
- Testing across devices, Play Console set-up and release management.
- Ongoing updates as Android and Play requirements change.
Technologies we work with
| Area | Options | When we tend to choose each |
|---|---|---|
| Language | Kotlin, Java | Kotlin for all new work; Java when maintaining existing modules. |
| UI | Jetpack Compose, Android View system | Compose for new apps and screens; Views where an existing app or library depends on them. |
| Architecture | Jetpack ViewModel, Navigation, Hilt, Kotlin coroutines and Flow | A well-documented, widely understood structure that other teams can pick up. |
| Data | Room, DataStore, WorkManager | Local database, preferences and reliable background sync. |
| Networking | Retrofit, OkHttp, Ktor client | Mature REST clients; Ktor where code is shared with Kotlin Multiplatform. |
| Back-end services | Firebase, Supabase, AWS Amplify or a custom API | Managed services for quick starts; custom APIs for complex integrations. |
| Testing and delivery | JUnit, Espresso, Compose testing, Firebase Test Lab, Gradle, GitHub Actions, Fastlane | Automated tests and repeatable signed builds. |
| Monitoring | Firebase Crashlytics, Sentry | Crash and performance reporting after release. |
Google has described Android development as Kotlin-first since Google I/O 2019, with new Jetpack libraries, samples and documentation designed with Kotlin in mind, and calls Jetpack Compose Android’s recommended modern toolkit for building native UI. Our defaults follow that direction.
How we approach it
- Discover. Goals, users, devices and constraints, and confirmation that native Android is the right approach.
- Design. Flows and prototypes informed by Material Design, tested with representative users.
- Architect. Modules, data layer, offline strategy, permissions and API contracts.
- Build in increments. Regular builds on internal testing tracks so you can use the app throughout development.
- Test. Automated tests, a device matrix covering screen sizes, Android versions and manufacturers, plus accessibility and security testing.
- Release. Play Console set-up, staged rollout and monitoring; see App Store launch and optimisation.
- Support. Updates for new Android versions and Play policy changes.
Quality, security and performance
- Target API level. Google Play sets target API level requirements for new apps and updates. At the time of writing, new phone and tablet apps and app updates must target Android 16 (API level 36) or higher (deadline 31 August 2026, extendable on request to 1 November 2026), and existing apps must target Android 15 (API level 35) or higher to remain available to new users. These requirements move forward over time, so we plan for them in every maintenance cycle.
- App format. Since August 2021, new apps on Google Play have been required to publish as Android App Bundles. Our release pipelines produce signed bundles by default.
- Data safety. Every developer with an app published on Google Play must complete the Data safety form, which feeds a section of the store listing. We inventory the app’s data flows and third-party SDKs so that the form is accurate.
- Mobile security. We test against the OWASP MASVS, covering storage, cryptography, authentication, network, platform interaction, code quality, resilience and privacy.
- Personal data. Where the Digital Personal Data Protection Act, 2023 applies, a request for consent must be accompanied or preceded by a notice. We design permission prompts and consent screens to work together clearly. These provisions are being brought into force in phases; our DPDP guide tracks the dates.
- Performance. Profiling with Android Studio tools for start-up time, memory, jank and battery, with attention to lower-end devices.
- Accessibility. TalkBack support, scalable text, contrast and touch target sizing, tested on device.
Engagement options
- Fixed-scope first release. A defined version 1.0 delivered to Google Play or your managed devices.
- Time and materials product development. Ongoing feature development against a prioritised roadmap.
- Ongoing support. Android and Play compliance updates, monitoring and enhancements through our support and maintenance service.
Share your app idea or existing codebase and we will recommend the right route to Android users.