Shipping Flutter apps š± Dad of 2 š§š» Sharing wins & fails publicly. No days off. https://teapaw.org/t.co/RTXmTnYTh0 https://teapaw.org/t.co/OJtb36fe2w https://teapaw.org/t.co/VK5EkDfy9p
India
Joined December 2013
- Tweets5.7K
- Following586
- Followers1.4K
- Likes46.4K
Pinned Tweet
finished the purchase-abandon survey for SignalFind.
now when someone taps buy, opens Appleās purchase screen and decides not to continue, they get one quick question.
they can tell me if:
- price is the issue
- they want to try it first
- theyāre not convinced itāll work
- something else stopped them
or just tap āNot Nowā.
small change, but now I can make the next paywall decision based on actual user responses.
my last SignalFind app post on LinkedIn got 23K+ impressions.
65 people clicked through to the App Store and 7 new users installed the app.
the interesting part: almost all of them opened the paywall, tapped buy, reached Appleās purchase screen, but didnāt complete the purchase.
I could start changing the price or paywall based on guesses.
instead, Iām working on a purchase-abandon survey that appears after someone cancels the Apple purchase flow and asks what stopped them from buying.
that should give me actual reasons to decide what I need to change next and improve the app based on user responses, not assumptions.
I now have 2 apps with paying users.
pitchbuddyapp.com was the first.
Then SignalFind got its first sales too.
And now it just got a $10 renewal, taking the total to $30.
I know $30 is basically nothing as a business.
But this made me happier than the first payment.
The first time, someone was willing to give the app a try.
This time, they had a full month to use it, could have cancelled, and chose to stay.
PitchBuddy took me around 6 months to get here, and the revenue chart is still almost flat š
Still, seeing the first renewal is probably the best signal Iāve had from the app so far.
Ali retweeted
doing ASO research for SignalFind made one thing clear:
the biggest keyword isnāt always the best one.
"bluetooth finder" has more volume, but also much stronger competition.
Iād rather rank for a smaller relevant keyword than get buried trying to compete for the biggest one.
Ali retweeted
got my second sale for my Bluetooth finder app š
I havenāt spent anything on ads or really done much marketing for the app.
so far Iāve mostly been working on ASO, improving the App Store listing, and sharing the app only a few times on X/LinkedIn.
3 new users in the last 7 days, 2 purchases.
small numbers for now, but seeing people find the app and actually pay for it without ads is pretty cool.
got my second sale for my Bluetooth finder app š
I havenāt spent anything on ads or really done much marketing for the app.
so far Iāve mostly been working on ASO, improving the App Store listing, and sharing the app only a few times on X/LinkedIn.
3 new users in the last 7 days, 2 purchases.
small numbers for now, but seeing people find the app and actually pay for it without ads is pretty cool.
Vibe coding didnāt fail.
It simply made building easy enough to expose the real problem:
Distribution.
You can ship 10 apps this month.
But if nobody knows they exist, youāve just built 10 very fast ways to make $0.
SignalFind has 30 users so far.
25 of them reached the paywall.
0 purchases.
itās a $7.99 one-time purchase with lifetime access, so I expected at least some conversion.
I even added a survey after users back out of the purchase flow.
out of those users, only 1 answered: "too expensive".
so now Iām stuck š
- is it the price?
- not enough trust that itāll work?
- showing the paywall too early?
- something else?
what would you test next?
working on localization for SignalFind today and learned something useful:
changing the language inside your app doesnāt mean every SDK follows it automatically.
SignalFind uses Superwall for the paywall, and Superwall has its own locale setting.
so Iām syncing the selected app language with Superwall too.
worth checking if your app uses third-party paywalls, auth, chat, or other SDKs with their own localization.
Ali retweeted
I used to think App Store localization was mostly about translating the app.
turns out thereās an ASO opportunity too.
Apple has separate English (US) and English (UK) localizations, which means I donāt have to use the exact same keyword set for both.
and for other languages, I can localize the metadata around how people actually search in that language.
working on this now for SignalFind: Bluetooth Finder.
more localizations = more keyword opportunities to test.
Ali retweeted
Check out SignalFind: Bluetooth Finder šš» apps.apple.com/in/app/signalā¦
I used to think App Store localization was mostly about translating the app.
turns out thereās an ASO opportunity too.
Apple has separate English (US) and English (UK) localizations, which means I donāt have to use the exact same keyword set for both.
and for other languages, I can localize the metadata around how people actually search in that language.
working on this now for SignalFind: Bluetooth Finder.
more localizations = more keyword opportunities to test.
I added a one-time payment to SignalFind instead of a subscription.
the reason is simple:
you might need the app when an earbud or Bluetooth device goes missing, find it, then not open the app again for weeks or months.
charging every month for that didnāt make much sense.
so itās simple:
pay once ā unlock the finder ā keep it.
Ali retweeted
if I launched SignalFind app again tomorrow, Iād change a few things before hitting "Submit for Review":
- add product analytics before launch
- track the full purchase flow from day one
- ask users why they leave without buying
- make sure I can see exactly where users drop off
- stop staring at install numbers and look at what people actually do inside the app
these are all things I ended up adding or learning after launch.
wouldāve saved me a lot of guessing if I had them from day one.
if I launched SignalFind app again tomorrow, Iād change a few things before hitting "Submit for Review":
- add product analytics before launch
- track the full purchase flow from day one
- ask users why they leave without buying
- make sure I can see exactly where users drop off
- stop staring at install numbers and look at what people actually do inside the app
these are all things I ended up adding or learning after launch.
wouldāve saved me a lot of guessing if I had them from day one.
Ali retweeted
launching an app taught me something quickly:
installs tell you almost nothing.
I wanted to know:
- do they actually use the core feature?
- do they reach the paywall?
- do they tap buy?
- where do they leave?
so I added PostHog to SignalFind: Bluetooth Finder.
thatās how I spotted users reaching the purchase flow and backing out.
without those events, Iād probably still be guessing what to improve.