Build a Where? app for web and Pebble users

Where? App Logo

Where am I? Where can I go? Where have I been? In this tutorial, you’ll build a client/server app that answers these and other “where” questions for web users and for wearers of the Pebble smartwatch.

First, you’ll build the back end: a Node.js app that you’ll deploy to IBM® Bluemix. The back end provides a REST API that enables clients to:

  • Register a user’s geolocation with the server, to be stored in a Cloudant NoSQL database.
  • Get the nearest postal address associated with the location by using the Pitney Bowes Reverse Geocoding service (UPDATE: now part of the APIs from Pitney Bowes service). This service provides a powerful API for looking up postal addresses based on GPS location.
  • Retrieve information about where someone could travel from a location, by using the Pitney Bowes Travel Boundary service. This service provides GPS coordinates for a “boundary” around a specified location that can be reached based on driving time or distance.
  • Provide worldwide statistics for recent and popular “check-in” locations (using the MapReduce capabilities in Cloudant).

Then, you’ll use this REST API as the basis for building two very different client apps:

Where? App: Pebble Main Screen

  • An app written for Pebble that’s designed to provide useful but more-focused info in the smaller screen of this cool wearable device. You’ll write this client app in JavaScript by using the Pebble.js library and the CloudPebble online IDE.

Where? App: Web with Travel Boundary

The New Bluemix Look

We have been listening to your feedback on the Bluemix UI and have used that to design a brand new user experience (UX) that we believe will streamline your workflows. The new experience is now live for your immediate use. In this blog, we'll walk you through the new taxonomy organizing your resources, the redesigned catalog, the updated flows for creating new compute resources, the reorganized app details page, and more! Continue reading

Bluemix Updates: Cinco de Mayo!

Published on May 04, 2015