A web application using the API for everything?

Question

I am going to start planning an internal project management tool for my company. One thing that always surprised me was the API.

Would it be considered bad practice / too inefficient to create an API first and build the actual site using these API calls, rather than implement it twice?

Let me know your thoughts!

Answer 1

I totally agree that developing an API will give you an unbound architecture, and I recommend that.

However, I believe that you should warn that developing an API first increases the risk of developing the wrong API (by the way, PM basically reduces the risk of a project). You will also be tempted to focus your API functions, which may be unused, which is a waste of time. Developing an API in conjunction with an application ensures that it properly meets the needs of applications or applications. If you are not sure about the accuracy and understanding of the requirements, I suggest programming the API one opportunity at a time with the application.

For example, as you develop an application and find the exact point at which you need to make an API call, create an interface (depending on technology) that will look exactly the way you need it. You can drown out this interface to launch the application, which is a great tool to verify that the application is still on the way to user expectations. ("You want it to work like that, right?"). Later you can implement this interface. If random requirements are subject to change, you will not waste time creating an outdated infrastructure.