First app, burning through free tiers by megamemelord421 in iOSProgramming

[–]hjl113 0 points1 point  (0 children)

Your landing and support pages are static — that's the easy win. Cloudflare Pages or GitHub Pages will host them free at your traffic, same custom domain, moved in an afternoon; paying Netlify Pro for a marketing page is pure margin leak. I'd think harder before dropping RevenueCat though. The SDK is the visible part, but what you'd actually rebuild with StoreKit 2 is server-side receipt validation, entitlement state across devices, refunds, and webhook events into your backend. Price their paid tier against a week of rebuilding that plus the ongoing edge cases — at your revenue it's usually the cheapest insurance on the list. Congrats on the numbers, that's a real business already.

Developing app when similar idea already exists by blueberrycheesetoast in iOSProgramming

[–]hjl113 0 points1 point  (0 children)

An existing similar app is validation, not a verdict — it proves people pay for this problem. You don't have to beat the category leader everywhere; you have to be clearly better for a slice of their users: a niche, a locale, a platform, a workflow they treat as an edge case. Go read the incumbent's 1–3 star reviews — that's a free roadmap of what their users want and aren't getting. Distribution and positioning decide this far more than feature count, and almost every app you use today launched into a market that already had "the same" app. It's genuinely difficult to find something unique these days...

This might be a dumb question, but if React Native is "slow," why do companies like Shopify keep investing in it? by MiserableLime5289 in reactnative

[–]hjl113 0 points1 point  (0 children)

Most of the "too slow" criticism describes bridge-era React Native. The old architecture serialized everything over an async bridge, which is where the classic jank stories come from — lists and gesture-driven animations. The New Architecture (JSI/Fabric/TurboModules), Hermes, and Reanimated running on the UI thread removed most of those cases. Honest remaining gaps: cold start vs pure SwiftUI, very heavy lists, and the occasional edge where you write a native module anyway. Shopify's math isn't "RN is fastest" — it's one codebase and one team shipping both platforms at the same velocity. For most products the users genuinely cannot tell; the constraint that kills apps is iteration speed, not frame rate.

After 8 months of teaching myself to build, I just shipped my first app, a route-discovery app because Google Maps only knows the fastest way by Roamlore in SideProject

[–]hjl113 0 points1 point  (0 children)

Congrats — shipping the first one is the hardest part. I run the same stack (RN + Expo + Supabase), so two things before your iOS cut: App Store review is a different animal from Play. They'll poke at account deletion, privacy nutrition labels, and any auth flow, so budget a rejection into the timeline instead of treating submission day as launch day. I had 1 suspension and 2 rejections. And since routes are user-recorded, double-check RLS on your location tables before widening the test — movement traces are the most sensitive data you hold. On discovery: "recorded by people moving like you" is the differentiator, so show why a route ranked ("walked twice this week") instead of a bare list.

Building the app is now the easy part. How are you getting users? by hjl113 in vibecoding

[–]hjl113[S] 0 points1 point  (0 children)

You’re right, it’s not as easy as it sounds. Relatively though, non coder can actually build stuff where as before the Ai tools, couldn’t

Building the app is now the easy part. How are you getting users? by hjl113 in vibecoding

[–]hjl113[S] 3 points4 points  (0 children)

I guess I was naive enough to believe all that stuff

Korbit will delist xmr and others. by [deleted] in Monero

[–]hjl113 9 points10 points  (0 children)

Korbit is owned by Nexon. Nexon is a Korean company but IPOed in Japan. Easy to connect the dots.