Managing Lights and Plugs Made Easy for Developers With Taapi’s API

“…Taapi is gamification at it’s best.” Wired 
“The game is the first global, mobile gaming platform that will have a significant impact on the real-world.”

Taapi provides the first, open-source, global, all-purpose energy management API for developers.  

We believe that users should be able to control their light and wall sockets from their favorite applications and that app developers and game builders should be able to incorporate light and wall socket controls into their applications.
Managing lights and plugs has typically been an expensive, proprietary domain using closed source systems. Producers of light and wallsocket controllers do not allow wide developer access to their products in the home or integration of their in-home products with third-party applications.

How Taapi Works
We build wallsocket adapters and smart lightbulbs that operate using a commercial-grade protocol and low-energy WiFi chipset.
Through our smart bulbs and wall socket adpaters we create secure communication between lights and wall sockets to power lights and sockets on and turn them off.
The Taapi systems handle authentication of users devices, auth of user ID’s in your apps via OAuth and creating a completely masked identity for a user’s devices for security.
Taapi also maintains a constant record of state that recalls the state a socket or light was in when it was acted upon by Taapi. Maintaining states ensures that the light or wall socket can be returned to it’s original state when a user wants to regain full control of their lights or wall sockets.

Taapi employs commercial-grade standards in it’s open-source APIs.

Multiple devices can be run off of a Taapi wallsocket.  Lightbulbs can be used for hardwired lights, like overheads.

Taapi creates local WiFi communication between sockets and bulbs by using a hub that connects to your router. The hub communicates securely with the Taapi service and the light’s owner. The Taapi service exposes REST services to developers.

Taapi Cloud Services for Developers

The Taapi Cloud and Service Paths

Easy Integration for iOS, Android and OUYA Enabled Games

Integration with Taapi is optimized for speed and ease of set-up.
Libraries for iOS, Android and a rapid-setup, special build set of classes for OUYA will be available to developers. Integration with Taapi is optimized for speed and ease of set-up.

The Taapi Social Game
The Taapi API is now used to power a social game where unused lights are added to a pool of anonymous lights waiting to be turned off. Players race to turn off lights as they are added to the pool. This game leverages many parts of the API such as session establishment, auth and lights and plug management.
The first Taapi game is available on iOS, Android and the OUYA game console.

The Taapi Social Game

What will the Taapi API offer developers?
Taapi manages the heavy lifting that devs typically associate with environmental controls: hardware, normalization, security, WiFi protocols and local network authentication
We manage those pain points and provide the dev with a manageable API that they can leverage as the dev, and their users, see fit.
Taapi has tools to provide access to a range of game and app developers by providing a full REST API with hooks that can programmatically act on Taapi’s services from your app or service.
The Taapi API will provide access for app and game devs to features such as:

  • Adding new players
  • Authenticating players
  • Calling player stats
  • Calling general country, energy, and date stats
  • Initiating a race session
  • Obtaining the stats for a unique race session
  • Polling for available races

