How many of you thought of building an API instead of an app?

Question

Hi,I am a data engineer. Like many of you, I've always had these ideas to build something myself.Right now I do have one well-going side project where we work as a group of people. However, the complexity/time invested in managing and communication grows exponentially when it's not your full-time job.Therefore, at some point, I realized that a good alternative might be to start from an API that you can build yourself (that actually can be heavily used to build an app).So, my question for those who are good with the back-end things, have you ever considered such an option?I, for example, started building an API that gives access to a database with the news data.

dangerface · Accepted Answer

Makes sense to me, recently I wrote a function that checks domain name availability.
I started to write my own thinking it would be simple enough, but each tld has its own whois server with its own layout that needs parsed and they all rate limit.
I had a look around for a better method and found some examples on https://rapidapi.com/ of other people who have rolled their own and are now selling it as an api
I decided to just write it myself but now I have it built I think I might put it on rapidapi too.

jfoster · Answer

I think one challenging aspect of this approach is that beyond something trivial and without a lot of experience, you might design the API in a way that is inconvenient for real usage. If you develop the app as well, you'll have to use the API you build, and you'll make adjustments as necessary.

muzani · Answer

This is actually a surprisingly good idea. I'm heavily a front end person and never really thought of just releasing a API. It's taking a surprisingly long time to set up a CRUD, even small things like responsive drop downs.

thedevindevops · Answer

What about a simple console app that consumes an sdk you develop alongside the API?