Conversation
You tell me the problem and who has it. I tell you honestly whether an app solves it, and what it would take.
Most app developers can write the code. Far fewer can tell you whether the app should exist, who will actually open it on a Tuesday night, and what will make them come back.
I am an Industrial and Organizational Psychologist who builds software. That means the behavioural question gets answered before the technical one, which is usually the difference between an app that ships and an app that gets used.
We start with the problem, not the feature list. If an app is the wrong answer, I will say so before you spend anything.
I am an I/O psychologist. Screens are designed around how people actually behave under time pressure, not how a designer imagines they behave.
One codebase, native performance, offline-first where it matters. Clean architecture you or another developer can pick up later.
Typography, colour and spacing with rules, so the app looks considered rather than assembled from a template.
Data safety declarations, privacy policy, target-audience settings, signing keys and developer verification. The paperwork that gets apps rejected.
Store screenshots, description, keywords and release notes written to convert, not to fill a field.
Not client work described in vague terms. These are live on Google Play under my own developer account, which means I have been through every part of the process that goes wrong: signing keys, data safety declarations, target audience rules, policy rejections, store listings and updates.
You get a test build at each milestone, not a surprise at the end.
You tell me the problem and who has it. I tell you honestly whether an app solves it, and what it would take.
Screen flow, design system and a clickable direction you approve before a line of code is written.
Built in Flutter, in stages you can see. You get a test APK at each milestone, not a surprise at the end.
Signing, Play Console setup, data safety, screenshots, listing copy, and submission.
Updates, review responses, and the fixes that only real users find.
Cost, time, the Play Store, code ownership and iOS.
It depends entirely on scope, and anyone who quotes before understanding the scope is guessing. A focused single-purpose app is a very different project from one with accounts, payments and a backend. Tell me what the app has to do and I will give you a real number and a real timeline, free of charge.
A well-scoped first version is typically a few weeks, not months, because I build in stages you can see. You get a working test build early and often, so nothing is a surprise at the end.
Yes, all of it. Signing keys, data safety form, privacy policy page, target audience, content rating, screenshots, description and release notes. Most first-time rejections come from that paperwork rather than from the app itself.
Yes. You get the full source and the signing keys. Losing a signing key means never being able to update your own app, so I hand it over properly and show you how to back it up.
The apps are built in Flutter, which means one codebase can produce both. I currently ship Android, and an iOS build is possible as a separate stage with its own App Store process.
Then I will tell you in the first conversation, and it costs you nothing. I would rather lose a project than take money for an app nobody opens.
Everything on this site can be checked before you pay for anything. A free tool runs fourteen measurable checks on any public page in about thirty seconds, and 47 full brand psychology audits are published here in full, no email required.
Tell me the problem, who has it, and what they do about it today. That is enough for me to tell you whether an app is the right answer, what it would take, and what it would cost.
Your cart is empty
Browse Shop