I'm trying to develop for Google Glass. However I can't pair Google Glass with any of my devices (my Windows 7 laptop, my Kyocera Event Android mobile phone, and my iPhone 4S). I suspect that the problem is due to the Google Account used in the Glass is different compared to the Google Accounr I use in my other devices. However, I don't know if it is even possible to log out/switch Google account on Google glass.
I'm not sure that is the problem, but it is possible.
There is no way to switch accounts on Glass. I would suggest you make sure any pictures you have on Glass are backed up, do a system reset, and initialize it with the account used on one of the other devices.
See https://support.google.com/glass/answer/3297404?hl=en for details
Related
After getting the Google Fit API to authenticate user and read data on the phone I use for debugging, I sent the debug.apk to my friend's phone to test it. I checked the Cloud Platform console, the API dashboard shows the requests.
However, it is not working on any device except mine. I tried with testing mode on google cloud(all the emails were added as testers), it did not worked. When I publish the app on google cloud, nothing changes, same problem again, getting result code 0.
I would like to know if problem is with google cloud platform or I should wait some time...
I've gone through the documentation of enrolling device one by one using this documentation.
Also I can see that there is another way to do it by calling API from each mobile as given. The description of the same mentions that Instead, you can use this REST API to register an Android device with WSO2 IoT Server, without having to install an Android Agent.
But is there any way to enrol multiple devices in one shot ? Let's say I want to enrol all the android devices which are in my network, something like that ?
Because if company has around 2000 employees, it's useless to call API from each mobile (which will be the manual process) or by downloading Download IoT Server Agent on each mobile and following steps given in doc.
Let me know what strategy we can use to solve this problem ? or I'm missing something from documentation of WSO2-EMM which already solves this problem.
I'm currently working on a assay for a school project about Google Services.
The question is not programming related, but I hope you guys could help me out.
I've done some research and a little bit of digging on the Google Cloud Platform and Google Apps for Work, but before I start to make wrong assumptions in my assay, I was hoping if you could say wether I'm right or wrong.
Is Google Apps for Work part of the Google Cloud Platform? Or is it a whole seperate service?
I couldn't find any connections between the two, but shouldn't Google Apps for Work a service of te Google Cloud Platform?
Thanks in advance!
Tristan
Short: No it's not part of Google Cloud platform.
Long: Google Apps for Work contains products such as Gmail, Google Drive, Google Hangouts, Google Calendar, and Google Docs. You will probaby be familiar with at least some of those. These can all be used by individuals at home, but if used in the 'for work'-context they offer some extra features such as custom domains and support. While these are all running in the cloud, they are not technically part of Google Cloud platform.
Google Apps for Work can be seen as a SaaS-product (Software as a service), while Google Cloud platform is more of a PaaS-product (Platform as a Service). While Apps for work lets you use the software written by Google (Gmail, docs,...), Google Cloud Platform allows developers write custom applications which run on the Google cloud.
Applications written on Google Cloud Platform can however be used together with the Apps for Work part. For example you could use your Apps for Work account to log in to a custom application written on GCP, or you could access your emails or from within your custom application stuff like that.
Small note, GCP also contains stuff like Google Compute Engine, which is more of a IaaS (Infrastructure as a service). However this will still be used for custom development by the user, but it gives the developer more freedom.
We have an existing Android and iOS application that consumes REST API from our servers. The API provides a token to the authenticated users after they log in using their credentials (username, password combo.) from the mobile applications.
Now, we're planning to create a Google Glass application for the same. In this case, we'd like to use the existing REST API along with Glass also. The Glass app will be built natively using the GDK.
My concern is, how would the users be able to input credentials? Because, users may have signed up for the service using non-google accounts?
Many thanks in advance.
At the moment, there is no supported way for apps made with GDK Early Access to authenticate the user or provide a way to connect the Glass account to your auth system. The Glass team has indicated such methods are coming, however - the Strava Cycling app, for example, does this, and it is expected that a similar feature will become widely available as the GDK matures.
Strava Cycling appears to get its credentials at the time you setup the app through MyGlass. When you turn it on it redirects you to a website to log into Strava's service before completing the install.
I just gave a talk on this exact topic at Wearables DevCon. The solution I proposed is purely done through GDK. All the user has to do is sign into their Google Account on a phone/tablet/computer and enter a code that is shown on Glass.
Check out the slides here:
https://docs.google.com/presentation/d/1NepYwlKdEvLV0QH9ix2I8l-JY1kHjBR9AXKBNpgTI6g/edit
And the code here:
https://github.com/victorkp/GlassWebNotes
The latest Glass release (XE16) publishes the remote authentication API for apps distributed through MyGlass:
https://developers.google.com/glass/develop/gdk/authentication
Is there a way I can leverage the Google APIs to get a report on Google Voice usage in my domain? We just turned it on and wanted to see if any of our users were using the service.
Google Voice is not a core service within Google Apps and does not fall under Google's SLA. There are also no official APIs that allow access to Google Voice data. There is however at least one unofficial Python library to interact with Google Voice programatically.