Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm looking for a simple messaging server which I can run on my server which will be used to register clients when they are online so they can "talk" with each other (kind of WhatsApp service but much more lightweight). The clients will be Android and iOS devices so I need a compliant client side as well.
The best solution I came up with is XMPP server but I'm not sure that this is the best choice and I'm not familiar with other possibilities.
What do you think about XMPP: is that the right solution or are there any other options?
ThX!
XMPP is a complete open standard IM protocol with a lot of features implemented besides messaging and presence (via XEP - extensions).
There is a really wide range of opensource servers, clients and libraries as well. So it is relatively easy to develop applications based on XMPP.
Other IM protocols are listed in this complete comparison table:
https://en.wikipedia.org/wiki/Comparison_of_instant_messaging_protocols
So, IMO XMPP is a good choice to implement Android/iOS apps.
XMPP is a good option, especially as many of the features will be already built into the platform.
However, there are many other possible approaches, depending on the actual design and feature list of your platform. You could decide to rely purely on Websockets for example to build channel based group chat. You could even decide to build your own basic protocol if you only plan to have a few features.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I already knew the basic of android programming. now I want to build a offline multi-user chat application. I found peer-to-peer and Bluetooth are the most used techniques to communicate each other. I need to know,
Which one is easy to begin with among P2P and Bluetooth?
I already built a Bluetooth chat application using online tutorial. That method is a communicating between two endpoints. Is it possible to make it more than two?
Which one is easy to begin with among P2P and Bluetooth?
It depends on your previous skill and expertise. As I have seen that you have already managed to create an application for p2p communication via bluetooth, so of course it is easy to begin with bluetooth.
I already built a Bluetooth chat application using online tutorial.
That method is a communicating between two endpoints. Is it possible
to make it more than two?
Yes, it is possible. There are a lot of tutorials in the internet of connecting multiple bluetooth devices. Please check this SO answer.
However, chat application based on bluetooth is not a good approach. If this for your learning only, then from my point of view this is fine. If this is a professional project, then I would suggest you might consider looking into other options. Check this tutorial which uses Firebase as well. Using firebase for real time chat application will definitely serve your purpose.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I'm relatively new in mobile development, but I'm really familiar with HTML5. I have a project, wich will be used in pubs, where the customer orders the bar through his cell phone. Some informations:
The bar will have a local server to receive the requests (it will work in local network)
The clients application will have live a chat, so the customers can meet new people in the same bar :). However, the chat server will be online (the customer will need internet to access this functionality)
The application will likely use push notifications and maybe perform some simple background processing.
The application should be Cross Platform.
So what would be the ideal technology to use? Cordova? PhoneGap? Intel XDK? Xamarin? Embarcadero? Should I also use WebSockets?
Thanks!
So phonegap/XDK is really the same a cordova and they're all fantastic. Phonegap and XDK are just... implementations of Cordova. Phone gap can do everything you want it to. I've used phonegap to link multiple phones to a server(and each other) for a grocery deals app.
I would hold off on websockets(though they technically can do what you want). They're not the most maintainable or easiest to set up.
I've explored Xamarin a year ago and it looked like it would work for my(and your) applications. However, it seemed to be completely tied to the .NET framework. So if you don't mind being led by the nose for all you're profits...
I have no direct experience with Embarcadero, but I've now signed up for a trial due to this post.
Sources: 2013-2016 Mobile developer---successful and lucrative project completion
I don't have much idea about all the technologies you asked but I have worked with cordova and accomplished all the requirements for your app. It can be a good option. I'm not very familiar with other tech
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Thanks to all for their earlier support. Now these days i am looking for a Framework Which can provide backend support for Android Applications. I found one of them is Parse Here . Although i didn't initiate any implementation based on the same but it seems very promising after once visit their portal, dashboard and documentation. Can anybody describe pros and cons of using such Framework. If anybody have any experience to work upon Parse Framework please share your feedback should i go ahead in the reference. Is it free to start like developing demo Apps. Thanks very much in advance.
The basic plan, which is all you need to get started, is free.
The most important reason, in my opinion, to use a service like Parse is that you can focus on your app, and what's special about it, and let someone else make sure your backend just works. A service like that will scale to whatever number of users your app gets (providing you design it correctly). The API is also quite similar between the platforms they support (like Android, iOS etc) so that the backend does not create obstacles in the event you need to port your app to other platforms.
You also have the advantage that the API is so similar to the programming you're already doing with your app so it fits very well with your existing code.
Just make sure you design your backend with a NoSQL mindset and don't fall in the trap of trying to implement a SQL-ish model that will not scale. Going through the Anypic tutorial on their site is a good primer if you are not used to designing for NoSQL databases.
Good luck!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have been doing some research to create an IM application. I saw many sample codes and still trying to decide which method to use. Before starting development I want to ask your opinion if anybody knows how popular IM applications such as Kakao Talk, Line, We Chat, WhatsApp work.
I saw some articles saying to use Google Cloud, and some articles about using XMPP.
I am a kinda new for Android development and before starting development I want to see all my possibilities and choose best method for that.
Thanks for your time.
Well, I would presume they don't all work the same way. There are different techniques one can use to implement a chat client. Each of these companies might have their own proprietory technologies depending on their scale, user base, finances etc.
2 popular options you can check out are :
XMPP - It's supported by most major chat clients and is used by the likes of Facebook (a customized version of it anyway). asmack is a popular XMPP library for Android which might be useful to you.
A Backend-As-A-Service (BAAS) provider like Parse. This will save you a lot of server side heavy lifting and writing backend code like you would have to do if you were considering something like AWS
If this is a learning project, I would suggest implementing a very simple client and writing both the server and client-side code so that you know how the whole stack works. Hope that helps!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I was wondering how people generally realize backends for either complex data-synchronization ("cloud"-sync, since everyone seems to love that word) or simple user-management when developing mobile apps for iOS an Android. I'm not much of a web-guy, so I'm sorta clueless here.
What's your system of choice? Is everyone just writing custom solutions in Ruby, PHP, Java Servlets... which return JSON via HTTP (HTTPS for confidential information) or is there any standardized framework out there that I've been missing? Especially in combination w/ databases - apparently, you need to store the information somewhere.
Sorry for the very general question - but I'm not really sure where to start refreshing my knowledge here.
You can try Parse.com as a backend solution.
If it is simple application I use parse.com. If I need more flexible backend I use Ruby on Rails.
It's so simple to get started with a mobile backend these days that you should really give it a shot.
Kii Cloud for example supports data and file synchronization and user management including support for Facebook and Twitter accounts and has a generous free tier with carrier grade scalability and reliability.
From all the research I have done Parse or Kinvey sound like the best choices. I was about to build out my won backend out of pure ignorance but after researching thee tools I am going to go with one of them. Kinvey has a pretty cool estimation tool that demonstrates how much time you will save: http://www.kinvey.com/app-cost-estimator
Hey why reinvent the wheel.
Built.io's Backend https://www.built.io/products/backend/overview is my backend solution of choice, its such a simple and straightforward tool to design and build apps.