I would like to create an Android app that is basically a chat.
I have read many articles on the web until I found QuickBlox.
(I admit I didn't understand exactly how it works and how to use it and I'm new in mobile app develiping).
I am following this tutorial and now I should download the sample code.
I saw that there are different types:
Simple Android Chat code sample
Simple Android WebRTC (VideoChat) code sample
Simple Android Location code sample
Simple Android Push Notifications (Messages) code sample
Simple android Custom Objects (key value data store) code sample
Simple android Users authentication code sample
Simple android content storage and update code sample
I would like some advice on which is the best in my case.
My app is a "simple" chat app that allows a registration (for example, using social networks like Google+ and Facebook) and orders the users based on proximity.
So if the user X is located in Paris, registered users will see the app in order of proximity (eg before those who live in Saint-Denis and then those live in Orleans).
For the moment I'm only interested to send/receive text, not multimedia content such as photos and videos.
So I'm undecided whether it is better to use between "Simple Chat Android code sample", "Simple Android Location code sample" or "Simple Android Push Notifications (Messages) code sample".
From what I understand, push notifications can be added at a later time, or am I wrong?
I hope I have said all that is necessary for the selection..
Thanks for your suggestions
You will need all three in order to do what you want:
Simple Chat Android code sample - helps with almost everything involved in normal chat applications(send and receive messages,emoji support,typing status etc). However it doesn't include multimedia messaging and push notification support.
Simple Android Push Notifications (Messages) code sample - basically shows how to send and receive push notifications. Which can be added anytime you want. The chat will work fine without it.
3.Simple Android Location code sample - shows how the location api works and can be used for what you described.
Hope this helps.
Related
Please I want to create an online or offline feature for users in my app
I tried onDisconnect in Firebase and it didn't work for me
You can use socket.io for flutter. When user open the app then socket will tell the server that specific user is connected.The user able to see other connected users. Here is a article of how to use socket.io in your project.
You can try pusher presence channels.
It is based on websockets, and it tells you who is connected to the channel (who is present). You can find the use cases for presence channels here.
click here to find out how to build presence channels.
I'm currently building an online and offline statusbar for a flutter app if a user is connected to a presence channel. If I have the working code I'll post an update.
How can I implement WhatsApp/Telegram like call notification when the flutter app is in the background or cleared from the recent task (clearing ram)? Can anyone let me know Exactly How to do this?
There is a great youtube series on this exact topic. In the series, a YouTuber by the name of the CS Guy creates a clone of Skype. I've placed the link to the video where he explains how to create a pop-up screen when a user calls another user, however, you may need to watch the previous videos within the series in order to get everything working. Its quite long but I recommend you watch the entire thing. In terms of displaying notifications when a user is called, I recommend you watch a video by Fireship listed below. In the video, he explains how to send notifications in the background when a certain event occurs in Firestore.
I can't explain the entire process in detail to achieve what you want but I can give a general overview of what you would need to do.
Watch the video/entire series by the CS Guy and complete everything
Learn how to send push notifications in firebase from Fireship
When a new document is created within the calls collection (You will understand once you finish the cs guy series) trigger cloud function.
Find the uid of the receiver of the call within the cloud function and grab the user's token from Firestore.
Finally, send a notification to the receiver telling them about the incoming call.
CS Guy:
https://youtu.be/v9ngriCV0J0
Fireship: https://youtu.be/2TSm2YGBT1s
I have done the exact same thing in my application and can help you out if you need further assistance, however, please go through both videos/series first.
You can use the flutter_local_notifications plugin with the firebase_messaging plugin.
From the documentation of the flutter_local_notifications plugin;
[Android] Support for the following notification styles
Big picture
Big text
Inbox
Messaging
From the documentation of the firebase_messaging plugin;
With this plugin, your Flutter app can receive and process push notifications as well as data messages on Android and iOS.
I am wanting to develop an app similar to 'Notiduino' where it takes android notifications such as whatsapp message notifications or missed calls and retrieve them within the app. Is there any lib for this function? I searched and found nothing ...
Sorry for my bad english
Yes. You can use Overlay widgets. Combining them with a little bit of animation will give you effective UI. One example here and another is here.
You can also use Firebase in-app notification. Using Firebase in-app notification has one more advantage. You can also send push notifications from the same firebase project. Of course, relevant settings have to be made. Having said that, there are a bunch of web pages which will guide you through the step by step process.
Have anybody heard of some opensource, or one that can be bought, client-side (web, android, ios) chat based on pure pubnub or pubnub ChatEngine?
The reason I'm asking is that it looks like PubNub gives a reliable backend, but it doesn't come up with UI that we can just use as drop in replacement for our current chat, that doesn't perform well, and we don't really have time to build UI from scratch.
I found many examples of really simple chats, but it's still a long way from that to fully functional chat that we need to replace.
We have a multi-room chat, with users being able to access only some subset of rooms and also open one-on-one chats. Similar to Slack, but with way fewer features.
Thanks
There is a well-made UI for ChatEngine using Vue.js. The example has 1 to 1 chats which can also be chat rooms. There is a tutorial for building the app with ChatEngine on the PubNub Website:
Tutorial:
https://www.pubnub.com/tutorials/chatengine/vuejs/chat-app/
Live Demo:
https://ajb413.github.io/chatengine-vue-chatbot-1to1/
GitHub Repository:
https://github.com/ajb413/chat-engine-vue
Screenshot:
I need to implement a message service into my app that works exactly like this:
users register with a nickname within the app
they can add contacts (just nicknames) and send them a message by just specifying their nickname
they can send a message whenever they want, and the message is stored on a server until when the receiver connects to internet.
when a message is received, a push notification is triggered.
So, the messages work pretty much like emails, however instead of using email addresses, we only use usernames. I'm also going to build my own back-end for it.
Which APIs should I use or which 3rd party framework can I use ?
And any tip ?
N.B. I need to make it work with iOS 3.0 as well.
and in the future I will develop an Android app, so the nicknames should be unique and I should be able to send messages from iPhone to Android devices within the same app.
thanks
I've successfully used the Three20 library and would recommend giving it a try. It's an open source spin-off originated by the author of the Facebook app. It features a bunch of additional GUI components that might be useful to your project, like a message composer that resembles the one used by Apple's email app.
Also, Three20 features a nice framework for handling navigation within your app. Currently, the biggest drawback seems to be that certain features don't play well with the iPad API.
The answer seems to be Push Notifications