#AppleWatch & #PlaceCodes
Posted on April 8th, 2015
4/8/2015 @Mission50 room 213, 50 Harrison Street, Hoboken, NJ
The presenters were
- Peter Kramer talking about his experience developing and app for the Apple Watch
- David Ingerman @PlaceCodes, tells mobile users the nearest place to purchase a product
Peter Kramer talked about his experience extending his stock position app to display daily returns on the Apple Watch. His original StockPosition app monitors how your positions performed during the trading day.
He was invited to Apple’s headquarters to expand his app to display on the Apple watch. His app, “Watch My Stock” is currently being reviewed for inclusion in the App Store. The data download is still done by the phone, but the returns are communicated to the watch over a Bluetooth link. He found that the slowness of communication had a major effect on his interface design on the watch. These included:
- There was a delay in the download using an actual watch. This delay affected the program design. However, the simulator showed an immediate download.
- Since it could take 5 seconds to transmit the portfolio, the interface was designed to display the initial entries on the top of the screen as a fixed image while downloading the remaining positions which were in a more general format. These positions would be revealed only when the display was scrolled.
His description of the interface, communication link, available hardware, and programming constructions such as notifications , etc. lead me to believe that the general programming tools and hardware limitations for the Apple watch are similar to those of the Android watches. Peter was more ambitious in developing his application than I have been in my Google watch application, however, some of the issues he encountered appear to be due to quirks in Objective-C. Swift and ADT/Java may not have some of these issues.
David Ingerman @PlaceCodes: “the shortest distance between intent and purchase”, helps businesses drive consumers to physical locations. Their approach disintermediates Google by giving the seller control over the list provided to the customer of the nearby locations selling the product.
For example if a mobile user wants to buy Friendly’s ice cream, a custom web page from PlaceCode can provide nearby locations of both restaurants and supermarkets selling the product. By contrast a Google search only shows the restaurant locations and will show locations for competitors.
David talked about how their approach can include promotions. He gave an example in which customers could win football tickets when they went to a Buffalo Wild Wings restaurant on Tuesday nights. When the user opened the app on a Tuesday it would display a sweepstakes entry form if the customer was at a Buffalo Wild Wings restaurant. If it was a Tuesday, but the customer was not at a restaurant, the app would show the nearby restaurants. If it was not a Tuesday, it would show the nearby locations and invite the customer to come back on a Tuesday to enter the contest.
He talked about how the user locations where the app was opened could be mapped in real time versus the store locations. He also talked about future developments including
- A customer searching for locations could save a reminder/coupon to buy the product upon arriving at the store.
- Image recognition: a scanned billboard or other advertising image would open a list of nearly stores.