APIs as building blocks

26
Giuliano Iacobelli, CEO and co-founder [email protected] APIs as building blocks: let's code what matters most.

Transcript of APIs as building blocks

Page 1: APIs as building blocks

Giuliano Iacobelli, CEO and co-founder [email protected]

APIs as building blocks: let's code what matters most.

Page 2: APIs as building blocks

@stamplay

500 Million users32 Engineers

Page 3: APIs as building blocks

@stamplay

30 Million users13 Engineers

Page 4: APIs as building blocks

@stamplay

40B image views / day7 Engineers

Page 5: APIs as building blocks

@stamplay

How long before we have a billion-dollar acquisition offer for a one-engineer startup?

Page 6: APIs as building blocks

@stamplay

0

7500

15000

22500

30000

2006 2008 2010 2012 2014 2016

API Proliferation is exponential

The number of open API grew from ~0 to 13K in the past 8yrs.Will more than double to >30K in the next 2 years.

Page 7: APIs as building blocks
Page 8: APIs as building blocks

@stamplay

“An API for everything there is.” Yoda, Jedi Master.

APIs for everything

https://www.mashape.com/ismaelc/yoda-speak

Page 9: APIs as building blocks

@stamplay

API Explosion is transforming software development

Page 10: APIs as building blocks

@stamplay

APIs as a product

Horizontal Vertical

Page 11: APIs as building blocks

@stamplay

Rise of data integration and data execution platforms.

Page 12: APIs as building blocks

@stamplay

More than 77% of top apps integrate APIs.

} {

Page 13: APIs as building blocks

@stamplay

Stamplay uses some building blocks as well

{

Page 14: APIs as building blocks
Page 15: APIs as building blocks
Page 16: APIs as building blocks

Build vs Buy

Page 17: APIs as building blocks

@stamplay

There are no small changes.

When you’re striving for quality

Page 18: APIs as building blocks

@stamplay

Let’s do a test.

In a Yelp-like app, we want to limit the length of a text review in the product to 140 characters,

because we may want to use SMS to send them out.

..that’s a small change, right?

Page 19: APIs as building blocks

@stamplay

LET’S ADD AN IF-STATEMENT

Page 20: APIs as building blocks

@stamplay

Think again..

• What happens when the review is above 140 characters?• Do we crop the string, or display an error message to the user?• If we display an error, where does it appear? What does it say?• Who is going to write the error message?• How do we explain to the user why we’re limiting them to 140

characters?• How will these errors look?• Do we have a style defined?• If not, who is designing it?

Page 21: APIs as building blocks

@stamplay

• Who’s writing the JavaScript?• Does the JavaScript display the same type of error as the server-side

code?• If not, what’s the new style?• How does it behave with- out JavaScript?

..and again..

Page 22: APIs as building blocks

@stamplay

• Who is going to write this character counter?• Who wants to test it in our target browsers?• Also, where is the count of letters displayed on the screen?• What does the count look like?• The style should change as the user approaches zero characters and

look erroneous at the limit?• Should it stop accepting input at that point?• If so, what happens when they paste something in?• Should we let them edit it down, or alert them?

..and again!

Page 23: APIs as building blocks

@stamplay

Nothing comes for free.

Page 24: APIs as building blocks

@stamplay

It’s not free because you’re talking about it.

It’s not free the verifying it was done right.

It’s not free in the communication of doing it.

It’s not not free to carry it forward.

Page 25: APIs as building blocks

@stamplay

Connect all the things!

Page 26: APIs as building blocks

THANKS!

Giuliano [email protected]@Giuliano84

https://stamplay.com