SERVICE
App development. From idea to ongoing operation.
We build apps for iPhone and Android, including the server, the website and, where it makes sense, AI features. We don't stop at launch: we run our own apps, LottoRead and FlirtPro, ourselves, with updates, store handling and support. That experience goes into your project.
Who it's for
Businesses with a clear use case
a tool for customers or staff that works better on a phone than on paper or in a browser.
Processes that start with a photo or a form
capturing documents, receipts or data, checking them and passing them on.
Founders with a product idea
you want a first version (MVP) in the stores and to learn from real users.
Existing products that need an AI feature
suggesting text or reading images, with a person reviewing the result.
WHAT WE BUILD
Apps, server and AI.
Where they help.
iPhone and Android apps
native (Swift for iOS, Kotlin for Android) as with LottoRead, or from a shared codebase (Flutter) as with FlirtPro. We decide which fits during the concept phase.
Server and web
the backend for data, accounts and background jobs (TypeScript in our own apps) and the website for the app. For web applications with ordering and an admin area, see the Genusseck reference.
AI features where they help
Reading images and documents: LottoRead reads numbers, symbols and fine print from a photo and asks for a clearer one if it is blurred. Suggestions under human control: FlirtPro turns text or a screenshot into reply suggestions; only what the person picks gets sent. Practice and dialogue features: FlirtPro role-plays conversations in practice mode and gives feedback afterwards.
Background processes
for example automatically checking stored data against new information and sending alerts, as in LottoRead.
Accounts, subscriptions and privacy
account management with in-app deletion of account and data, in-app subscriptions via Apple and Google with restore and cancel through the store account, as in FlirtPro.
Store handling
submission to the App Store and Google Play, store texts and screenshots agreed with you, ongoing updates.
HOW A PROJECT RUNS
Agree first.
Then build.
First conversation: you describe the idea, the audience and existing systems. We tell you honestly whether an app is the right path, or whether a website or an existing tool will do.
Concept and scope: we put features, screens, data, platforms and operation in writing, together with timeframe and price. Work starts only after that.
Build in stages: you get regular test builds on your own device (TestFlight or Google Play internal testing) and give feedback.
Store submission and launch: we prepare the submission and see it through Apple's and Google's review. Your app is published under your own developer account – the app and its store listing belong to you.
Operation and further development (optional): updates for new OS versions, bug fixes, server operation and new features, agreed separately.
Typical scope
(example).
A first version (MVP) for iPhone and Android from one codebase, with:
- sign-in and account, including in-app deletion of account and data
- one core feature, for example: take a photo → AI reads the details → show the result for review and save it
- a history or list view and notifications
- a lean server backend and a simple website for the app with a privacy policy (you supply the legal text)
- submission to both stores
Timeframe: A first MVP often takes 4–8 weeks; larger apps take longer accordingly. We agree the exact timeline in the first conversation.
Price: on request. After the concept conversation you receive a written quote with a fixed scope.
References
LottoRead
An app of our own for iPhone and Android. It reads lottery tickets and scratch cards with AI and checks saved tickets against new draws. Native apps (Swift, Kotlin), TypeScript server, website lottoread.com. On the App Store since 2021.
Built and run by Amin M. Tehrani, owner of AMIFA.
View referenceFlirtPro
An app of our own for iPhone and Android: a chat message or screenshot becomes reply suggestions, and the person sends their own message. One codebase (Flutter), TypeScript server and website, in-app subscriptions through the stores, practice mode. On the App Store since 2024.
Built and run by Amin M. Tehrani, owner of AMIFA.
View referenceWhat's not included
and honest limits.
No promise of store approval
Apple and Google decide. We prepare the submission carefully and respond to their questions.
No promises about downloads, ratings or revenue
We commit to the agreed work, not to market success.
Running costs are yours
Apple and Google developer accounts, servers, AI usage and store fees are in your name.
Marketing and app store optimisation
are not included.
Legal texts
you are responsible for the privacy policy and terms; we supply the technical details.
AI can be wrong
so we build in checks, such as asking again for a blurred photo, or a suggestion a person approves.
Existing apps
we take them over only after reviewing the code and infrastructure.
FAQ
Native, or one codebase for both platforms?
We use both: LottoRead is built natively for iOS and Android, FlirtPro from a shared codebase. Which suits your project depends on features, budget and future development; we settle it in the concept phase.
Who owns the app, the code and the store listing?
You do. Your app is published under your own developer account – the app and its store listing belong to you. Code rights and handover are set out in writing in the quote.
Can you add an AI feature to an existing app?
Often, yes. After reviewing the code and systems, we tell you whether and how it makes sense. For a single workflow, the AI Workflow Assessment can be the right starting point.
How much does an app cost?
It depends on the scope, which is why there is no package price. After the concept conversation you receive a written quote with a fixed scope.
What happens after launch?
Apps need care: new OS versions, store requirements, bug fixes. We agree operation and further development separately if you want them, just as we run our own apps on an ongoing basis.
APP PROJECT
Have an
app idea?
Briefly describe what the app should do and who it's for. We'll come back with an honest assessment and the next steps.
Discuss an app project