If we assume the user has not started your app, how do you send/push news/updates?
For instance, imagine the user installed "shops-in-your-area" app and set some option to inform the user when new shops launch... But the user forgets to run the app. How do you auto-launch and/or auto-check for news to show them inside Android?
I'd suggest you start by looking into Google Cloud Messaging. You might have seen it referred to before as 'GCM'. http://developer.android.com/google/gcm/index.html
This should provide all the functionality you require.
Related
In an ionic4 hybrid mobile application.
We want to show a "Maintenance message" pop-up on our mobile application launch. Can we configure this kind of message from play store developer account?
This popup should appear like the pop-up we see for any update notification for an app.
In the sample image below, how to configure the pop-up content and action?
We are very new to mobile application development, any inputs around this will really help us.
You can't configure it from the play store developer console.
What you see obove is the In-App updates feature of the play-core library. If you want exactly that, you would need to implement the library and use the provided AppUpdateManager which helps you handle updates, showing the dialog and so on.
Allthough I don't know if you can easily use the library with Ionic4.
You can also implement the solution yourself. Make an API call to your server and send the current app-version. Your server can then send back update information and tell your app if a new version is available. In your app you can then decide to show a dialog and guide the user to the play store.
I am trying to build a simple app which can be triggered by google assistant.
Like if the users say, "Hey Google, Open TestApp" or "Hey Google, perform xyz from TestApp".
What would be the best approach? Dialogflow?
Saying "Okay, Google - do [something] with [your app]" in order to open your app to fulfill a query is called a Google Voice Action and you can add these to your app quite easily. See the documentation here for full details. Keep in mind - for these to work, your app does need to be in the Play Store, uploaded as a beta at the very least.
The Google Assistant is a little bit different - it's more conversational and doesn't take the user directly to your app. Instead, it takes the user's input, looks for the appropriate app to handle the query, feeds the query to your app, and then returns the response, within Google Assistant itself. This is all about having a conversation with an app, from the Google Assistant, without actually opening up your app.
I have been recently looking into the google home hardware and would like to build an assistant app that communicates between the google home hardware and an app on the users device, so far what I have been able to find is that an assistant app can be built that works with a webhook to a backend but not directly to an app on the device which is what I want, is this possible or has this capability not been added as of yet?
Such a feature does not exist, nor is it really likely to exist in the future in the way you describe. Google Home is just one device that supports the Google Assistant, and many of these others have other setup and linking abilities and requirements.
You don't indicate what your use case is, but it sounds like you might want to investigate Account Linking which will let your Action key data (such as commands) against your user's account id. You can then use something like Firebase Database or Firebase Cloud Messaging to update data or trigger an event in your app.
I have a Facebook Android application, and I need to notify my application users via Facebook when I publish a new update to my Android application, Is that possible? And how?
Knowing that according to this Facebook documentation I can get my Facebook application to notify a user with a message up to 180 letters (Following the recommended UX), but here's my other problem, I don't have my Facebook application users IDs, and of course it would be very hard to manually send a notification to each user (In case I have their IDs, and I don't).
https://developers.facebook.com/docs/games/services/appnotifications
To sum my question, does App-to-User notification could achieve what I want or I misunderstood its purpose?
P.S: I know you may say, why would you want to notify your users that there's a new application update where Google play will notify them.
Simply, my application and its updates being distributed via different stores and some of them are web based which will not notify the user, plus most of users may not pay enough attention to Google store apps updates notifications as they pay attention to Facebook notifications, along with the fact that users uses Facebook many times a day, while the majority of users will not open Google App Store in a long period.
I like to implement Refer a Friend functionality in my mobile application (Android and iPhone).
User "A" will refer my mobile contacts via SMS (Referred user "B"). And if "B" install my referred application or the referred content, "A" will earn some reward points.
This is my scenario. Suggest me.
Thanks in advance.
I used Google Analytics Campaign to implement this scenario.
Another way to do this is to generate unique links for all your users, that they can then send out to their contacts.
Let's say User A shares a link with User B. When User B clicks on the link to get your app, rather than immediately redirecting to the App Store, you can make a call to your backend, with the goal being to create a digital fingerprint. Your backend can record the digital fingerprint then do a 301, 304 or 307 redirect to the App Store.
To create the digital fingerprint, your backend can then make a browser-based digital fingerprint including:
1. IP address
2. OS
3. OS version
(These can be grabbed from the request headers).
--
Later when the user opens your app, you should send up the same 3 things, IP, OS and OS version. If they match and are close time-wise, you know that they came from this click from User A's link! Then you can give User A a reward and thank him for getting User B to download the app. This is what we do at Branch Metrics, where I work. We also leverage a browser cookie that works across apps, so that we don't need to rely on fingerprinting except for the very first time we see a user in any of our apps.
You should also think about preventing fraud. You should prevent User A from referring himself, you should prevent User A from referring User B over and over, etc. This is something we work on everyday as well. Definitely spend time on fraud prevention unless you really don't care about giving out duplicate rewards to the same user. Please leave a comment if you'd like more info.