Skip to content

Services

Mobile apps

Native iOS and Android apps — from first sketch to App Store and Google Play release.

Let's talk about thisAll services

I write native apps: iOS in Swift and SwiftUI, Android in Kotlin and Jetpack Compose. Not generic web wrappers, but apps that behave like part of the phone — instant launch, offline support, camera, sensors and health data, and they pass store review. Healthness is my own product built exactly that way: two platforms, one backend, three languages, subscriptions and AI meal photo analysis.

Technology

  • Swift
  • SwiftUI
  • Kotlin
  • Jetpack Compose
  • Firebase
  • StoreKit 2
  • Play Billing
  • HealthKit
  • CameraX
  • Fastlane
  • XcodeGen

What you get

  • iOS app (Swift, SwiftUI, iOS 17+)
  • Android app (Kotlin, Jetpack Compose, Material 3)
  • One shared backend for both platforms — a single source of truth
  • Submission and shepherding through App Store and Play review
  • Subscriptions and in-app purchases (StoreKit 2, Play Billing)
  • Push notifications, deep links and invitations
  • Offline-first behaviour and sync
  • Multi-language localisation
  • TestFlight and internal testing before public release
  • Automated releases (Fastlane) — a new build in minutes

FAQ

Questions about mobile apps

Question not answered? Ask directly.
How long does it take to build a mobile app?

A tightly scoped first version with sign-in, one main flow and a backend usually reaches a test release in six to ten weeks. An app with subscriptions, a social layer and AI features takes longer. You get the actual schedule after the first call, before you pay anything.

Do you do both iOS and Android?

Yes, both natively. Healthness ships as an iOS and an Android app over the same Firebase backend with tracked feature parity — so I know exactly what keeping two platforms in step costs and how to organise it so it does not double the price.

What if the app gets rejected by the App Store?

That is part of the job, not an extra. I answer the review notes, change what needs changing and resubmit until it passes. Privacy policy, data declarations and purchase descriptions are prepared up front, because they are the most common reason for rejection.

Next service

Web apps & SaaS

Contact

Tell me what you are building — I reply today.

I normally reply the same working day. The first call takes thirty minutes, costs nothing and commits you to nothing.

Request a quoteinfo@faitech.hr