Android Tutorial

Mobile development teams are often small in size and project schedules are short in length. The entire project lifecycle is often condensed, and whether you’re a team of one or one hundred, understanding the mobile …

Developers can easily adapt most modern software methodologies to mobile development. Whether your team opts for traditional Rapid Application Development (RAD) principles or more modern variants of Agile software development, such as Scrum, mobile applications …

Requirements analyses for mobile applications can be more complex than that of traditional desktop applications. You must often tailor requirements to work across a number of devices—devices that might have vastly different user interfaces and …

In addition to the normal risks any software project must identify, mobile projects need to be aware of the outside influences that can affect their project schedule and whether the project requirements can be met. …

You might think that with its shorter schedules, smaller teams, and simpler functionality, mobile software project documentation would be less onerous. Unfortunately, this is not the case—quite the opposite. In addition to the traditional benefits …

There are many wonderful source control systems out there for developers, and most that work well for traditional development work fine for a mobile project. Versioning your application, on the other hand, is not necessarily …

When designing an application for mobile, the developer must consider the constraints the device imposes and decide what type of application framework is best for a given project. Understanding Mobile Device Limitations Applications are expected …

Mobile application implementation follows the same design principles as other platforms. The steps mobile developers take during implementation are fairly straight forward: Write and compile the code. Run the application in the software emulator. Test …

Testers face many challenges, including device fragmentation (many devices, each with different features—some call this “compatibility”), defining device states (what is a clean state?), and handling real-world events (device calls, loss of coverage). Gathering the …

Developers need to determine what methods they use to distribute applications. With Android, you have a number of options. You can market applications yourself and leverage third-party marketplaces such as the Android Market. Consolidated mobile …

Generally speaking, mobile application support requirements are minimal if you come from a traditional software background, but they do exist. Carriers and operators generally serve as the front line of technical support to end users. …

The “rules” of mobile application design are straightforward and apply across all platforms. These rules were crafted to remind us that our applications play a secondary role on the device. Often Android devices are, at …

Last but not least, here is a list of some of the silly mistakes Android designers should do their best to steer clear of: Designing or developing for months without performing feasibility testing on the …

Developing applications for mobile is not that different from traditional desktop development. However, developers might find developing mobile applications more restrictive, especially resource constrained. Again, let’s start with some best practices or “rules” for mobile …

Like all QA processes, mobile development projects benefit from a well-designed defect tracking system, regularly scheduled builds, and planned, systematic testing. There are also plentiful opportunities for white box (or gray box) testing and some …