Bruce Lefebvre

Content management meets mobile

IoT Day in Ottawa

The folks at IoT Ottawa hosted an all-day meetup on the subject of the Internet of Things, right here in the Adobe Ottawa office tower. As someone new to the IoT field I found the many short, to-the-point sessions served as both a nice introduction to possibilities in the industry and also as a glimpse into the innovation happening right here in our backyard. What follows are my personal highlights from the day.

Dr. Ghods on Smart Buildings

(thanks to Aali R. Alizadeh for sharing this picture)

Mobile Apps: Made and Managed in AEM

I’m thrilled to be returning to Basel this summer to present at the conference formerly known as CQCON: CONNECT Web Experience. This year I’ll be speaking about building and managing mobile applications within AEM, with a focus on the technical details of the solution.

To frame the context of the integration between AEM and PhoneGap, I told a story of a hypothetical company looking to extend the reach of their content by building a mobile app. Since presenting at both Adobe SUMMIT and AEMHub, I’ve had a chance to work with some real, non-hypothetical customers, and have selected a few themes from these experiences to highlight for an audience of highly-technical AEM pros.

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?

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.

Here’s what you’ll need to get started: