{"id":558,"date":"2013-05-01T07:59:12","date_gmt":"2013-05-01T12:59:12","guid":{"rendered":"http:\/\/www.padizio.com\/blog\/?p=558"},"modified":"2013-08-07T10:12:09","modified_gmt":"2013-08-07T15:12:09","slug":"web-and-native-sitting-in-a-tree","status":"publish","type":"post","link":"https:\/\/www.padizio.com\/blog\/2013\/web-and-native-sitting-in-a-tree\/","title":{"rendered":"Web and Native, Sitting in a Tree"},"content":{"rendered":"

Last night I read the delightful “Web Apps vs. Native Apps Is Still a Thing”<\/a> by my he-doesn’t-know-me internet pal John Gruber. It’s a great piece, in response to this article from Wired<\/a>.<\/p>\n

The most salient point here:<\/p>\n

\n

Andreessen does have a solid point in the fact that app stores are in some ways a pain in the ass \u2014 particularly Apple\u2019s App Store, with its deliberative and at times opaque approval process. But app stores are mostly only a pain in the ass for developers, not users.<\/p>\n<\/blockquote>\n

I don’t think this can be overstated. App stores are incredibly convenient as a computer user<\/em>. Even as a developer, the fact that I don’t have to think about collecting money when I make an app<\/a> is – for 99% of apps – worth any pain endured in the opaque approval process.<\/p>\n

I’ve had the opportunity to develop a large<\/a> number<\/a> of apps<\/a> and websites<\/a> at my day job<\/a>. We build custom apps and websites for clients. So we get the “what should we build” question all the time.<\/p>\n

Here’s how I break it down for them.<\/p>\n