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 2 years ago.
Improve this question
I am new to flutter and programming as well.
I am following flutters official docs and have sailed smoothly till State Management.
After that it has section for networking https and json serializing.
here
I have no idea about backend and networking and json please help me or guide me how to connect and access servers for my app.
Don't worry!
First, you need to learn a bit of JSON and Rest API
Here is a random tutorial
https://www.smashingmagazine.com/2018/01/understanding-using-rest-api/
Hope it's good) or google it yourself "what is JSON rest API"
What you need to know that there is no "Flutter specific backend" there is an app and the server and most popular way to communicate is Rest API.
Second, you will need to learn How to send a request and receive a response from the server. Hope its in your tutorial and after understanding what is Rest API and JSON it will make sens to you.
But there are great flutter official docs about that
https://flutter.dev/docs/cookbook/networking/fetch-data
Finally Firebase It's wonderful, thanks to google for it, it provides you a server for your app for free (at least when there are no too much of real users), It will save you a lot of time and money because it provides easy to use free servers that require minimum knowledge of backend
you can start with with packages for basic http request : https://pub.dev/packages/http
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 2 years ago.
Improve this question
So i'm developing a project using Laravel 5.7, and I want to include a RESTful API to make the mobile version communicate with the app, and of course the web application itself.
My question is, what is the best practice is such cases when it comes to routing and controllers, I have read some suggestions here and other blogs and got confused, some suggested that I should declare One Routing file to be used by the web app and API and add an identifier for e.g("web" and "mobile") and based on it I return a view or JSON data, others suggested to separate the routing (api and web) but point them to the same controller methods which is think it's better than the first suggestion.
Appreciate your help.
Laravel separates the api routes from the web routes.
Web routes are in the routes/web.php file.
API routes are in the routes/api.php file.
What can be annoying is to separate the logic of the API part from the logic of the web part.
Here the solution is still simple. What I do is I create a folder that I call API in app/Http/Controllers; all the controllers I put in this folder are in the App\Http\Controllers\API namespace. In the corresponding route file, all you need to do is add the API\ flag before the controller name.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
We are going to develop some mobile app for one of our clients, and we are defining the technical solution for the backend server.
Basically, we need to implement a backend providing REST apis for the apps. The apps will need features such as user authentication, handling of user profiles and user contents. The backend should also expose a web administration interface and allow to manipulate some of the app contents in a CMS-like way.
My client specifically wants to avoid baas solution (like Parse), and I am trying to find some open source software able to provide some of the features out of the box, to avoid writing everything from scratch, and develop the other parts. We can use cloud services such as AWS for hosting the backend.
What existing platform/software would you advise?
Here a a few options to look into:
DreamFactory: http://www.dreamfactory.com/
Loopback: http://loopback.io/
Apache Usergrid: http://usergrid.incubator.apache.org/
BaasBox: http://www.baasbox.com/
Not sure if this answer your question. Did you come across other options?
I am currently using apache usergrid for one of my projects and consider it powerful on following areas;
Authentication & Authorization (also social login)
Activity creation and activity feeds
Asset storage (local or aws s3)
Dynamic collection creation
Search on collections and support custom query language (via elastic search)
But it doesn't support push notifications. If you need that out of the box, you may have a look at BaasBox. It seems a good alternative to usergrid.
I didn't find documentation adequate for usergrid (i mean for internals not api usage), so you have to dig source code to find out answers.
If you are developing social application (user activities, feeds, comments, likes) it is hard to update counters in a document (e.g. updating comments and likes count). It is not natively supported. You may sync increments on the same document using a queue like kafka.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I am developing a django web app(just for fun/learning) where users can sign up, ask questions on a certain topic and provide answers. It is all working just fine but I want to learn mobile app development so looked into moving that web app to be a mobile app using phonegap or something similar (recommendations welcome).
From my research it seems that, in order to serve up the data to the mobile app, as REST API would need to send the data as JSON which would be displayed in the app, at least for Phonegap anyway.
Would I be right in thinking that converting the django app to just be a REST API which serves the JSON to the app is the right way of going about things or have I gotten the wrong idea? (I am just learning the concepts of REST apis so apologies if that makes no sense).
Perhaps another framework would be better for creating the API or another approach all together?
I am not tied to any language or framework as I am just using the project to learn.
Thanks for your time.
For a PhoneGap app you don't want to use Django to render the HTML, you just want the PhoneGap app to authenticate and communicate to Django via an a web service (here a REST interface, in JSON format e.g.)
This is one possible way to implement REST server on Django: http://www.django-rest-framework.org/
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'm having a frustrating time with Ruby. I've been working on developing a program that randomly generates a string from two arrays, which I'm all fine and dandy on that front. I'm fluent in the language. The problem I am having is with putting it online. I've been trying to figure out rails with no luck running my piece of software. Anyone able to help me along the way here? I'm unsure how to get this thing into a website for launch
Thanks in advance!
Sounds like Rails is overkill for this. If you only plan on having very simple actions, Sinatra might be better for you. http://www.sinatrarb.com/intro.html
After creating a simple API in Sinatra, you can then serve static assets (HTML, JS, CSS) where you can then use simple AJAX calls to hit your Sinatra backend.
You can get a Heroku account for free to host your application. Hosting a Sinatra application on Heroku should be pretty easy: http://blog.kuntz.co/2014/03/15/deploying-a-sinatra-app-to-heroku.html
You have a lot of options when it comes to deploying your web app.
A lot will depend on the scale of the application, budget and preference.
You will have mainly 2 main options.
Ready to use options
Ex. heroku, enginyard
Do it yourself options
Normal servers Ex. Digital ocean
After you make this decision you will find it way easier to deploy your app.
In case of heroku(its free I recommend it for start) reference this tutorial
If you do it on your own you will have to deiced which server will you use
Nginx, apache or others
Check out this
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
In my 4 years of experience,I have developed a lot of web applications. Now, the concept of programmable web getting more and more popular, new APIs are being released almost everyday. I would like to develop a java API/library for a few of these endpoints.Ex stackapps,reddit,digg etc... What I would like to know from you people is ,
How is the API of the regular web
apps differ from the API of these
libraries. Or what is the difference
between these two from design
perspective
What are the best API development
practices.
What are all the factors that I need to consider before designing the API
.
Please comment, if the details are not sufficient.
Stability
If you offer an API to your web app, it is probably because you want other people to build applications using it. If it is not stable they will hate you for forcing them to follow through your frequent changes. If this takes too long, their site might remain non-functional for a long time while they are figuring out the new way of doing things in your API.
Compactness
You want the API to be complete but compact, as in not too much to remember.
Orthogonality
Design it so there is one and only one way to change each property or trigger an action. Actions in an orthogonal API should have minimal (if ever) side effects.
Also, it's not a good practice to remove a feature from a public API once released.
Security and Authentication
Since the API is web-exposed, you will have to authenticate each request and grant appropriate access. Security common sense applies here.
Fast Responses or Break into pieces
I believe in a web environment we should have fast responses and avoid requests that will take too long to complete. If it's unavoidable then it is better to send an ACK and break the task into several pieces and subsequent calls.
From my experience, all good API were not made to solve a generic problem, but to solve a problem for some that requires a certain abstraction. This abstraction is then evolving as the requirement and/or the underlying layer change.
So instead of finding the API that will do it all, I'd start by finding one or two good case problem were your API could help.