ME DID.

IN 2009.

AND 2007.

AND 2003.

Rest APIs and SPAs are not new but combing them with Responsive Design in a large scale app is. Who else is doing that?! Client-side rendering is super fast now (a reason why LinkedIn was able to change to it).

BASECAMP MOST FAMOUS VERSION OF HTML SNIPPETS.

ME PRETTY SURE TWITTER SWITCH BACK TO THAT TOO. OR MAYBE THEM SENDING BITMAPS. THEM DO SOME FUNNY THINGS.

LINKEDIN HAVE GOOD BLOG ON WHAT THEM DOING, IT WORTH READ.

TUMBLR, INSTAGRAM, USE VARIATIONS.

MOST EVOLVE LIKE THIS:

1. WHATEVER FAMILIAR WITH

2. GET SCALE, SWITCH TO SOMETHING THAT WORKS

3. GET MONEY, HIRE NECKBEARDS, END UP WITH LOTS OF SPECIALIZED PIECES IN DIFFERENT TECHNOLOGY THAT DO ONE THING GREAT

#2 IS PART EVERYONE GET EXCITED ABOUT.

http://highscalability.com/ GOOD SITE TO READ.

The thing to remember with the demise of the PC is that people will still use PC’s and increasingly laptops for content creation and ‘doing work’.

Tablets and Smartphones will continue to grow as content consumption devices. However they are a pain in the ass to do anything that involves more than swipe and tap.

The challenge for RSR is re-creating the responsiveness and performance of Native apps on smartphones. I think it’ll be a bit easier on tablets with the extra room but getting your RSR smartphone app to the point where a user can’t spot that it’s not Native is a real challenge.

Hey Dino,

Thanks for commenting.

Got links for any apps using this approach for more than just a “utility” type app? Ie, something of a fair size/complexity?

NOW IT THE BAR.

THOUGH ME RECOMMEND SHIP FULL HTML FRAGMENTS, NOT JSON, ONLY TINY BIT MORE DATA, LOTS FASTER RENDER.

Not to mention the fact it’s a massive selling point for us, many clients are considering mobile, but not yet convinced, or can justify, we can tell them to relax as little to no extra cost to develop the mobile client(s) later as the API backend remains consistent.