Hybrid app in Google Glass - google-glass

Is it possible to build a single app that can work as native(GDK) and also insert cards into my timeline with Mirror API. Or i have to build separate apps for GDK and Mirror API.
I am aware that we can invoke a GDK app from a card inserted through Mirror API. But these are
in essence two different apps interacting.
So is it possible that i can do the whole authorization through GDK app?

It is certainly feasible to have a GDK-based app on Glass call the Mirror API to insert a card. Calling the timeline.insert endpoint is not a big deal. You will have bigger issues if you're trying to handle callbacks since you'll need a stable IP address, but if all you want to do is insert cards with a URI to use as an intent trigger, that part is not an issue.
The issue you face, as you noted, is to do the authorization through Glass. This part is still immature in the GDK, and although there are some workarounds, there is nothing that Google provides yet that can help with this. Auth support is quite frequently requested, so expect something to address this as the GDK matures.

Related

Stacking reviews - Project to create a health virtual assistant using Dialogflow

I am working on a project to create an online medical booking system using Dialogflow as the frontend to provide users with a more personable experience.
So far I have come up with an ideal stack PIC. I plan to have it hosted on AWS (or GCP). However, I am new to Dialogflow but I know it is a very powerful platform. My two criteria are: (A) A stack that makes it easy to personalize frontend UI display and (B) Scalability, I am starting with a web app but would like to also develop an iOS app.
I have two questions: (1) Would you change anything in the stack? and (2) Is there a way to change the name of the bot each time user visits (to make it more "real")?
Super appreciative of you guys expert opinion :)
IMHO, I've found GCP to be easier to use than AWS, since Google handles SSL encryption with .app domains, while AWS requires a more manual solution. Google Cloud also offers a terminal window inside a Chrome tab, which can be a fun experience. So, for hosting, I recommend Google Cloud, unless AWS has a unique feature that applies to your personal circumstances.
Personally, I prefer Angular to React, but Angular, React, and VueJS are all fine choices for a front-end framework on a web app. Your choice of these probably depends on which framework you already know, or (if you plan to outsource development) which language you can use to hire better engineering talent.
For my own projects, I use Express and Node on the server side, instead of GraphQL and Prisma. Your call there.
Good luck!

Server Side / Cloud Coding for the app?

I am am making an app for iOS & Android whose frontend UI is ready. Now I wanted to learn some server side coding to connect my backend with Amazon services.
MY app will feature 1.image upload & download 2. storing of data and meta data 3. user registration and stuff
I have no clear idea about server side and cloud coding ? so want you guys push me a bit from where should I begin and how should I begin to make the above features for my app working ?
It sounds like you are looking to do mobile app development that works with cloud datastores.
Here are a few blogs that you can take a look at get started with:
http://mobile.awsblog.com/post/TxERCU1UMRFNPB/DynamoDB-on-Mobile-Part-5-Fine-Grained-Access-Control
The above blog post talks about using AWS Mobile SDKs with DynamoDB. In general, mobile.awsblog.com has more resources for developing with other datastores and might be a good resource. For DynamoDB's support for enabling mobile developers to build serverless architectures, please take a look:
http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/FGAC_DDB.html
Hope this helps.
Swami
If you have no clear idea about server side coding maybe you should use a backend-as-a-service platform such as Backbeam. These platforms give you SDKs for iOS and Android typically and you don't have to worry about the servers stuff. You can create a database in the control panel and start using it from your iOS apps making queries, inserting data, etc. You have also other features such as push notifications, users authentication, and more.
Disclaimer: I work at Backbeam. Other well-known platforms are parse and kinvey

Locate Glass's location on Google Map

Is it possible to have Glass do a POST on it's current coordinate to the server while running other apps, say, Google Hangout or take a picture?
Is there any example or APIs I can leverage?
If you are using Goggle Glass GDK, you can use an AsyncTask to to do work. If you are using Mirror-API, then that is a separate app, and it can work simultaneously (see GlassWare Fieldtrip).

Take a picture and share it with one voice command using Google Glass Mirror API

I just started using the Mirror API with a PHP web server. Is there anyway to integrate a voice command with my app that when said, Glass will take a picture and automatically share the picture with my server?
From what I read so far, it doesn't seem possible to access the camera with anything other than the default "Take picture" command. I also don't see a way to have Glass commit two actions (in this case take a picture and then share it) with one voice command. Is there any way to do the above with the Mirror API?
This isn't possible with the current features provided by the Mirror API. If this is a feature you're interested in using, file it in the official issue tracker.
However, you can implement this functionality with the GDK.

What is the difference between Glass Mirror API and Google GDK?

What is the difference between Glass Mirror API and Google GDK?
Google has announced the GDK here: https://developers.google.com/glass/gdk
but they haven't exposed any new features specific to Glass yet. How do we actually use the Google GDK?
Looking at the examples listed on the above link, we can create APKs, load APKs onto Glass and launch them using adb shell but is there a complete app or example anywhere?
The difference between the Mirror API and the forthcoming GDK boils down to where the application being written will run.
The Mirror API specifies how a web-based application will communicate with Google's servers to send updates to a user's Glass and how it will receive notifications when the user takes an action (such as a share, or a location change) that is directed at the Glassware.
The GDK is intended for applications that will run on Glass itself and have more low-level access to the sensors and to the underlying Android environment that Glass is built on top of. Google has not released the GDK yet - that page is where it will be released, and provides some early "getting started" concepts for developers who are interested in building native apps that run on Glass.
GDK has not been launched yet, so you cannot actually use it right now.
GDK will allow you to work directly on the Glass device using your Android development skills whereas Mirror API is a cloud/web-based API for interacting with a user's timeline only. See Prisoner's answer for more detail on this.
Because GDK has not been released yet, "complete" apps and examples do not exist. There are three samples (Compass, Level, and Stopwatch) listed on the link that you posted. The page says that these samples will eventually be updated into a "full Glass experience" when GDK is launched.
When we launch the GDK, we'll also update these samples to show the migration path from a traditional Android app to a full Glass experience. Make sure to check regularly for updates
Glass Mirror API is for developing the Glassware(Pushing Webcards from server to Glass).
Google GDK(Glass Development KIT) is similar to current Android SDK, but they will have some special tool that will help develop Android Apps for google glass. Even now without GDK, developers are developing apps using Android SDK.
GDK will allow you to run apks on GLASS along with the GlassHome. GlassHome is the main display that you see within GLASS. If you install an APK without the GDK, the only way to get to it is using something like Launcher2.apk. With the GDK, and this is an assumption, your apk will be represented as a card within GlassHome.