Mobile

Wouldn’t it be great to develop for Google Glass without learning a new programming language, and even by just using knowledge common to all web developers? Yes, it is possible! This article will introduce you to web development techniques you can use to build application used on Google Glass.

Since Apple's launch of Swift this past June, many iOS developers have been struggling with the question of if, how, and when to transition from Objective-C to Swift. This article explores some important points to consider before jumping into Swift development.

After 6 years of improving and working on Objective-C, Apple decided to throw another challenge at developers. Once again, iOS developers will need to learn a new programming language: Swift. Swift 1.0 is already a stable and strong development platform, which is sure to evolve in interesting ways over the coming years. It is a perfect moment to start exploring this new language, as it is the future of iOS development.

Google Glass promises to revolutionize how we use our devices to interact with the world. But from a developer's standpoint, what is so special about developing for the Glass? You'll be glad to know that the answer is "Nothing!" Here's a step-by-step tutorial that walks you through developing your first Google Glass app.

I often hear iOS developers ask some variant of the same key question: "What's the best way to develop a UI in iOS: through Storyboards, NIBs, or code?" Answers to this question, explicitly or implicitly, tend to assume that there's a mutually exclusive choice to be made, one that is often addressed upfront, before development. I'm of the opinion that there's no single choice to be made. Rather, each option has its strengths and weaknesses—and there's no need to use any one of them in isolation.

Mobile web development—optimizing web apps for mobile devices—is necessary for modern apps. Discover the best methods and tools for the development of highly functional, intuitive, and easy-to-use mobile web apps.

Making a basic Android app is easy. But making it reliable, scalable, and robust, on the other hand, can be quite challenging. With thousands of available devices pumped out from tons of different manufacturers, assuming that a single piece of code will work reliably across phones is naive at best. Segmentation is the greatest tradeoff for having an open platform, and we pay the price in the currency of code maintenance, which continues long after the app passes the production stage. In this post, we'll walk through a solution: automated crash reporting with ACRA and a Cloudant back-end, all visualizable with acralyzer.

Building games for the iOS platform can be an enriching experience in terms of both financial and personal growth. Recently, I deployed a Cocos2D-based game to the App Store. In this post, I'll explain the process behind developing games for iOS, from Cocos2D through to publishing.