330 karma · joined April 6, 2012
Creator of HabitRPG, a startup begun on Kickstarter which now has ~1.5M users. Built an enterprise PDF-creation service employed by 1.5k sites, and websites for clients such as Adidas, BigFix, and UCSF. Obsessed with AI - bonafide Singularitarian and herald for the takeover. Check out my AI podcast http://ocdevel.com/podcasts/machine-learning.
But the reason I chose web first is (1) easy access to all platforms, (2) plug into web services and hooks. Eg, there's the Chrome extension (http://goo.gl/gze94) where you lose HP for surfing reddit, facebook, etc. Pomodoro plugin, and future integration with Pivotal, Asana, etc. Integration is easier on the web.
In all honesty, I didn't know about EW when I built this. When I saw EW after finishing the website, I thought "God damn it! Effing spot on, too" and walked home dejected. But their Android app has been long in the works, there won't be web, and in all honesty - I want something REALLY rpg. My goal with Habit is to push as many possible traditional RPG features into the app, starting with a 5-person party system, healing and all (see http://goo.gl/TvPTg)
After that, I use my own https://habitrpg.com to keep me on task with my Workflowy.
People say Backbone & Angular are different use-cases, but I find so many people "graduating" Backbone and wishing they'd chosen a more robust framework. They say they want to start minimal, so they pick Backbone. You can be minimal with Angular. It's like saying "ms paint or photoshop? Well what are you trying to do?" There's only 1 or 2 people really trying to draw something in Paint, the rest "think" they want minimal, non-bloated software. The answer to the question is Photoshop.
Now, Rails v Node v Java, something like that - there are tons of questions to ask before making such a decision, there's no one-size-fits all. But I think there is a one-size in this particular case.