Review: BioSport™ Biometric Headphones with Heart Rate Monitor

by
SMS Audio BioSport Headphones

When I attended IDF 2014 in San Francisco, one of the most prominently hyped products was the then-forthcoming BioSport™ earbud set with integrated heart rate monitor. There was an impressively large and aesthetically awesome area of the Moscone Center dedicated to it. The headphones, produced by SMS Audio, were featured in the keynote and even Google co-founder Sergey Brin made a random appearance to participate in some yoga as part of its promotion.

For attendees, the coolest part came during the keynote when it was announced we'd all be getting these $150 headphones for free. Months passed with no word, but right before the Christmas holiday a mysterious package appeared on my doorstep. Inside contained the message: "As announced during Brian Krzanich's opening Keynote, and as a thank you for attending IDF14, you are receiving your own pair of SMS Audio BioSport In-Ear Headphones, powered by Intel.  The in-ear headphones include a heart rate monitor so you can listen to music and monitor your heart rate at the same time." Read Full Article

Verizon Ellipsis 7 (QMV7A) Development Woes

by

A couple years  ago I decided to switch my cellphone provider.  On Black Friday, Verizon Wireless offered a "free tablet" deal upon activation.  It was the same sort of persuasive deal many carriers offer throughout the year, almost always requiring a two-year activation commitment for the tablet itself, on top of the regular cellphone contract.  The tablet was their own branded Ellipsis QMV7A 7" (by Quanta) with so-so hardware specs. (I had, in fact, just been gifted the all new 7" Kindle Fire HDX a week prior as part of an Amazon promotion, and the QMV7A was light-years behind it in resolution, technical specs and overall build quality.)

As I sat waiting for hours on end for the recently hired Verizon staff to activate my service, I checked the going rate of the QMV7A tablet online; $130 at most. Verizon promoted it as a $250 tablet, and with the two-year contract this "free" tablet would actually cost me about that much given the $10+ a month service charge.  The data plan was shared with the main phone as well, so there was no extra data allowance.  Still, I saw some value in owning another Android tablet for development purposes and agreed to the commitment. Read Full Article

Apple Muncher Project Postmortem: Developing for Panasonic VIERA Connect SmartTV (Part 2)

by

This is the second of a four-part story documenting my somewhat excruciating and wholly uncharted experience developing an indie game for Panasonic’s obscure VIERA Connect television app market.

In the first part of this postmortem, I detailed the pains of becoming a VIERA Connect third party developer and struggles of setting up the rigid development environment required by Panasonic. Now I turn my attention to the actual development process using the company’s available API. Read Full Article

Synchronizing Local Databases and Web Content via Dropbox (MySQL, Apache, WAMP)

by

When working on web-based projects locally, developers are often faced with the burden of transferring the data across multiple development machines for one reason or another. In my case, I develop primarily on a desktop machine in my office but occasionally require access to the project files from a laptop or mobile device; this is especially true when working remotely or if needing to demonstrate a WIP to a client.

A typical web project consists of many static assets, dynamic scripts powered by a server-side language like PHP, and database-driven content powered by an engine like MySQL. Due to these interconnected components, constantly exporting and importing the databases from one machine to the next while also carrying over all of the updated page scripts and static assets immediately becomes a tedious and time-intensive commitment. Database synchronization can be especially cumbersome when needing to mirror user accounts, table and database privileges and other lower level details. Read Full Article

RIP Original iPad; iOS Device Fragmentation

by

Developer life sure was simpler when I began developing apps for Apple's iOS platform nearly half a decade ago.  My first commercial iOS app was developed while the original iPad still loomed on the horizon. The iPhone 4 had just been announced with its "stunning retina" display that boasted twice the resolution of its predecessor, thanks to a much greater pixel density. From a developer's perspective, creating universal applications 4-5 years ago merely required basic knowledge of Apple's three mobile device variances:

  • iPhone/iPod Touch 3rd Generation and below (320x480; 163 PPI)
  • iPhone/iPod Touch 4th Generation (640x960; 326 PPI 'Retina Display')
  • iPad 1 (1024x768; 132 PPI)

At the time, all available iPhones and iPod Touches shared the same aspect ratio and screen size, so supporting retina displays was basically a matter of producing 2x-sized assets (i.e., a 44px icon on standard devices would be rendered at 88x88 on the retina 2x devices).  Apple enforced the convention of appending '@2x' to the filenames of each retina-made asset to automatically load them in place of the standard assets on supported devices. The iPad used standard resolution assets but had a larger resolution; depending on the app some adjustments would need to be made to take advantage of the added screen real-estate.  Aside from these few considerations, it was blindingly simple to develop for the few available iOS devices. Read Full Article