So, you want to build an app
You’ve been approached by management and given orders to begin architecting a plan to get that ever-coveted place in the app store. Your peers at the office are devoted iOS fans - aside from that one guy, still touting the battery life of his flip phone - and expect to see your work in their preferred store, and soon. However, upon reviewing mobile browser analytics from your company’s site, you notice a trend: not all traffic is from mobile Safari. Hits seem to be originating from Android browsers at about half the rate of Safari, and Google’s Chrome browser is not far behind. Your office may be satisfied with an iPhone app, but how will your Android customers take it?
CQ Gems: Mobile First Development
Evolve 2013: CQ Mobile Apps
Setting up a Dispatcher on OS X
The dispatcher is an important piece of a secure, stable, and solidly-performing AEM implementation. According to the documentation it can provide caching, load balancing, as well as help to protect your publish instances from attack. For such a multifaceted tool it seems to receive very little attention during the dev process, typically called to action in the final stages of a deployment when most of the dev work has already been done. I propose that developers (including myself) could write better code if they had a deeper understanding of this tool, which is why I went through the process of setting one up on my Mac. What follows are my notes.