Developers Say They Don't Have Enough Access to Internal Programming of Google Glass
Flying blind, they say
Ever since developers got their hands on Google Glass earlier this year, software coders have clamored for greater access to the programming internals of the controversial headset. Google accommodated them this week -- albeit to the sound of muted applause.
To be sure, Google's Glass Development Kit (GDK) does fill in a key puzzle piece that had been missing from Google Glass. Yet many developers are worried. They say that in the absence of more leadership or more access from Google, they're being asked to figure out the final picture on their own -- knowing that it might change by the time Glass gets mass produced.
Editor's Note: As of February 29, 2024, commenting privileges on reason.com posts are limited to Reason Plus subscribers. Past commenters are grandfathered in for a temporary period. Subscribe here to preserve your ability to comment. Your Reason Plus subscription also gives you an ad-free version of reason.com, along with full access to the digital edition and archives of Reason magazine. We request that comments be civil and on-topic. We do not moderate or assume any responsibility for comments, which are owned by the readers who post them. Comments do not represent the views of reason.com or Reason Foundation. We reserve the right to delete any comment and ban commenters for any reason at any time. Comments may only be edited within 5 minutes of posting. Report abuses.
Please
to post comments
I agree but what are the alternatives of it? First of all I would like to say Developers trying hard given their level best...Check out their works like Google apps security