How we built the new Exec iPhone App
In this technical retrospective (2012), @mjdipietro shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Web 2.0 Genesis (2007–2013)
COMMUNITY SCORE 70 points
TOTAL DISCUSSIONS 34 comments
I'm sorry, but I don't like this UI at all. It looks foreign on the iOS as if it were designed for some other device and the ported over. Such neglect for the consistency with a native look and feel is not a "fun experience", it's really quite annoying.
My iPhone is not an empty canvas for you to drop an arbitrary UI style on. It comes with Helvetica and a whole bunch of well designed controls. I insist you use them.
Really curious to know why you had to reimplement Uikit uiview subclasses instead of just extending them and use ib to position them. Drawrect overriding has always been the recommended approach, and at least you can position buttons and panes and tableviews using ib , simply changing the name of the class in IB...
Funny to see him talking about reading the header files of the built-in classes to guess how they work - One of the things I prefer about Android development is being able to easily dig into the source, most of it is easily understandable and it gives a good authoritative reference.
I wish this post had more specifics about the coding or design. As is, it's screenshots and generic descriptions of difficulty. It would be good to hear why you made specific design decisions, why you didn't want to use IB, breakthroughs you had creating custom UIAlertViews etc.
Hey, great write-up. I feel that if you're creating a simple app you can only get so far with the built-in theming. Custom animations/themes are critical to make a fun, useful, and simple apps. I would love to see a blog post/tutorial on this topic.