I'm currently working on publishing my PWA to Play Store; and stuck with Notifications. My TWA makes use of Firebase Push Notifications for Web - and they work fine. The only issue is that user must opt-in to the notifications when using PWA.
However, I'd like to enable notifications automatically whenever user downloads my TWA app from Play Store; and I couldn't find any relevant section in Google's TWA tutorials.
I have zero knowledge of Android development but I'm following tutorials by Google and got the TWA working on my mobile, minus the push notifications.
Can someone point me in the right direction?
Related
I have an a flutter app integrated with Kochava, where Kochava is selected to receive SKAdNetwork data. The app is also setup in facebook so that install campaigns can be run. However, when I select it in campaign manager, I get "The Mobile Measurement Partner app used to configure events for this app doesn't currently support SKAdNetwork events. To run iOS 14+ campaigns for this app, choose a different app event connection for SKAdNetwork in Events Manager.".
In the Events Manager, Kochava is configured as the source of SKAdNetwork events (and the configuration screen is "all green"). Also, on the dashboard I can see "fb_auto_published" app install event from MMP and the app screen shows a date of "last mobile app install" (those are all likely originating from iOS14+ live testing).
I want to avoid integration with Facebook SDK and having Facebook as the recipient of SKAdNetwork data (mainly because it feels like a less clean setup with MMP getting some events and Facebook some - while other networks like Twitter are also integrated).
I have tried replicating this setup under clean ad manager and setting up new app in Facebook (no change - still doesn't work). The Kochava-side configuration has been reviewed by Kochava team and looks good to them. Facebook's business support directs me to developer support but only after "recommended" step of Facebook SDK is completed (which I am a bit reluctant to do).
I'm looking to launch a single web app that works as a PWA for web users and a TWA for users wanting to download it from the Google Play Store. The app includes a yearly subscription so I'll need to implement separate payments methods for the PWA and TWA in order to comply with Google Play policies.
With this being said, is there a way to identify with JS if the user is viewing the PWA vs the TWA app from the play store? Perhaps something unique to check in the global window object?
Or, is it recommended to publish a whole new version of the app used for the TWA to a different URL that only supports the Google Play payment option.
Any info would be great. Thanks in advance.
Google has discontinued Near By API by the end of 2018. Android OS had built in support for Near by API and hence without a custom APP , the device was able to capture the beacon based push notifications.My requirement is as follows:
With Digital loyalty pass on Google wallet, when the end customer enters the vicinity of a beacon , the device should receive offers as push notification. There is no custom app developed . With out a custom app , how to receive the push notifications with just the Digital loyalty pass on google wallet? . Please help with a solution.
Please refer https://android-developers.googleblog.com/2018/10/discontinuing-support-for-android.html
Unfortunately after Google Nearby was discontinued, there is no longer a solution to send notifications to a user on BLE detection without a third party app installed to do so.
The only workaround is to develop a third party app to do the detecting and notifying. Keep in mind that the way Google implemented this was with the Google Play Services app, so an app was still required to send the notifications. (It was just an app that was installed by default on most phones sold outside of mainland China.). And it didn't even work unless a user had opted in, something that few ever did.
Google's Nearby discontinuation basically says Google is no longer willing to use their app to send notifications for you. So you must use your own app or the app of a different partner.
There are other third party apps that track a user's location and send notifications -- such apps are often popular "free" games. But while the install base of these apps can be in the hundreds of millions they do not approach the install base of Google Play Services. These apps can also be a bit "shady" about their practices, and to my knowledge do not have a public policy about how you can get them to send notifications for you or let users opt-in or opt-out.
I have and ionic, cordova hybrid mobile app on play store and i have used OneSignal for handling Push Notifications in mobile app. I have noticed from OneSignal Dashboard, there are lots of "Calypso AppCrawler" entries without Push Token being generated(refer to attached screenshot).
Does anyone knows what are those entries and how do i exclude them from OneSignal Dashboard?
I can't help with the second part of the question (excluding them from OneSignal dash) - but those entries are Google's App Indexing crawlbot, and the devices they are set up with never generate an FCM token.
Is there a way to simulate push notifications by pushing data to mobile safari? Here are 2 scenarios.
I make a web app via phonegap and dont want to use APNS but rather make a web-socket connection and push data to the device myself. On the device end is there a "alert" function I can call to emulate a pop up when a user is not in the application?
Lets throw web app out the window. Is there a way I can do this in native mobile safari? Im not talking about a plain old JS alert window that would only come up if the user was in the app, but be able to do so with it backgrounded.
You cannot run background tasks with mobile safari so for #2 you can't do true push notifications or alerts. However you can send a user an SMS if you have the user's phone number. This can have a hyperlink to a part of your web site (which can contain some sort of payload). You can use a service such as Twilio to help you send SMS'es. However this costs money. APNS does not.
For scenario #1 I'm assuming you're talking about a native app using a phonegap solution. In this case when the app is backgrounded you cannot access any UI at all and wake up the app and show a UIAlert. In fact unless an app is registered for location updates or background music, the app is effectively not going to respond after a set period of time (it only can "finish" certain operations it had started before). So the websocket solution will only be effective if the user has the app opened.
You could register a local notification that runs at some predetermined time which will show an alert. But that is not being pushed from the server so its probably not what you want.
APNS is your best solution for scenario #1. Its not that hard to implement and its pretty inexpensive. Check out urban airship if you want to avoid building out your own server-side components for it.