How does Kakao Talk work? [closed] - android

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!

Related

How dynamic android application works? [closed]

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 know how to design and develop android application which works offline.But now i want to move towards dynamic android app,which works totally online like facebook,quora,newshunt.Where should i start please give me a way.
Thanks
I personally am completely self-taught when it comes to android, and, well, its been a journey.
For me, a big turning point was
"http://www.androidhive.info/2012/05/how-to-connect-android-with-php-mysql/"
It really gives you a good idea of what it takes to create an app that is connected to the internet, and it isn't hard to implement yourself. Mind you, before, you were working with just android, but once you integrate network connectivity and a server backend, the levels of complexity multiply.
If you're a solo-developer, just getting started, the Google App Engine does a pretty good job of making everything very easy to use, so I might recommend that. It has a free trial of all their cloud services which is $300 for 2 months.
https://cloud.google.com/appengine
Amazon AWS also is attempting to create a similar system, but they are seemingly geared to more enterprise-level operations.

Mobile app development for beginners [closed]

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'm a beginner in mobile app development. Am planning to develop an app related to social networking. Curious to understand the best possible resources to start with. I see some websites like apparchitect.com which help to create a mobile app easily. But I'm not able to figure out how the backend works. Can anyone guide me on how I can proceed with UI and the backend? Are there any tools or platforms available in cloud which will help me to quicken my mobile app development especially social networking apps?
This is a very broad question but i can understand it is difficult for beginners to approach as you don't know where to start, you can design user interface using google's IDE or eclipse, stick to that at least for the start before you move to advanced or custom UI design
for back-end there are many choices including but not limited to sql, sql lite, many other sql based products this list can get quite long, however i'd suggest parse.com it is easy to implement and reliable cloud based service or you could look at similar services usually they don't charge until your app gets to a certain request/traffic limit
if you can afford below sites offer good training content
https://teamtreehouse.com/home
http://www.pluralsight.com/
http://www.raywenderlich.com/category/android (paid plus free content)
Hope this helps !
That's a broad question. You can look at Android tutorials on teamtreehouse.com and look into using Parse.com for the backend. At least one of the teamtreehouse Android tutorials focuses on Parse.com, and another tutorial focuses on UI layout.

What are the pros and cons of Cloud based Backend for Mobile Applications eg. Parse [closed]

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!

Creating an API for Android, iOS and Web [closed]

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 9 years ago.
Improve this question
So I am creating a project with a couple of buddies and I need to create an API. This is my first time creating a big project and creating my own API. I don't know where to start. The project that we're working on will have a website, an app for Android and IOS, and use PostgreSQL. We will be using Javascript and Node.js as well. If there are any tips about creating API's for Android, IOS, and Web please let me know.
I would strongly recommend you read "RESTful Web Services" by Richardson
The book gives a thorough grounding in the "why?" behind organizing resources restfully. Also provides a good outline of different RESTful authentication mechanisms and the pros and cons of each - vital for a mobile app talking to a web-based back-end.
Then, sit back and outline the resources that will be necessary to run your app and have at it!
First of all take paper and pen to start design the architecture and write down all use cases. Also define the way data will be access.
While creating an API for mobile apps we should keep some important things in mind. First what type of API it should be JSON based or XML. And I will prefer JSON for mobile app as its lightweight and will take less time to parse. Also it will be fast to transmit. While XML bit costly.
One of most important thing you should design the api as secure as it could be. Because sensitive information can be sniff by some one. better to use SSL hand shake to make it secure.

Backend-server for mobile apps [closed]

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.

Categories

Resources