I'd like to send a text message using ShowComposeSmsMessageAsync (which shows the messaging app) and once the user tap the send button, I'd like the app goes to foreground again automatically.
Is it possible to avoid a user action to come back to the app?
Related
We have an Openfire XMPP/Jabber server setup (with a NodeJs backend and React frontend).
Chat is a feature embedded in the app (NOT an overlay or window that is always visible). So the user has to navigate to a specific page to access the chat interface.
It is working via websockets and messaging sending is working fine. We have a React frontend.
The challenge is that XEP-0333 Chat Markers is not supported by Openfire (the spec never become production ready).
Therefore we need to know how can we implement this feature so that :
A users knows when they are online that they have an unread message (and later, how many unread message they have). For example, if they are not in the chat window and messages are arriving, we need to indicate that in the header of the app so they see it)
if a user goes offline, and comes back online but NOT into the chat window, how can we know if they have unread messages and notify them of that?
My understanding is that somehow we have to keep track of unread messages (eg perhaps in indexedb or local storage or even in postgres backend) and after the user reads a message, we delete it from storage. If the storage still has records for that user then clearly those are the unread messages.
Obviously we don't know if they actually READ the message, but we can assume that if the chat window is open and visible (ie. active tab in their browser) that any messages delivered have been read.
So if our application tab is active, but user is not in chat, and a message arrives, we store it. When they open chat and click on the sender, we remove it from storage.
Has anyone solved it this way? (looking for links to React or JS/TS code)
Is there a better way? (links to other solutions would be helpful, esp. code)
I have a web application using NodeJS, Express, and MongoDB. In my application, I have a view, that can be seen by anyone who accesses the application. That view is rendered with a different image, depending on which a user selects to view (they do not need to be logged in) ie the view is mapView/mapId.
Now, I want something similar to notifications to occur in realtime for those that are on that page. When a specific event happens from an external source, I want to display a popup on the view to which the event belongs to. So the event may only belong to one mapView/mapId and not another mapView with a different ID. All users on the same mapView/mapId should see the notification. Remember, these are general users that do not need to be logged in.
I am researching into Socket.io because I know it is for making realtime applications. But I am wondering if this is even the right way to go. How will I send data to the correct mapView/mapId?
Check out what your server can do with rooms
The idea is that each of your connections, from a particular view, is joined to a room. Then you use socket.io from the server to send a message only to that room. And only those sockets will get the message.
I've created a very simple chat (one to one chat) which works by just sending TCP-packets. The way it works at the moment is just by sending and receiving messages in the terminal. I would like to create a simple GUI that shows dialogs (modal i think it's called) in Gnome like in this picture:
Gnome Modal Dialog Chat
In other words just an application that runs in the background that pops up a modal if you receive a message, and then you can type in an answer and just press enter to send it.
Does anyone have an idea how to do this? Any examples of this online?
I know how to send notifications to my iOS devices through PushSharp. However, once I do and the app is inactive, I am looking to find a way to handle the push notification once the app becomes active again.
In other words, I want to be able to see what item they clicked on and be able to show data relevant to that.
Here is a link for reference, it does what I am asking for, but only when the app is active.
http://roycornelissen.wordpress.com/2011/05/12/push-notifications-in-ios-with-monotouch/
Whats the problem?
You have two scenarions:
Push-notification received when app is not launching. If use tap on notification, app will get data in FinishedLaunching handler;
Push-notification received when app is launching. App will get data in ReceivedRemoteNotification handler.
Article in your question shows that processNotification is the same in both scenarios. It shows how to read alert (text)/badge (count)/sound fields and your own custom payload.
I'm building an iPhone-app in which the logged in users can chat to each other. It's very like the Wordfeud chat for example. You click a user and a modal view controller shows up where you chat.
I have set up a push notification server that works, I just need to know just how I should use it.
When the chat view controller is open I poll in the background with ASIHttpRequest every tenth second to see if a message has been sent from the user you chat with. This works perfectly fine.
But what happends when i close the chat view controller to do something else in the app. Should I create a ASIHttpRequest in every single view controller in the app to poll for new messages or is it here the push notification service takes over? Even though the app is still open?
Or shouldn't I send push notifications when the app is running, only when it's not running?
If that's the case I guess I have to send a request to the server which says that the app is has now been closed (here is a problem if the app crashed out of the blue).
I would be really greatful for some guidelines here, I have searched the web but there are old discussions which confuses me, and some new ones where many people says different.