Jump to content
  • Advertisement
Sign in to follow this  
Alpha_ProgDes

What exactly is API-First?

This topic is 1011 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

So I read this link: http://techcrunch.com/2015/09/27/the-future-of-coding-is-here-and-threatens-to-wipe-out-everything-in-its-path/
And it seemed like a whole lot of nothing. So I googled the term. And the first 3 links were still vague. I get it's a "new" approach to developing software. But why should I buy into this? Is there a takeaway from this paradigm I should be getting and embracing?

I'm going to keep googling. But I was hoping that someone had a more concrete, concise explanation of this new API-First thing.

Share this post


Link to post
Share on other sites
Advertisement
Ugh.

I also had a Google, as I was curious. Seems like drivel written by journalists without any actual real-world development understanding to me, but I'm happy to be corrected on this.

The idea that we have traditionally focused on the back-end, then developed the API as an afterthought seems pretty bogus to me.

Share this post


Link to post
Share on other sites

Well after reading up on this it seems a bit daft to me for all but huge projects.

 

It's like writing an engine before you have any game to use it.

 

Basically you write the api first indenting to use that api to write your website so that extending the service to apps, desktop programs, etc can be easily done through that api.

 

That is all well and good but IMHO (as a business solutions developer with many years under my belt) it could result in a massive drain on resources. A library can easily be wrapped by a Web api using various dcom such as xmlrpc. It's one thing to write a reusable library (sensible) but another to go creating a Web api, kind of like "build it and they will come".

 

This is my own opinion and might not necessarily reflect reality smile.png

Edited by braindigitalis

Share this post


Link to post
Share on other sites

Self fulfilling prophecy. Author talks big about nothing, nothing becomes something because of what the author said. Bam, traffic.

 

Next year you'll be hearing about API First manifesto or something...

Share this post


Link to post
Share on other sites

It's like writing an engine before you have any game to use it.

 

Actually I'd say it's like the opposite. Write (or prototype) your game to figure out what you need, and then build/use the engine that best accomplishes those needs.

 

But really, the headline is total clickbait and the article is just drivel. This isn't the "future" of coding. It's the future, present and past. The large software company I used to work at has been API-focused for at least a decade. This is nothing new. Design the APIs to ease and enable coding scenarios, and not as "artifacts" of the underlying implementation.

Edited by phil_t

Share this post


Link to post
Share on other sites
Feh.

All our projects have been API First before API First was a thing.
</webdevhipster>


Just wanted to throw more fuel to the SEO fire.

Share this post


Link to post
Share on other sites

First comment on the article sums it up nicely.

 

 

Did someone resurrect Jackson Pollock and give him access to Word to just splatter a bunch of buzzwords over?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!