Comments on: Making A Simple App Takes A Serious Commitment

By: Natasha Murashev

Natasha Murashev — Thu, 15 Nov 2012 14:38:00 +0000

Great advice! I usually go back to my old projects and just copy the features I need for my new projects. There is probably a better way to do that. I’ll make sure to take a look at the book you mentioned!

By: Nathan

Nathan — Thu, 15 Nov 2012 02:31:00 +0000

This happens a lot in both scripting and programming. The best solution I’ve found is to sketch out what you want the app to do before even touching a keyboard and prioritizing the core features above what can be added later. (Sound a little like MVP?) After that when you start work on the individual features write it in a way that you won’t have to recreate the effort in the future. Eventually you’ll have a working library of code where you can just throw those features in as quickly as you put together a MVP. I’ve found knowing software design patterns helpful in writing that kind of code. If your interested I’d checkout a book like “Head First Design Patterns. It contains the first 10 or 12 most commonly used patterns and strategies and for something more technical and deeper you can check out “Design Patterns: Elements of Reusable Object Oriented Software” which has most if not all common patterns (very hard read).

By: Jenna

Jenna — Mon, 08 Oct 2012 06:17:40 +0000

I think it may be a free time thing. That is, if I had a lot of free time, then I’d spend more time building a better app, versus, if I had little free time (Saturdays & Sundays only) then I would rather spend time doing other things than coding like watching a movie or relaxing…