On: The API-ization of everything

[jmduke]

I'd follow that with:

For tech businesses, "there's an API for that".

For 90% of the other businesses, "what's an API?"

There's a vast amount of value to be captured by adding pleasant and easily used interfaces over otherwise boring APIs.

[AznHisoka → jmduke]

For 90% of other businesses, there's an Excel export. There's your API.

[antsar → AznHisoka]

Excel export to printer to fax machine, in some cases.

[patio11 → antsar]

Someone literally requested this as an import option for Appointment Reminder, because it was easier for their office staff to understand than uploading.

[AznHisoka → patio11]

I thought they wanted to download the Googles to their printer.

[antsar → AznHisoka]

Well, its a two-way process. Upload to the Googles through the fax machine, download the Googles through the printer.

[chaz → jmduke]

There's a massive gap between the tools that are given to [business] end customers vs the APIs. If I'm savvy enough to propose complex processes or ask nuanced questions but not savvy enough to write code against an API to get it done, I'm SOL. Expensive developer is my only real solution.

Agree that good API UIs (I realize that's two "interfaces") has a great future ahead.

[zbruhnke → jmduke]

and I'd counter that point with there are a ton of businesses being built on top of API's to deliver the types of products those "Other 90%" won't build themselves.

Innovation drives more innovation, the future is business being built on top of the framework these API's are laying