Is it worth building from the beginning or is it better build an API later on when you actually need it?1 tykkää
Esitä kysymyksiä ja opi freelancer-asiantuntijoilta
The question is very good. First of all, you have to be clear about your websites purpose.
If adding an API to your website does not offer any business value, or does not offer any service which people or developers could use, then there is no real sense to create an API, only if you want to do it for fun.
The type of websites which usually do not have an API are company websites, contact websites (like online CV for yourself) or blogs.
The typical webpages which may have APIs are the ones which offer some service, like Google's Search engine, Google translate or Maps. Basically if your website or product is doing some data processing then it does worth creating an API.
Another reason why you could create an API for your business or website is because you want to use the API in mobile or desktop applications built for your business case, or even offer as API as a Service for developers or other companies.
Please keep in mind if you are building an API for your website that it's a new apart of your website which needs to be protected and it may also be subject to cyberattacks.
if you want to build an API that you want to use as a template in you future projects.
you have to fixes your object and needs if want to use a special Programs do it with pure language (PHP,Python,...) , if you want to be more organised use frameworks like(laravel,django...).
you idea must be general if you want to use it in many projects,
API (application program interface) is a set of data, routines, protocols, and tools for building software applications. If your website provides some kind of service, you can build API. But that service must be useful for other software components or service consumers. Unless it would be waste of time and resources.2 tykkää
The question mostly is not - when to build, but - do you need it? As said above, think about your own needs. API is a service to let some of your users (customers) communicate with your site, or platform. So based on this, decide the purpose of API before dreaming about it.
If you still think you need it - it's fine to make a point in the plan of your site building, and at first make the needed functional blocks of the main application, test it, then only include the service for external use of your application.
It depends on whether it is necessary to use API. There is not any compulsion that you have to use API which does not make any sense in your application. If your application works completely fine without API then no need to think for that.
Keep it simple unless it is needed.
I think you should build it when any other company or person needs data from you. Like if you are job listing website and others want to show your job listings on their website.
Their are many ways of data theft for programmers. So it is better to implement your security and give APIs for better access.
Yes, you probably should. Most web applications have a backend and frontend, and an API gives you a very structured way to communicate between them. If you don't go for an API, chances are you'll end up with an unstructured mess which is hard to deal with and hard to introduce new developers to. It's better to go with an API to get a documented, reusable interface between your backend and frontend.0 tykkää
Actually it needs for project purpose. If you consider security, it is necessity to build an API at beginning.
Anyone who has had to refactor to build their API will want to avoid doing this the next time. It is totally consistent with rapid release of your product. Any well architected web app will have a data layer, a logic layer and a presentation layer. The API is merely the ability to access the data and logic layers directly in order to put additional presentation layers on top of them.