3 ms·
> it has bugs and it's not good enough to begin marketing yet Measure and prioritize the bugs. If you don't know how many people are dealing with them you can'
by hiou 12y ago
> it has bugs and it's not good enough to begin marketing yet
Measure and prioritize the bugs. If you don't know how many people are dealing with them you can't figure out how many you need to fix.
> I'm learning Swift to build the 2nd version
I won't tell you what to do, but software history is full of 2nd versions the morphed into death marches.
tl;dr Figure out the fewest amount of bugs you need to fix to make it work for 80% of your users and then market aggressively. Do not rewrite right now.
- jmduke 12y agoAs someone who rewrote his app in Objective C into Swift, I highly recommend it if you think Swift is rad (I do!) and enjoy substantially improving the quality of your code. That being said, I highly recommend against it if your primary goal is one of the following: - revenues - features - installs - bugfixes It will take you longer than expected to accomplish very little in terms of meaningful improvements which can be relayed to your customers.