I am creating a web app that needs a customer to confirm from his mobile phone. Exactly the way google two-factor auth works. Or another option is the USSD popup on the customer's phone like the way primer bet does.
What do I need to come up with like that?
Related
I have deployed an Alpha version of my app and supplied the email address of a tester and received the opt-in link the user can use to access the Alpha app. In typical fashion, Google gives no instructions for the user, who clicks on the link and promptly gets an error message that no Google or Stackflow search throws any light on.
A further Stackflow search reveals a complex procedure for an Android phone involving copying the opt-in link to Google Notes, pressing on it, and then taking the option to open the Google Assistant app. It would be difficult to find a better way to discourage testers.
Also, this only opens the app on an Android phone. No mention of how the 20 testers can access the Alpha app on Google Home or Nest Mini. Frustrating when the app is specifically designed for use on Google Home or Nest Mini and not on a phone. Does anyone have a solution?
Users need to opt-in to the alpha program on the phone by following the link. (They shouldn't need to copy it, but they will likely need to open it in an actual browser such as chrome.)
Once they have opted in, however, it will be usable on any device linked to the same account on your approved list and that they used to accept.
I am experimenting with Google Smart Home. My end goal is to receive home control events, such as Turn the lights in the living room on, in my Dialogflow fulfillment service.
I am wondering if it is possible to develop and test Google Smart Home without actual devices. That is, it would be great if I could configure a Google HomeGraph configuration via browser and verify Google Smart Home actions via the console (console.actions.google.com).
Is this possible and practical?
No, currently it isn't possible to test smart home devices with the web-based Simulator. You will need to add the device using the Google Home app on your phone and can then test it using the phone's Assistant.
As an aside, you also can't develop it using Dialogflow directly - you'll need to use the Action SDK. (You can relay it to Dialogflow if you want - but since you just get events and not conversation, it really doesn't help you much.)
We plan to manufacture a device that we want it to communicate with Facebook. If the user presses a button on the device, we want something to appear on users wall as a post. It means that the device will post on behalf of the user on Facebook.
As we see from the Facebook developer page, the types of applications are a Facebook app, a web app or a mobile app. The thing we have just explained does not belong to any of these categories. For instance, it is not a web app because the device does only support http connection but does not have a built-in web browser. It is not an Andorid or iOs app because the operating system in this device is none of these.
What would you suggest for this kind of application?
Thanks in advance.
Definitely look into http://developers.facebook.com/docs/authentication/devices/
Your other decent option would be to run an HTTP server on your device that users could connect to from a computer or phone to authenticate.
Once authorized, a simple HTTP request is all that it will take to share anything.
Edit: Just noticed that Facebook is no longer accepting applications for new partners with the auth device pattern. This is definitely what you want. You could try contacting them anyways.
Possible Answer = make it web app but dont forget the facebook policies about the user privacy issues. Your device can send a signal to your server and server can make the post i think it is possible (hmmm but to acquire access token again your clients have to login your webapp again every 60 days, there must be a better solution)
I am also working on similar problem
I have a prototype device for jogging wrist band and I am trying to post a wall story about number of steps in current day and the tempo on behalf of a user by just clicking on a button on the machine when it is connected to wlan or android phone in a wireless fashion.
Hi gentlemen (and gals)!
I'd really appreciate any insights here....
We all know bout the in-app popups that say "Confirm if the XYZ app can use your location" or other things. These are like windows of notices that pop up in-app.
I'd like to be able to 1. choose a user of my app 2. send them a in-app popup message of my choice anytime... ALL done from server-side after the app is already distributed on the Appstore
Hypothetical example ....So an example of this is i can see a user who has not filled out their profile and we (from admin side) can send them a in-app popup that says "User, please fill out your profile!". Just an example.
Client-side wise.... What would we need to do in XCode (what libraries, etc) before we submit it to the appstore? To allow our serverside to do this anytime later?
Thank you very much!
It's call "Push Notification" that you can choose specific user with device UDID.
You can also study from these question.
I am creating an iphone application that requires the users to have an account at my website.
But if i have to distribute it through apple store, how should I make the users of this Iphone Application first create an account with my website. There could be a few options like :
1) Ask the user to create an account when he/she tries to run the application on iphone.
2) Provide a 'Sign-Up' page in the Iphone application itself.
My question is "Is there any mechanism provided by Apple Store to make the user sign-up to my website before he/she can download the application".
Kindly give in your suggestions for the same. Which would be the best approach for solving my problem.
Thanks,
LG
There's no way to do this through the app store.
Yes: your two options are to create a sign in / sign up screen with cocoa, or to display your login webpage with a NSWebview.
I'd recommend the native control route...
No, you can't do that through Apples App Store.
You could provide the user with aviability to register to your site when opening your app, throug, say a NSWebView.
There are many ways to solve this, just not the one you might like.