4 ms·
I think we're missing your experience here. You seem to talk the talk, but have you built an app on the platform you're targeting before? How confident are you
by pedalpete 15y ago
I think we're missing your experience here. You seem to talk the talk, but have you built an app on the platform you're targeting before? How confident are you in your abilities to hit the deadline.
You seem fairly confident, so what's holding you back.
If you try to launch and don't quite make it, you'll end up with more sign-ups.
If you try to launch and the MVP isn't quite done, but close enough to get people using it, you'll get tons of feedback.
If you launch, you've got lots of exposure for an MVP.
If you don't do it, you only loose out the opportunity to talk to more people about the product and help to get it fine tuned.
The only reason I would say not to do it is if you think it is going to take 2 months, but then it ends up taking much longer, as you may kill off any goodwill. But again, how bad will it be.
- mgallivan 15y agoI'm a fairly confident programmer but I haven't spent much time in mobile development. I'm sure I can finished a core feature or two and have it ready for launch. My worry was that if I launch a product with half the core features, would that make it harder in the future to launch a fully-functioning application? (if people didn't like it the first time) Thanks for you response!