Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
API Trends: What to expect in 2012
1. API Trends –
What to expect in 2012
01.17.12 @ 11:05 PST
VOIP or Dial-in (see chat)
groups.google.com/group/api-craft
Sam Ramji @sramji
Anant Jhingran @jhingran
Brian Pagano @brianpagano
25. Data-centric APIs
Today’s models
- highly paid - custom feeds (Dun & Bradstreet)
- free-for-all - sea of xls/csv files on a website
(Data.gov)
26. Data-centric APIs
Today’s models
- highly paid - custom feeds (Dun & Bradstreet)
- free-for-all - sea of xls/csv files on a website
(Data.gov)
Tomorrow’s model
- in the middle
- data brokered by APIs
- free and freemium models co-exist
29. Data-centric APIs
Is it about easy consumption of silos? Or is it for clean linking across silos?
30. Data-centric APIs
While data sources might be motivated to publish clean,
linkable data, a more likely scenario is new data platforms
that cleanse and standardize and aggregate
37. APIs optimized for the mobile developer
Mobile apps drive API development and adoption
38. APIs optimized for the mobile developer
Multiple devices – multiple requirements
39. APIs optimized for the mobile developer
Today
- mobile apps for iPhone (iOS) and Android
40. APIs optimized for the mobile developer
Today
- mobile apps for iPhone (iOS) and Android
Trend
- HTML5/JavaScript for apps that can run on any device
41. APIs optimized for the mobile developer
Mobile devices need to receive less data in API responses
Shouldn’t need to make repeated API calls to perform
simple tasks
42. APIs optimized for the mobile developer
Inefficient APIs make things worse for
app developer
API provider
43. APIs optimized for the mobile developer
Problems are multiplied by mobile demand patterns many
small API requests
Concurrency the sheer number of devices hitting the API
at once
44. APIs optimized for the mobile developer
Let developers filter the size and content of the API response
before it's returned to the app
45. APIs optimized for the mobile developer
Give developers the right format for their app environment
plist for iOS
JSONP for HTML5/JavaScript
47. OAuth 2.0 – the default security model
In 2012 OAuth will become the default choice for securing
APIs that enable end-users to interact through apps with
their valued services
48. OAuth 2.0 – the default security model
Apps are the new intermediaries in the digital world
49. OAuth 2.0 – the default security model
Apps put buyers and sellers together
buyer = end user
seller = API provider
50. OAuth 2.0 – the default security model
Great apps package the provider's API in
…a great user experience
51. OAuth 2.0 – the default security model
Adoption
users can explore and try an app without compromising their
private data and privileges services like Salesforce.com, Twitter,
Facebook, eBay, . . .
52. OAuth 2.0 – the default security model
User can terminate the app's access to their account if
they don't like or don't trust an app
53. API Trends
Enterprise APIs go mainstream
API-centric architecture
Data-centric APIs
Enterprise APIs for Analytics
APIs optimized for the mobile developer
OAuth 2.0 - the default security model
54. THANK YOU
Questions and ideas to:
@sramji
@jhingran
@brianpagano
groups.google.com/group/api-craft
Editor's Notes
Creative Commons Attribution-Share Alike 3.0 United States License
Creative Commons Attribution-Share Alike 3.0 United States License