Firebase In-App Messaging is designed to retrieve messages from the server only once a day, but I would like to retrieve Firebase In-App Messaging messages stored on the server at each app startup.
Does anyone know how to implement this?
Related
I am working on adding support for our cloud storage solution to MS Teams but there is no central server you can send http messages to and get meaningful relies back from. I have no experience with creating Teams apps so I was hoping someone with Teams apps experience could tell me if this is even possible. At this point I only need my app to work on Windows and OS X.
This is how I would like my Teams App to work:
Each member of the team already has our cloud storage app running locally on their machine which provides access to the files.
Within MS Teams the user adds a file reference to a message via a message extension that would result in a link unfurl creating a card that contains an 'Open' button. The URL in the card would be one generated by our locally running cloud storage app. Other members of the team could then open this file by clicking the 'Open' button. The action of the open button would be to send the URL to our cloud storage app that would then open the local copy of the file on that team members machine.
Is it possible to do something like this within a Teams app? The communication between the Teams app and our cloud storage app would be done over our own protocol.
If it weren't for the fact that all bot communication must be done over https rather than http the local cloud storage app could act as the server.
All the communication in Teams with 3P apps needs to happen over https public endpoint. You could use ngrok to tunnel to local.
We have developed an android app, which we wanted to upload it to google play store and have this app to be freely available for the users. This app connects to our API/service which is paid for the users like subscription based. The users are given an option where they can pay for the service. This is not really in-app purchase.
My question is do we need to pay google if the app is free but the service for the app is paid.? Amazon app is free on playstore but the products in app are sold via different payment methods which no where connect to google. I am not sure, if amazon pays to google for such service.
Please let me know. Any help is really appreciated.
WhatsApp just announced a new web application see here.
For some reason, the interface requires the phone to be connected all the time. Is it for performance reasons (not to create additional load on their current servers)? Is there any other constraint that cause that?
The official explanation:
Your session on WhatsApp Web is an extension of WhatsApp on your
phone. WhatsApp Web connects to your phone to sync messages, thus you
can see all messages on both devices. Thus, the first requirement to
being able to use WhatsApp Web is an active WhatsApp account on your
smartphone.
Source: https://www.whatsapp.com/faq/en/web/28080002
As you may know your Whatsapp history is only being stored in a database on the phone itself. To see that history in your web browser, it needs to get it from the phone. Whatsapp could have redesigned it, so that everything is stored in the cloud (as many competing messaging apps do). But that seems to be against their philosophy. They keep it tighly coupled to a (one) phone. As you may know you cannot install Whatsapp on multiple phones using the same account. The web interface is just a remote for Whatsapp running on your phone.
And even though I don't know for sure, I think it's more secure too. It wouldn't surprise me if the data that's sent between the web app and the phone is encrypted in a way that even Whatsapp themselves cannot decrypt. Maybe the QR code is generated client-side (in the browser) and by scanning it using the app there is no need to exchange the keys through Whatsapp's servers. That way they don't ever get the encryption keys and will not be able to inspect the data that gets routed through their servers.
Note: Of course Whatsapp could at any time change their implementation of both the app or the web app and enable eavesdropping.
Scenario:
I'm building a Windows 8 App which is outside of Windows Store. Here I wish to receive notifications using WNS. I have a Publisher which will generate events based on the user action on UI (Ex: Like Uploading a file, Once file upload is completed the event will be generated). I created a internal WCF Service(End Point) which will subscribe to the publisher and listens to the notifications sent by the Publisher. I'm integrating my Listener to WNS service in turn, once notifications are received by the listener, in turn will be sent to WNS Service to process and deliver to specific Device.
Here my question is in order to avail WNS service , do I need to keep my app in Windows Store ?? Is it mandatory ???
And Is their any way to implement push notifications in Windows 8 without using WNS Service????
Please clarify me on this.
Any help is appreciated
Thanks
Karthik Vadla
An app that needs to use the Windows Push Notifications Service (WNS) will also need to be present in the store. For an app to use WNS, it needs to register with the store app portal, which provides an app with a package security identifier (SID) and secret key, which are required to authenticate with and use WNS.
Windows Store Apps that need push notifications can only use WNS.
Traditional desktop applications are not able to use WNS, although they could implement their own version of push notifications.
I have to set up push cloud notification server. I decided to use: http://pypi.python.org/pypi/pyapns/
The question that i have is how to test the server if i don't have an app which will be connected to the server? Is there any sample apps or services that would display the push notification? I just want to send payload using some sort of script and see if sending is successful or not. How people debug such things? Aren't there any kind of virtual env for such tasks?
I do have certificates and ID's of the app, but not the app it self, since the other people are making it. I do not use MAC, or have iOS device. I did read docs from apple.
So eventually i got the right .pem certificate and token of phone with the app-under-dev, phone had to registered as testing one for that app. I just pushed messages and waited for answer unit i got it. Apple do not provide any "easy to use" testing grounds, logs or messages for debugging. Best you can do is to separate pushing service and getting token as much as possible and when you got your hands on app do the raw testing.