Shipping any app on a budget is a daunting task for so many reasons:
Competing technologies at every level of the stack all have their advocates and evangelists.
You need skills within your team (which might be just you!) across a really wide spectrum of skills.
Technologies and new competitors are constantly emerging. Before your first release, you may have to pivot or completely rewrite
Different opinions on what you should prioritise will come from almost everyone you ask for feedback
You're most likely building a product to fulfil a need or tap a market that doesn't exist yet and which, while scaleable is impossible to predict potential revenues (let-alone profits) from.
You constantly are having to tradeoff bootstrapping solo (or near solo) with spending (and/or raising) funds to develop more quickly.
In this app, I'll seek to demonstrate my experience developing and shipping apps both for myself and for other organizations. Along the way we'll:
Learn to differentiate good technologies from bad ones.
Identify common pitfalls that could trip you up further down the development pathway.
Expose the real pitfalls of AWS, Apple and Google and evaluate external tools that are worth paying for, like Sentry or Circle CI
My views are born of real-world experience, and so are to be disagreed with as well as hopefully being endorsed or useful to someone. Genuine comments are always welcome, both direct to the article or indirectly via Twitter or Email.
Did you find this article valuable?
Support Ben Watts by becoming a sponsor. Any amount is appreciated!