Thanks to those who joined and coded along during this week's webcast. @timanglade demonstrated how to build a store locator app using HTML5 and Adobe PhoneGap, incorporating geolocation and context-aware app features, and deploying easily with Apigee. The recorded webcast, the final code and the finished app are now available.
Enterprises are adopting API strategies to open up access to their back-end systems enabling developers to innovate and build web and mobile apps. Today's economy is exploding with business being done via apps, and as a result more and more transactions flow from end users and developers to enterprises.
Analytics plays a critical role in the success of an enterprise's API program. Using Apigee Analytics, Apigee Enterprise customers and their developers get visibility into their APIs, apps, and developer traffic. In our latest release, you can access a new "Traffic Composition" report right on the Apigee Enterprise User Interface (no setup required!).
I build apps all the time and while preparing for our recent webcast, From Napkin to App: Rapidly Prototype and Build for Mobile, I built out an Adobe Illustrator file that has all sizes of icons and background screens for various iOS and Android devices. I thought I'd share this collection of pre-sized artboards to use as a template for designing app icons and launch images. It will hopefully save you some time for the tedious task of sizing all your icons and launch images for various mobile devices.
When building an analytics system, three big areas need to be considered: how to capture, process, and visualize data. We’ve built our Mobile Analytics solution from the ground up with the requirements of data capture, processing, and visualization in mind. In this blog post, we examine each in the context of mobile analytics, including how they drive the requirements and influence the design of a mobile analytics solution.
Thanks to all who attended our recent webcast: From Napkin to App: Rapidly Prototype and Build for Mobile. The video and slides are below.
Brian Mulloy and Alan Languirand discuss the lessons they've learned quickly getting from concept to app. They provide a recipe for rapid app development and a list of the tools and techniques to successfully get from concept to prototype in just a few days.
In my last blog post, Optimizing for Mobile? Bounded, Piggy-Backed Mobile Network Transmissions, I talked about a way to reduce battery consumption and optimize apps for mobile.
The current implementation of the Apigee Mobile Analytics SDK (Android and iOS) follows a simplistic timed interval (60 seconds by default) for upload of secondary traffic (device metrics). This guarantees that the radio will be in the high state (turned on if it were off) at least once per minute. We will be revving our SDK to build in a bounded, piggy-backed strategy for secondary traffic to support the arguments...
Doing mobile app development? Need to optimize? One way to conserve battery is by piggybacking networking transmissions. To preserve battery life, the cellular radio in mobile devices gets put into a lower powered state after some inactivity, and then gets turned off after an additional period of inactivity. Once the radio is off, it takes some time for the radio to be turned on and for the radio to negotiate a new connection with a nearby cell tower.
The current implementation of the Apigee SDK follows a simplistic timed interval (60 sec. by default) for upload of secondary traffic. This guarantees that the radio will be in the high state (turned on if it was off) at least once per minute. We will be revving our SDK to build in a bounded, piggybacked strategy for secondary traffic.