I love personal annual report season. Nicholas Felton's (feltron.com) and Jehiah's are the two that I've been looking at the longest.
The amount of work that goes into these — being thorough when collecting the data throughout the year and putting it together in a nice package at the end — is too daunting for me to consider, so I like observing and admiring the odd minutiae of the lives of those willing and able to put in the work.
"… as soon as I saw 'the slow web movement,' I assigned my own meaning to it. Because it’s a great name, and great names are like knots—they’re woven from the same stringy material as other words, but in their particular arrangement, they catch, become junctions to which new threads arrive, from which other threads depart."
I'm having a hard time without sarcasm tags. The Web 2.0 was so vague a phrase that it had too many meanings and the end was meaningless. I doubt any new threads were woven due to the invention of that phrase.
Nice. It does seem like one of the lighter-weight Python web frameworks might fit in better with the overall theme of this intro, and Flask is a great choice.
I thought about doing the same thing as I read through it.
I believe that the python2.6 json module (basically forked form simplejson) is much slower than the current simplejson version. The speedups (simplejson rewrite) didn't get included until 2.7 as I recall (memory is vague on this point).
Kind of strange title, to me. I don't know why anyone would ever create separate server-side backends for different mobile platforms. I guess this just means that this company is providing libraries for both Android and iOS? Are the other "easy mobile app backend" services focused strictly on one platform or the other?
Hey, sorry if the title confused you. What we've heard from many mobile developers is that they want their apps to be cross-platform so they can reach more users. We have spent over a year building a platform that allows people to build a backend to their mobile apps very easily. We first focused on iOS and now our platform supports Android as well.
What we mean by single backend is you can have one backend and you don't need to know whether you are on an Android or iOS platform. You get the same analytics. You get push sent by username without caring whether it's an Android or iOS. If you are curious to see how it all works read our latest blog post http://bit.ly/onEjgM
I'm still confused. I'm neither an iOS nor and Android developer, so maybe this is not a confusing situation to them. But:
> What we mean by single backend is you can have one backend and you don't need to know whether you are on an Android or iOS platform. You get the same analytics.
I can't fathom why a backend service would ever not work this way.
The title confused me as well. Can you revise it to something like the "Backend Service Provider StackMob Comes To Android" title which the linked article used?
> _I think this is the current problem with mobile web apps today; too many are trying to feel native. Instead try to make it feel smooth and responsive, as a web app._
I think this is exactly what OP has done. It doesn't feel "native" to iOS to me, but it does feel like a well-made little web app. I don't have an Android device to test it on, but it does seem like it would fit in just fine on one.
The amount of work that goes into these — being thorough when collecting the data throughout the year and putting it together in a nice package at the end — is too daunting for me to consider, so I like observing and admiring the odd minutiae of the lives of those willing and able to put in the work.