Ray | $68K MRR (@_RoadTo10M) header
Ray | $68K MRR (@_RoadTo10M) profile picture

building apps since iphone 1 100+ apps | net worth $6.4M → $10M usd

Joined November 2021
19 years. $6.4M net worth. I started from zero. Here’s what I learned building apps since the first iPhone. 🍎📱
10
1
1
65
76,237
Why people are so care about him? Just block him back and move on.
20
1
1
50
1,745
hi 👋 , vibe coding in OSAKA rn. Looking to #connect with people who are actively building.. - indie hackers 🥰 - designers - vibe coders - #founders - #builders Show me what you're working on, let's connect
67
35
1,159
The worst part of Japan is the tourists.
The best part of Japan is the Japanese.
2
4
148
a local checkout isn't much of a fallback if you can't finish a change without the agent. try one small edit through to an archive in Xcode. check the toolchain, signing setup, screenshots, and review notes while nothing is urgent. the goal isn't a completely offline release. Apple's signing and submission services can still be required. it's a smaller, useful habit: don't let an unavailable coding assistant be the only thing blocking work you could finish locally.
3
3
130
Founder lesson before Submit, test the device you didn’t design around. an iPhone app may also run on iPad in compatibility mode, or on compatible Apple silicon Macs and Apple Vision Pro. check where your app can actually be available. recommended habit: take one other compatible device and run the core job. look at layout, input and navigation, not just whether it launches. your development phone can’t answer those questions for every destination. developer.apple.com/help/app…
4
139
“it worked on device” needs a build number next to it. when a teammate, contractor or agent hands over a candidate, ask which binary the evidence belongs to. last week’s recording doesn’t prove today’s build. a pass on another scheme doesn’t settle this configuration. recommended habit: run the critical path on the candidate device build and attach the result to that build number. confirm team, bundle ID and configuration if those changed. handoff the evidence, not just the confidence.
7
6
269
the expensive part of generated Swift is finding out why it almost works. Collins named “vibe coding” its 2025 Word of the Year. getting a screen from a prompt is one thing. diagnosing the wrong state after restore or a crash on relaunch is another. ngl another generated patch isn’t a diagnosis. reproduce the failure. read the stack. give the agent a failing case, not “try again.” blog.collinsdictionary.com/l…
4
2
201
If you’re into tech, let’s connect 🤝 Building something, SaaS? Say hi and tell me what you’re building rn 👋
2
2
193
a successful test purchase can still leave you with a broken product. the transaction is only part of the path. did the entitlement unlock the feature? does access survive relaunch? can the same test account restore after reinstalling? before a payment change ships, check those in StoreKit Testing or Sandbox. confirm the intended bundle ID, signing and environment configuration too no casual real charges to "be sure." know which environment you tested and what it couldn’t prove
2
3
192
I’m Ray 👋 Building apps and exploring Kyoto rn 🇯🇵🇯🇵 If you’re in #tech, let’s #connect!
12
7
423
one “ready to ship” checklist is doing two different jobs. an internal dashboard needs access controls, tested data and a recovery plan. a customer App Store app needs its own runway: signing, review notes, demo access where needed, compliance answers and customer support. keep two checklists. pick the right one before the release starts. faster web deployment shouldn’t quietly rewrite your Store definition of done.
2
5
352
I woke up with 1000+ followers in 5 weeks looking to #connect with - builders - #founders - app marketers - #SaaS - #buildinpublic - screenshot designers - app developers my next goal is to hit 5k in 3 months, be a small part of this journey Drop a “Hi” if that sounds like you 🤝 let’s connect 🚀
18
12
643
read this before you build the next “nice to have” cold opens aren’t vibe checks. they’re timed interviews. stranger opens the app, tries the job, leaves or stays. tbh the tutorial is rarely the fix — the first tappable job usually is screen-record a cold install. watch it without narrating. that’s your real onboarding
5
2
200
i stopped testing platform changes only on my daily driver years ago one spare stays on the public beta track whenever my apps lean on platform surfaces - App Intents, widgets, SharePlay, new review flows. daily driver stays stable. spare eats the surprises 27.3 public beta is a good reminder to re-enroll that spare if it’s been idle what’s on your spare-device beta list rn?
3
4
324
launch-day downloads are a vanity spike. week-1 paid still-active (and what people say when they cancel) is the real signal acquisition threads get likes. the cancel reason / support thread is free consulting most founders ignore while they sketch App N+1 habit: before you start the next app or feature, read the last 20 cancel/support notes. ship one fix that answers them
4
2
252
tbh shipping code was never the scarce bit. getting through the gate clean and keeping people who already pay still is when a vibe-coded first app sits in Waiting for Review past Apple’s 50% / 24h and 90% / 48h targets, it’s usually missing demo login, incomplete notes, or first-app scrutiny — not Apple secretly slowing the queue write Review Notes like the only user who will ever see them is the reviewer developer.apple.com/distribu… developer.apple.com/help/app…
10
14
2,029
App Review Information is a product surface, not paperwork demo account. special setup notes. a walkthrough video when the path is hard to reproduce. Apple says missing that info can delay or fail review, and on average over 40% of unresolved issues sit under guideline 2.1 App Completeness (crashes, placeholders, incomplete info) habit before Submit: open Review Notes and ask “could a stranger approve this in one sitting with only what I wrote?” developer.apple.com/distribu…
developer.apple.com/help/app…
2
13
1,900
Apple opened a Siri AI Developer Preview now. customer shipping “in a few months.” App Store submission in the spring when the platform gives you a quiet preview window before the store opens, use it. don’t wait for “final” docs. ship to yourself and internal TestFlight, try asking your app the things real users would say, and fix the intents while nobody’s reviewing you yet builders who treat previews as homework always feel late on submission day. the ones who practiced early look overnight when it goes public developer.apple.com/news
4
7
438
I’m Ray 👋🏻 I’ve been building apps for 19 years. If you’re a founder or just love tech, let’s #connect 💪🏼
25
26
876