FISCLOK
A personal problem became a public product.
GET IT ON PLAY
01
THE PROBLEM
I started Fisclok for an audience of one: me. I wanted to manage my own financial health better, with a simple way to track my income and expenses.
02
THE IDEA
If I was going to build it anyway, why not use it to learn something new? I'm a Flutter developer, but I chose React Native, a stack I was new to.
03
EXECUTION
Instead of learning React end to end first, I wrote my own syllabus covering just what this app needed, learned it, and finished the build. All data stays on the device in MMKV storage, so the app works fully offline, with no cloud sync and no special permissions. I designed the whole interface and the app graphics myself.
Technologies Used
04
OUTCOME
Once I was using it, friends noticed and asked if they could use it too. They had tried plenty of apps like it and said all of them were paid, with fewer features and weaker usability. So I published it on Google Play on 20 January 2026, partly to learn app publishing, and handled the release end to end. With no promotion at all, it reached 103 downloads and a perfect 5-star rating through word of mouth. I still listen to its users, and the next version is in internal testing now.
- Downloads, all word of mouth, no promotionas of 2026-09
- 103
- Play Store ratingas of 2026-09
- 5.0 ★
- Cost to users
- Free, ad-free
05
LESSONS
“You don't need to master a framework before you ship with it. Learn what the product needs, then build.”