Show HN: I built a React Native boilerplate to ship mobile apps faster (expoship.dev)
Hey HN.
I'm a developer and solopreneur.
Few months ago I realized I was doing the same thing over and over again: set up onboarding flow, user authentication, payments, connect a DB...
So I built ExpoShip for 3 reasons: 1. Save Time and focus on what matters: building a business. 2. Avoid headaches like setting up authentication or handling in-app payments. 3. Get profitable fast.
I hope this boilerplate will be as helpful to you as it is for me. Would love your feedback.
Rudolfs
13 comments
[ 3.8 ms ] story [ 63.1 ms ] threadOne thing that caught my eye is that you're using expo - how do you handle the tradeoff between expo's ease of use and its potential limitations? do you have any plans to support non-expo react native projects in the future?
And have you used flutter? I've used both rn and flutter, and i found flutter to offer much superior dx
Regarding Expo, I found the the easiest and most sane way to get iOS compilation working. It worked for me and got it set up in < 1h. Just getting Xcode to work took me way more and I don't even use xcode to code wtf
About flutter, yes I have used it a year ago but for my use case it didn't work very well so I switched to React Native.
I only have experience with no expo react-native development
Same thing if I sign in with github.
Trying it again now it’s still the same bug, and the email doesn’t arrive.
If you have bugs like this at the first point you’re trying to acquire a customer then that doesn’t bode well for the robustness of the product you’re selling.
I was genuinely interested to buy this (I bought shipfa.st, and have found it very useful) but this is a big red flag.
After building an app from scratch, I see the value in a nice starter template.
You can add your kits to BoilerplateSearch .com directory
That's not cool.