The 10 year old indie mobile app: what worked for the long haul
1–10 of 18 posts
Re: The 10 year old indie mobile app: what worked for the long haul
#2[deleted]
Re: The 10 year old indie mobile app: what worked for the long haul
#3What do you mean with running App Engine locally? There used to be a local development server, but that did not survive the 2to3 transition. GCP does ship a Datastore and a PubSub emulator, but no Cloud Storage for example (someone wrote this one [1], which sort-of works but it does not behave 1:1 like GCS, so ironically my tests have to work around bugs in the emulator...).
Re: The 10 year old indie mobile app: what worked for the long haul
#4What do you mean with running App Engine locally? There used to be a local development server, but that did not survive the 2to3 transition. GCP does ship a Datastore and a PubSub emulator, but no Cloud Storage for example (someone wrote this one [1], which sort-of works but it does not behave 1:1 like GCS, so ironically my tests have to work around bugs in the emulator...). [1] https://github.com/oittaa/gcp-storage-…
I'm using dev_appserver.py, installed via brew somehow, which seems to still do the trick (I don't quite remember doing this, but something like https://stackoverflow.com/questions/40065497/cant-find-dev-a...)
Re: The 10 year old indie mobile app: what worked for the long haul
#5I have over 50 ios apps that are over 10 years. It is amazing how competitors come and go.
Re: The 10 year old indie mobile app: what worked for the long haul
#6I have 10 year old android apps. Granted mine have few users and were never successful.
Re: The 10 year old indie mobile app: what worked for the long haul
#7> Novelty and optimization are the enemy of durable, long term code.
This sums up so much of what makes software rot in seemingly short time horizons.
Oh, and 3rd party SDKs that he mentioned.
Limit complexity and 3rd party SDKs like the plague.
Re: The 10 year old indie mobile app: what worked for the long haul
#8I have an 8 year old app that reminds me a lot of this article.
Something that's worked really well for me was that I created a plugin feature and most new features are actually plugins. This lets me add capabilities without touching or adding logic to the core code.
Last night I added SQLite support as a plugin. 2 code files and one is unit tests. https://github.com/jmathai/elodie/pull/443/files
I don't know if this is the best approach but it's worked better than others in my 20+ years of writing software.
Re: The 10 year old indie mobile app: what worked for the long haul
#9I have over 50 ios apps that are over 10 years. It is amazing how competitors come and go.
I'm curious how profitable that has been over the decade?
Re: The 10 year old indie mobile app: what worked for the long haul
#10> Novelty and optimization are the enemy of durable, long term code. This sums up so much of what makes software rot in seemingly short time horizons. Oh, and 3rd party SDKs that he mentioned. Limit complexity and 3rd party SDKs like the plague.
Alan Perlis' version:
> Optimization hinders evolution.
Still my favorite of all his epigrams.