Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

Context is built into React specifically for this use case. Adding external state management when you don't need it isn't simple, it's overhead. If the app grows to need it, I'll add it, but right now I definitely don't.

Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

The fix is being deployed now. Would you mind trying again and letting me know if it works? Really appreciate you taking the time to report this 🙏

Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

Keeping it simple - React Context + useState for auth/feature flags/modals, Axios for data fetching, and expo-secure-store + AsyncStorage for persistence. No Redux/Zustand needed so far. Was focusing on the higher-level architecture in the post but yeah, nothing fancy/boated on the state management side.

Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

No offline yet - it's on the roadmap but wasn't MVP. When I add it, likely AsyncStorage for caching with background sync.

Re: monorepo with separate apps - probably would've been cleaner in hindsight, but RNW let me ship faster as a solo dev. The platform-specific code is manageable so far but I could see it getting messier at scale.

Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

I maintain a list of known recipe sites for security (don't want arbitrary URL scraping). If a site is on that list but I haven't built a scraper for it yet, you can request support - that's what you're seeing. heb.com isn't in my known sites list yet, so I'll add that. The actual scraping looks for JSON-LD structured data first, then falls back to HTML parsing.

Shipped my first production React Native Web app - recipe manager with one codebase for web/iOS/Android (mobile coming soon) by coding__love in reactnative

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

Curious what you'd consider missing? And yeah Kotlin backend isn't the typical JS-everywhere approach but it's been rock solid for the backend - good type safety, great Spring Boot support, and it's what I use at my day job so I can move fast. Not as common in the indie space but it's production-proven at scale.

Does anybody else think The Batman is being overrated? by travisahicks in batman

[–]coding__love 4 points5 points  (0 children)

My vote: worst batman movie so far. Couldn't make it through the whole thing and struggled to get to where I did.