Thinko
Brain training, 60 seconds at a time
Google Play moves its requirements every year — target SDK levels, billing library versions, data safety declarations. Keeping up with that is part of the job, not an extra.
Not a portfolio of client logos — our own products, live, with the numbers they actually have today.
Brain training, 60 seconds at a time
Who owes what, finally clear
The second list is the useful one. Finding out on the first call that this isn't the right job costs both of us ten minutes; finding out three weeks in costs a great deal more.
Usually yes, and usually faster than expected. The recurring ones are the target SDK level, an outdated billing library and a missing data safety declaration — all mechanical once someone sits down with the Console.
With one Flutter codebase the question mostly goes away — the marginal cost of the second platform is small. If budget forces a choice, it follows where your users are, not where the tooling is easier.
Yes, in full, on completion — source, assets, and the accounts they run on. There is no licence to keep paying and nothing held back to lock you in. If you later take it to another developer, everything they need goes with it.
The people writing the code. There are no account managers and no relay chain, which is why answers come back in hours rather than at the next sprint boundary.
Tell us what you're making. We reply within 24 hours — a real answer from the people who'd build it, not a sales sequence.