Building apps · Distribution · Real-world success
The App Was the Talk
A real story about what happened after I pressed Publish.
Introduction
I built Tarsi for a university talk
The first version
One weekend. One useful job.
- No backend or account system
- Financial data stored on the phone
- Basic income and expense tracking
- On-device AI
Launch price: ₱199
What happened next
People started buying it
Source: Tap & Swipe case study ↗
The wrong takeaway
“Build fast and ship” is not the full lesson
Many people build fast. Many people ship. Most apps still disappear.
Reality changes the conversation
A slide invites opinions.
A working app invites behavior.
- Will someone pay before trying it?
- Will they trust it with private data?
- Will they return tomorrow?
- Will they tell someone else?
An honest advantage
Distribution started before launch day
I had spent years teaching, speaking, making software and AI content, and building a community of more than 200,000 people.
I was not launching into an empty room.
Reach is only the opening
An audience is not a bag of downloads
People followed me for software and AI. Tarsi asked them to pay for a finance app.
Reach opened the door. The product still had to earn the sale.
The product was the message
Four choices people could repeat
Pricing as distribution
The price changed where Tarsi competed
Most apps fight for attention in crowded free charts. Tarsi entered the quieter paid charts.
Architecture as positioning
A technical shortcut became a reason to buy
The distribution loop
The Facebook group was part of the product
No product theatre
The community became the roadmap
- Requests came from real users.
- Reactions showed which problems were shared.
- Useful ideas went into Apple Notes.
- The strongest ideas shipped while the conversation was alive.
Where speed mattered
The feedback loop was the real advantage
User asks → I understand → I build → I release → the user responds
Expansion followed evidence
Android began with 900 names
I opened a simple Google Form instead of adding “Android” to a roadmap.
Replication
One success can be luck. Three reveal a system.
Tarsi#1 paid Finance
Mayi#1 paid Travel
Kabi#1 paid Health & FitnessThe cost of traction
Success created a new problem
- Three products to maintain
- Three communities to support
- More bugs and feature requests
- Less time for the next idea
Demand is not the same as durability.
A more useful scorecard
A chart position is an event
- A user returns tomorrow.
- A payment proves value.
- Feedback changes the product.
- The app earns without ads running behind it.
- The system works more than once.
Before the next pitch deck
Make these five things agree
- The store sentence — what users repeat
- The data boundary — what leaves the device
- The payment boundary — what the price buys
- The first room — who sees and discusses it
- The return path — why people come back
The practical version
Build the smallest real system
Not the smallest collection of screens. Not a throwaway prototype.
The idea I want you to keep
Put it where people can say no
Some people will say yes. Listen closely to what happens next.