Taapi has selected Atlassian ( products for community support, Mashery ( for API hosting and Taapi has built-in an OpenSocial container for developers to write gadgets for Taapi using the OpenSocial ( standard.

Taapi’s OpenSocial container support will allow developers to quickly and easily write OpenSocial compliant gadgets that can call and serve a number of Taapi features like public Taapi use statistics, aggregated stats, individual users stats and game session availability.

The Taapi OpenSocial container will support gadget authentication via OAuth to enable personalized, contextual player information and interaction as well.  Players will be able to add approved gadgets to their instances of the Taapi game and extend Taapi’s functionality.
For example, a developer could write a ‘My Country’ Taapi gadget to alert a player when a session in a specific country is available, authenticate them, opt them into the game session and tweet about their participation, all in that country’s native language(s).

Taapi founder Carol Glennon states, “Support for an accelerated development process was one of our top goals for the Taapi platform. Enabling gadgets through our OpenSocial container makes it easy for developers to gain fast access to our API while writing cool gadgets that users can use in Taapi right away.”

Access to the Taapi API will also be available on Zapier, a service that syncs many different web apps. A developer can use Taapi and Zapier to initiate a number of web actions for example, setting a block of time that lights should be turned off for a user when they schedule a calendar event in the devs application.

Taapi Partners and Community Services for Developers

We Are Counting on YOU
We need your support as a backer now to produce the lightbulbs and wallsockets that will be used in thousands of your users homes and offices.
Enabling us to produce our home kits provides you as a developer with an ever-widing pool of users that are ready to use Taapi with your app and games.

Please come and back us today and pick a great reward. It’s inexpensive, fast and will benefit your app or game greatly.

Taapi Team Experience
The Taapi core executive team have been working on projects together for over a decade and have experienced amazing success in that time. Together, they have a pretty cool history of ability to deliver amazing experiences. Examples of previous work includes delivering mobile apps, games as well as cutting edge and complex 3D animations and solutions for major consumer-focused companies including Time Warner, Intel, CBS, California Tourism, Delta Airlines and National Geographic.

We have been recognized and received over a dozen National and International awards for our work and have been at the cutting edge of technology for a combined four decades.

2012 National Geographic Kids Almanac
2011 Visit California iPad application
2011 San Francisco Giants and Safeway2011 San Francisco Giants and Safeway
2011 MLB, 7Eleven and Frito Lay
2010 Stevie award – Most Innovative Company  of the Year
2010 World Cup through FIFA backed 1Goal
2004 Who Wants To Be A Millionaire U.K. (mBlox)

Author: Carol Glennon

iOS Development, XCode

Distributing iOS Applications for Private Testing, The Magic of Ad Hoc

The design, build and testing process for an iOS application should be extensive and iterative.  Combining excellent human-interface design with well-functioning code are the visible hallmarks of the best iOS store applications. 
A large part of the behind-the-scenes magic for top iOS applications is the manner in which they are tested long before being submitted to iTunes for final approval.
Ad hoc distribution makes private testing readily available to stakeholders on their personal iOS devices.

The typical development cycle for an iOS application will include rounds of testing, bug fixes and more testing. Once most major bugs are cleared, user acceptance testing takes place. This step gets difficult for brands that have distributed stakeholders or a combination of internal and external stakeholders.
Faced with the issue of distributing a test build of an application to disparate stakeholders many developers choose to undergo an early submission to the iTunes store to achieve easy distribution to the stakeholders for approval. The hope with this approach is that the submission goes largely unnoticed by the general public and that the stakeholders will have time to review the application after being asked to download it via the public store. The stakeholders provide feedback, normally under a tight deadline, in turn the development and product teams make an iterative update to the application incorporating the feedback. After the update to the application is successful the brand formally announces the launch to the public.
The risk of wide-spread, early public exposure and the tight response times required of stakeholders create a perfect storm that can be avoided by using ad hoc distribution or in-house distribution.
Ad hoc distribution allows for limited distribution, for up to 100 devices, of a fully-functioning iOS application. Stakeholders receive a private, ad hoc application file, install it using iTunes and can test without pressure.
To create the ad hoc application for distribution developers must build an Xcode archive of the application. They should then locate the archive in the archive organizer and select “Distribute.” Choose “Save for enterprise or ad hoc deployment” and then save the resulting .ipa file to send to stakeholders for installation. User installation consists of dragging and dropping the .ipa file into the Application folder in iTunes and then connecting their iOS device.
The ad hoc process requires that the stakeholders submit their iOS device’s ID or UDID, a unique 40 character string, to developers for addition to the iOS provisioning portal. This process allows 100 devices per calendar year, for each Standard iOS development membership. At the beginning of the calendar year old devices may be deleted to make room for new devices to be added for that year.
Developers enrolled in the iOS Enterprise program are able to distribute applications in-house to an unlimited number of devices using the same process. Files distributed in this fashion should be protected as the file is able to be installed on any iOS device without requiring a pre-registration of the device ID. The enterprise distribution method is also appropriate for applications that are built and designed for permanent internal use by an organization.
Ad hoc application distribution encourages significant stakeholder involvement in the iterative process. This behind-the-scenes iOS magic makes all the difference between simply getting an application out the door and building a truly great application with stakeholder buy-in.

Author Carol Glennon