I build mobile apps in Flutter, one Dart codebase for Android and iOS, together with the server they depend on. That covers sign-in, payments, chat, calls, push notifications, offline storage and the store submissions at the end.
Apps I have built or rebuilt and released include Estasher, an Arabic-first marketplace for engineering consultations in Saudi Arabia that I took over and rebuilt and that is live on the App Store and Google Play, Asaan Optics for optical shops on Google Play, and GeoPrints, a private travel journal on Google Play that keeps all of its data on the phone. I was also the main developer of the Flutter app for KAYANAK's customers and marketers.
One Flutter project that produces native builds for both stores, so every change ships to both platforms.
A server for identity, payments, files and push notifications, or integration with your existing API. For Estasher I wrote a new PHP and MySQL API that the app now runs on.
Local databases such as SQLite, Isar and Hive, plus sync queues, so the app keeps working on a weak connection.
In-app chat with voice notes and file sharing, and voice and video calls with native ringing on Android, as built for Estasher.
Arabic-first layouts, Arabic fonts and right-to-left support, with light and dark themes.
Camera, barcode and QR scanning, on-device text recognition, location, local notifications and home-screen widgets.
App Store and Google Play listings, automated builds, in-app account deletion and the privacy details the stores review.
I keep trust on the server. The phone handles the interface and local data, while the server owns identity, money and anything that has to be verified. On Estasher the app writes bookings under strict database rules, and only the server API can mark an order paid or a commission settled.
I design for the connection the user actually has. Asaan Optics queues every write with an idempotency key, so sales made offline sync later without duplicates. GeoPrints has no server at all: its location timeline lives in an on-device Isar database and leaves the phone only when the user exports it.
Release work is part of the job. I set up automated builds with GitHub Actions and fastlane, so Estasher's iOS builds reach TestFlight without a manual step, and I handle store listings, permissions and account deletion so reviews go smoothly.
Who uses the app, the main journeys for each role and what the first store release must include.
What lives on the phone, what lives on the server, and how sign-in, payments and notifications work.
Screens built on a shared design system, tested on real Android and iOS devices as features arrive.
Listings, screenshots, privacy details, permissions and test builds through TestFlight and Google Play testing tracks.
Submission under your developer accounts, then regular updates based on feedback and crash reports.
Engineering consultation marketplace app
A bilingual iOS and Android marketplace where clients in Saudi Arabia book consultations and request offers from verified engineers and engineering offices.
Optical shop management SaaS
Optical shop software for Android and Windows: prescriptions, counter sales, stock and staff shifts on one shared shop account.
Private location journal for Android
An Android travel diary that automatically logs your stays, routes and photos, with all location history kept on your phone.
Yes. Flutter is Farhad's main tool for mobile apps. His Flutter work includes Estasher, live on the App Store and Google Play, Asaan Optics on Google Play, and GeoPrints, a privacy-first travel journal for Android.
Yes, from one Flutter codebase. Estasher is published on both the App Store and Google Play, and its iOS builds are sent to TestFlight automatically from CI.
Yes. Estasher is Arabic-first, with Arabic and English, an Arabic typeface and light and dark themes. Asaan Optics ships in nine languages including Arabic, and Arab Expat, an app still in development, supports English, Arabic and Urdu with right-to-left layouts.
Usually, yes. Most apps need a server for sign-in, payments, files and notifications. I have written app backends in PHP, Laravel and Node.js, and I can also connect the app to an API you already have.
Yes. I took over Estasher in October 2026, replaced its backend, rebuilt the core features and redesigned the app before the client's launch date. I start with a review of the code, accounts and infrastructure so we know what to keep and what to replace.
Yes. I prepare the listings, permissions, privacy details and account deletion, then submit to Google Play and the App Store under your developer accounts. Review times are set by Apple and Google, so I plan releases around them.
Tell me what you are trying to fix. I will reply with honest questions, a practical plan and a realistic estimate.
