4 ms·
> I promise I didn't have my expectations too high, I only had a few core principles Proceeds to list 6 pretty high requirements. The author’s not wrong, thos
by makeitdouble 4y ago
> I promise I didn't have my expectations too high, I only had a few core principles
Proceeds to list 6 pretty high requirements.
The author’s not wrong, those are good requirements, but not to be expected from any standard app these days.
To dig on the first: “ Offline support”, this in itself requires a lot of work.
Going the technically easy way will often go in direct opposite to your business model (mobile ads or access info sales). Going for subscriptions or other mechanisms will have you do harder technical solutions, making that specific innocent requirement a decently high hurdle.
- woojoo666 4y agoWhy not just charge for the app itself, instead of trying to place ads or charge for subscriptions?
- makeitdouble 4y agoYes, this is of course one of the saner options. It brings a few issues down the line if you intend to have a server component for synching, or plan to maintain the app for a long enough time and/or expand its features etc, as paid upgrades are a PITA in iOS. But it could make sense.
- Jataman606 4y ago> To dig on the first: “ Offline support”, this in itself requires a lot of work What work are you talking about? How is accessing local filesystem more work than calling external API with authorization?