Why Android?

While controlling (the internet of) things from your phone makes a lot of sense, I've been asked why I would build a server application to run on an android phone.

Many people have started using android phones and especially tablets as dedicated devices within their homes or offices. Nearly as powerful as low end PCs and much cheaper, they come with easy to use touch screens and simplified user interfaces - they are becoming obiquitious. The simple touch screen interfaces forces developers to make them easy to use and convenient to carry.

For example, a wall mounted tablet in the kitchen provides a view of the weather, news, calendar, traffic, etc. Plus search for and use recipes (including a cooking timer), watch a TV feed or a movie, remotely control an entertainment system, or update grocery lists. A dock mount for your phone (or a spare phone) in the bedroom does the all this and adds an alarm clock, kindle books for night reading, and music. Adding my apps allow you to view the status of and control your security system and thermostats without the need for any additional wiring.

These devices are easily configurable and personalizable. Many new automation devices already ship with built in android (and iPhone) interfaces. Rather than single device consoles mounted in dedicated spots throughout your home or office, your android phones and tabets can be kept whereever they are most convenient for you, and show the information you need in the right way at the right time. Costs can be considerably reduced to the consumer; dedicated touch screen components (such as the CT-30 interface, or DSC dedicated keypads) are no longer required.

Tablets and phones are ideal as configurable control centers to manage many things - automotive controls (as you've probably noticed), your home, office, cottage, or other remote places. As prices continue to fall and connectivity improves, I expect these devices and mechanisms for control to become more pervasive.