
A few months ago I kept ending weeks feeling like I'd worked hard but had nothing to show for it financially. I knew my hourly rate. I knew roughly how many hours I'd worked. But the math never added up clearly in my head.
Then I did it manually one day — wrote down my rate, the hours I actually logged, and the hours I should have logged. The "missed" column hit different. Not in a motivational poster way. In a "oh, I left $340 on the table last Tuesday specifically" way.
That number — the missed income — is what most freelancers never see. They feel it at the end of the month when revenue is low, but they can't trace it to actual days.
So I built Billd. An Android app that shows you two numbers every day: what you earned, and what you missed.
The build itself was a bit chaotic. I'd never touched Flutter before. The entire app is one file (lib/main.dart — yes, I know). Local storage only via SharedPreferences. Daily notification at 6PM asking if you've logged. No backend, no accounts, nothing to sign up for.
I built it in 15-30 minute slots around work. Tested it on my own Realme Android 15 device. It does exactly one thing and I think that's the point.
It's sitting in closed testing on Google Play right now. Before I can apply for production, I need 12 people to test it for 14 days.
If you freelance and have an Android phone, I'd genuinely appreciate you trying it. The beta signup takes 30 seconds — I just need your Gmail to add you to the Play Store test group:
https://forms.gle/5KeUW3XF5HYeHxq7A
Happy to answer anything about the build — the Flutter learning curve, the single-file decision, the notification setup, whatever. And if you've shipped something similar or have thoughts on the "missed income" concept, I'm all ears.
Update: Beta is live on Google Play.
If you freelance on Android, you can join directly here — no form needed anymore:
https://play.google.com/apps/testing/build.gradle.kts
Just click "Become a tester" and install. Takes 60 seconds.
For Android beta testers, I’d make the ask scenario-based instead of install-based. With Kinetic Override, a useful tester would run one exact flow: grant Accessibility permission, record a tap/swipe macro, replay it twice, then say where trust or timing felt confusing. That gives much better signal than a generic “try my app”.
Congrats on building this especially coming from zero Flutter experience, that’s impressive. I’m an app tester and I specialize in beta testing early-stage apps, focusing on usability, onboarding flow, and bug detection. I’d be interested in joining as a tester and providing structured feedback if you’re still onboarding users
Appreciate that! The zero-experience curve was steep but getting it running on a physical Android 15 device made it worth it. I'm definitely still onboarding testers to hit that Google 14-day requirement. If you fill out the quick Google Form in the post with your Gmail, I'll add you to the Play Console closed testing track right now. Would love your structured feedback on the earned vs missed UI.
Great, I’ll fill out the form and join the testing track. I’ll focus on structured feedback around the earned vs missed UI, onboarding flow, and overall usability. Looking forward to trying it out