New app, from blank repository
An idea, a spreadsheet or a Figma file turned into a signed, installable Android build.
- Architecture and data model
- Compose UI against your brand
- Signed release bundle
- Store listing prepared with you
Remote-first studio, working with teams across Europe
We build Android apps, put them on the store, and stay on the pager after launch.
GENEX TECH does one thing: Android. We write the app, we prepare the release, we publish it, and we keep it working on the phones people actually carry — not just the flagship on the engineer's desk.
That narrowness is the point. An Android app is not a screenshot; it is a build that has to survive a four-year-old mid-range handset with 9% battery, a background process the system is keen to kill, a locale that writes dates backwards, and a store review queue that does not care about your launch date. Teams that treat Android as a port of something else discover all of this in the week they planned to celebrate.
So we start from the constraints. Install size has a budget. Cold start has a budget. Every permission the app asks for has to justify itself in a sentence a reviewer will accept. We build in two-week slices you can hold in your hand, on a real device, before anything is final — because a decision made against a running build is a decision you only make once.
One codebase, written the way the platform expects: Compose UI, coroutines, Room or DataStore for local state. No wrapper around a website pretending to be an app.
The app opens on the underground and on a dying signal. Local cache, queued writes, conflict rules we agree with you in advance instead of a spinner and an apology.
Signing keys, app bundles, staged rollouts, store listing text and screenshots, data-safety declarations, and the rewrite when a submission comes back rejected.
Monitoring wired in before launch, not after the first bad review. We read the stack traces, reproduce on the device model that threw them, and ship the fix.
Push notifications, feature flags, remote config, subscriptions and analytics — added only where they change a number, and gated behind the consent the user gave.
Old Java views, an abandoned repository, a build nobody can run. We get it compiling, document it, and update it without stopping the version that is live.
Four shapes of work. Scope is agreed in writing before anything is built.
An idea, a spreadsheet or a Figma file turned into a signed, installable Android build.
For an app that still works but nobody dares touch.
You have the build; you want it live and surviving review.
The app is live and needs to stay that way through every OS release.
Every engagement is quoted after a scoping conversation — we do not publish a rate card for work we have not scoped.
What the work looks like between the brief and the release.
One message is enough. Who uses it, what they do in it, and what already exists — code, designs, a back end, or nothing at all.
We ask the awkward questions early: offline behaviour, logins, payments, which Android versions you are willing to drop. You get a scope, a sequence and a range in writing.
At the end of each slice there is an installable build on your own phone, a short note on what changed, and a decision point. Nothing is saved up for a big reveal.
Signed bundle, listing, staged rollout, monitoring switched on. Then the quieter half: crash fixes, OS updates, and the changes the first thousand users ask for.
When the work ends, you should be able to walk away from us without losing anything. That is a deliberate part of how we hand over.
We are happy to stay on a care plan afterwards, and most clients do — Android moves every year, and target-SDK deadlines arrive whether or not anyone is watching. But staying should be a choice you make each renewal, not a lock-in you discover when you try to leave. If you ever hire someone else, the handover takes an afternoon.
Two lines about what it has to do is plenty to start — we will ask the rest.
Thanks — someone from the team will get in touch shortly with a few scoping questions.
This site uses cookies for analytics and advertising measurement, but only after you give your consent. Learn More