The document summarizes the results of a developer survey about API pain points. It finds that Facebook was rated as having the "worst API". Developers complained about inconsistent standards across APIs, poor documentation, lack of test environments, and APIs changing in ways that break existing integrations. The presentation calls for more communication between API providers and developers, following standards and best practices, clear documentation-driven design, and holding each other accountable.
This document is a presentation about New York City's use of APIs and open data. It discusses how NYC has opened up access to city data and services through APIs to foster civic innovation. It notes that NYC now has over 750 public datasets available via API. The presentation encourages other cities to follow NYC's example in unlocking their data and services through APIs to engage citizens and developers.
This document discusses how to create an API that developers love. It emphasizes the importance of solving developer pain points, using common standards like REST and JSON, providing thorough documentation with code samples in multiple languages, and reliable long-term support. Well-designed APIs at companies like Netflix, Twitter, Foursquare, Stripe and Twilio are used as positive examples. The document encourages aligning business goals with developers' needs, committing to API maintenance, and being available to help developers whenever needed.
The document discusses different interfaces for accessing systems and services, including web UIs, mobile apps, and APIs. It notes that APIs provide more flexibility than other interfaces by allowing for real-time decisions, historical reports, and automation. The document advocates for treating APIs as a new interface and making them easy to use through documentation, code examples, and ensuring they work with common HTTP tools.
This document discusses real-time APIs and why they are important for building real-time applications. It explains that real-time APIs allow developers to build apps that can process data in real-time, send push notifications, and provide fully real-time experiences for users. The document outlines different generations of real-time technologies including pubsubhubbub, HTTP streaming, and emerging bi-directional socket APIs enabled by HTML5 WebSockets. It encourages data providers to release real-time access to their data to enable further innovation by developers.
The document discusses the Guardian Open Platform which provides access to the Guardian's content through an API. The API offers rights-cleared content in three tiers of access and has been successful in increasing developer happiness, productivity, and the internal usage of the API. However, the document notes that more can still be done to improve external data references and reduce the gap between self-service and high-touch support. It promotes further opening of the Guardian's content creation process, rights management, and commercial models.
CabanaApp allows anyone to easily build custom mobile apps without coding by providing a drag-and-drop interface for designing apps and includes a demo of its interface. It aims to empower anyone to create mobile apps and is promoting its website and Twitter handle. The document was created by Reeve S. Thompson on October 27, 2011 to introduce CabanaApp.
Business of APIs Conference 2011 - YourTroveMashery
Seth Blank presented the results of an API developer survey that found Facebook had the worst API. Developers complained about poor documentation, inconsistent standards between APIs, lack of testing environments, and frequent changes. Blank argued that API providers and developers need to work together to establish standards, best practices, and a developer bill of rights to improve APIs and the developer experience.
Mashery Presents: The Evolution of Distribution - Adam Kleinberg, CEO, TractionMashery
Whether you are in retail, media, publishing, technology or travel, the ability to distribute information onto the multitude of internet connected devices has become a challenge for even the most nimble of companies. Everyone is vying for the attention and eyes of the consumer. It is a new world and consumer expectations have changed when it comes to the way content/data/inventory is distributed, discovered and consumed. This change in distribution, in part, is due to the adoption of APIs (Application Programing Interfaces). Businesses who have leveraged APIs have made it more than just a "database of stuff", but rather, have created a platform by which they are now basing their business strategy. Speakers from Mashery, Best Buy, eBay/PayPal and Netflix joined to explore the "Evolution of Distribution" and examined the notion of "why every brand needs an API".
This document is a presentation about New York City's use of APIs and open data. It discusses how NYC has opened up access to city data and services through APIs to foster civic innovation. It notes that NYC now has over 750 public datasets available via API. The presentation encourages other cities to follow NYC's example in unlocking their data and services through APIs to engage citizens and developers.
This document discusses how to create an API that developers love. It emphasizes the importance of solving developer pain points, using common standards like REST and JSON, providing thorough documentation with code samples in multiple languages, and reliable long-term support. Well-designed APIs at companies like Netflix, Twitter, Foursquare, Stripe and Twilio are used as positive examples. The document encourages aligning business goals with developers' needs, committing to API maintenance, and being available to help developers whenever needed.
The document discusses different interfaces for accessing systems and services, including web UIs, mobile apps, and APIs. It notes that APIs provide more flexibility than other interfaces by allowing for real-time decisions, historical reports, and automation. The document advocates for treating APIs as a new interface and making them easy to use through documentation, code examples, and ensuring they work with common HTTP tools.
This document discusses real-time APIs and why they are important for building real-time applications. It explains that real-time APIs allow developers to build apps that can process data in real-time, send push notifications, and provide fully real-time experiences for users. The document outlines different generations of real-time technologies including pubsubhubbub, HTTP streaming, and emerging bi-directional socket APIs enabled by HTML5 WebSockets. It encourages data providers to release real-time access to their data to enable further innovation by developers.
The document discusses the Guardian Open Platform which provides access to the Guardian's content through an API. The API offers rights-cleared content in three tiers of access and has been successful in increasing developer happiness, productivity, and the internal usage of the API. However, the document notes that more can still be done to improve external data references and reduce the gap between self-service and high-touch support. It promotes further opening of the Guardian's content creation process, rights management, and commercial models.
CabanaApp allows anyone to easily build custom mobile apps without coding by providing a drag-and-drop interface for designing apps and includes a demo of its interface. It aims to empower anyone to create mobile apps and is promoting its website and Twitter handle. The document was created by Reeve S. Thompson on October 27, 2011 to introduce CabanaApp.
Business of APIs Conference 2011 - YourTroveMashery
Seth Blank presented the results of an API developer survey that found Facebook had the worst API. Developers complained about poor documentation, inconsistent standards between APIs, lack of testing environments, and frequent changes. Blank argued that API providers and developers need to work together to establish standards, best practices, and a developer bill of rights to improve APIs and the developer experience.
Mashery Presents: The Evolution of Distribution - Adam Kleinberg, CEO, TractionMashery
Whether you are in retail, media, publishing, technology or travel, the ability to distribute information onto the multitude of internet connected devices has become a challenge for even the most nimble of companies. Everyone is vying for the attention and eyes of the consumer. It is a new world and consumer expectations have changed when it comes to the way content/data/inventory is distributed, discovered and consumed. This change in distribution, in part, is due to the adoption of APIs (Application Programing Interfaces). Businesses who have leveraged APIs have made it more than just a "database of stuff", but rather, have created a platform by which they are now basing their business strategy. Speakers from Mashery, Best Buy, eBay/PayPal and Netflix joined to explore the "Evolution of Distribution" and examined the notion of "why every brand needs an API".
The document describes ELIXR, a project that uses case stories in online videos to encourage teaching innovation. It discusses examples of how ELIXR videos were used in faculty development workshops at different universities, including workshops on the first day of class and universal design for learning. The document also provides an overview of the goals and outcomes of an ELIXR workshop on "just in time teaching" conducted at Cal State Northridge.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
The document welcomes attendees to the Business of APIs Conference in New York City. It provides information on a global database with company and industry records, as well as resources for small businesses. The document outlines challenges with different API interfaces, pricing, protocols, authentication, and documentation. It recommends thorough documentation, examples, flexible packaging and pricing, designing for consumers, and talking to developers and customers.
The document discusses platform owners potentially working against developers who build on their platforms. It notes that Fred Wilson advised developers to expect that platform owners may someday compete with them or act against their interests. Examples are given of different types of platforms and applications. The document concludes by suggesting best practices for developers building on platforms, such as having clear boundaries and over-communicating what data they expose.
This document summarizes Klout's presentation at the 2011 Business of APIs Conference in New York City. Klout announced that their API receives over 6 billion calls and has over 1100 API customers. They discussed their goals of building strategic relationships with customers through the API, helping customers monetize Klout data, and keeping the platform exciting. Klout also highlighted some partners using their API like about.me, Radian6, and VenueMachine. The presentation covered Klout's strategies around segmenting customers, controlling the platform, setting pricing policies, incentivizing consumers, and building a true open platform.
Business of APIs Conference 2011 - SalesForce.comMashery
The document discusses Salesforce.com's API journey. It notes that Salesforce currently services 500 million requests per day, with 60% (300 million) being API calls. It then outlines Salesforce's strategy to keep APIs simple and flexible while enabling integration, custom application development, and parity with platform features. The document also discusses the historical evolution of Salesforce's APIs from 2001 to present day and the addition of REST APIs to align with modern technologies like HTML5 and mobile platforms. Finally, it covers the Chatter API's shift to returning full object graphs via REST to improve performance over individual object calls.
Jesse Emery presented the results of an API developer survey that highlighted widespread issues with APIs. The survey found that Facebook had the worst API, with developers complaining about poor documentation, inconsistent standards between APIs, and a lack of test environments. Emery argued that APIs need to have more open communication, documentation-driven design, standards, and view developers as partners rather than just users of the API. By improving the developer experience with APIs, businesses can gain more developer adoption, customer retention, and revenue.
At Mashery's Business of API's Conference we shared data from our survey of developer pain to let API providers know where they could do better, and to sound a call to action for all the providers out there to start working together
5 Heresies for a Better World: some playful challenges to everyone's assumptions about building for the modern web.
(From some time back in 2008, so some of the references have been forgotten by now. The points about having to think, and not just following the crowd without thinking, and cats being evil and about to make us all obsolete slaves, are still pretty relevant thought.)
This document discusses Opera Mobile and HTML5. It provides an overview of key HTML5 features such as geolocation, video, CSS3, forms, storage, graphics, and others. It also references demos and specifications. The presentation introduces HTML5 capabilities in Opera Mobile and questions are invited at the end.
This document discusses building APIs for mobile applications using Python and Django. It recommends designing APIs that return hierarchical data, support authentication and authorization, use mobile-specific error codes, accept arrays of data, and return pre-calculated data. It provides examples of implementing these recommendations using the TastyPie framework, including limiting data by user and handling errors.
The document discusses the rise of internet-connected devices and online video. It notes that in 2010 there were 425,000 internet-connected TVs sold, rising to 820,000 in 2011. YouTube uploads were increasing exponentially from 2007 to 2010. The document also discusses new services like Apple TV, internet TV channels through services like Yubby, and the ability to live stream video from vehicles.
The document summarizes Tim Wright's presentation on the future of HTML5. It discusses emerging technologies like Web Workers for improved JavaScript threading, WebGL for 3D graphics in the browser, and Device APIs for accessing device capabilities. While some of these are still works in progress, they have the potential to enhance the user experience and push the capabilities of the web platform. Wright encourages the audience to get involved in developing these new standards.
Do you write JavaScript? Congratulations, you're probably awesome at Node.js! While thinking about things from a server-side perspective might feel off-putting and unnatural, things like callbacks, storing data in JSON, and implementing actual websites probably do not. We'll go beyond getting Node installed and talk about how to quickly build a working web application, and demonstrate that Node can offer frontend developers more than just a new prototyping tool or way of creating endless chat servers.
Javascript Views, Client-side or Server-side with NodeJSSylvain Zimmer
The document summarizes a presentation on building applications that can render on both the server and client using a single codebase. It discusses how traditional server-side and client-side apps are structured, then shows how server-side JavaScript allows building a single app with a shared core that can adapt for the server or browser through the use of adapters. It demonstrates this approach with a sample app and discusses benefits like serving HTML versions for search engines or legacy browsers. Key aspects covered are rendering on the server/client with a View class and handling browser history across environments.
This document discusses the benefits of scripting such as speed, accuracy, consistency and scalability. It covers various scripting languages like Ruby, JavaScript, and Python that can be used for automation. The document also mentions Apple Events, OSAX, dictionaries and provides hands-on examples and a recap. It directs the reader to a GitHub page for the code and provides the author's Twitter handles for further information.
Taking SM to Next Level - Governor's Conference 2011Andrew Hoffman
The document is a presentation about taking social media to the next level. It discusses establishing a solid foundation for social media use, including purpose, content, calls to action, and design. It also covers specific social media tools like Google Alerts and Analytics, social sharing platforms, email marketing, video, mobile apps, digital fundraising, and cloud-based collaboration tools. The presentation aims to provide practical strategies for nonprofit organizations to effectively manage their social media presence.
The document appears to be notes from a presentation on social media and the internet. It discusses topics like the rise of user-generated content sites like YouTube and Tudou, the growth of internet-connected TVs, and the power of online video. It also covers Google AdWords, new companies like Yubby that allow creating custom video channels, and the increasing number of daily YouTube video uploads.
The document appears to be a slide deck presentation on social innovation and following consumers. It discusses topics like live streaming an electric vehicle trip, social media 2.0, the power of online video including statistics on YouTube usage, multi-screen media usage, and the rise of internet-connected TVs. Several technologies and companies are mentioned like the iPhone 4, Yubby for company video channels, and 3D television findings from the FIFA World Cup on ESPN.
I've given different versions of this talk at different venues over the past 12 months. This is the most recent version as presented on 18/10/2011 at the Belgian ISSA chapter meeting.
The document describes ELIXR, a project that uses case stories in online videos to encourage teaching innovation. It discusses examples of how ELIXR videos were used in faculty development workshops at different universities, including workshops on the first day of class and universal design for learning. The document also provides an overview of the goals and outcomes of an ELIXR workshop on "just in time teaching" conducted at Cal State Northridge.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
The document welcomes attendees to the Business of APIs Conference in New York City. It provides information on a global database with company and industry records, as well as resources for small businesses. The document outlines challenges with different API interfaces, pricing, protocols, authentication, and documentation. It recommends thorough documentation, examples, flexible packaging and pricing, designing for consumers, and talking to developers and customers.
The document discusses platform owners potentially working against developers who build on their platforms. It notes that Fred Wilson advised developers to expect that platform owners may someday compete with them or act against their interests. Examples are given of different types of platforms and applications. The document concludes by suggesting best practices for developers building on platforms, such as having clear boundaries and over-communicating what data they expose.
This document summarizes Klout's presentation at the 2011 Business of APIs Conference in New York City. Klout announced that their API receives over 6 billion calls and has over 1100 API customers. They discussed their goals of building strategic relationships with customers through the API, helping customers monetize Klout data, and keeping the platform exciting. Klout also highlighted some partners using their API like about.me, Radian6, and VenueMachine. The presentation covered Klout's strategies around segmenting customers, controlling the platform, setting pricing policies, incentivizing consumers, and building a true open platform.
Business of APIs Conference 2011 - SalesForce.comMashery
The document discusses Salesforce.com's API journey. It notes that Salesforce currently services 500 million requests per day, with 60% (300 million) being API calls. It then outlines Salesforce's strategy to keep APIs simple and flexible while enabling integration, custom application development, and parity with platform features. The document also discusses the historical evolution of Salesforce's APIs from 2001 to present day and the addition of REST APIs to align with modern technologies like HTML5 and mobile platforms. Finally, it covers the Chatter API's shift to returning full object graphs via REST to improve performance over individual object calls.
Jesse Emery presented the results of an API developer survey that highlighted widespread issues with APIs. The survey found that Facebook had the worst API, with developers complaining about poor documentation, inconsistent standards between APIs, and a lack of test environments. Emery argued that APIs need to have more open communication, documentation-driven design, standards, and view developers as partners rather than just users of the API. By improving the developer experience with APIs, businesses can gain more developer adoption, customer retention, and revenue.
At Mashery's Business of API's Conference we shared data from our survey of developer pain to let API providers know where they could do better, and to sound a call to action for all the providers out there to start working together
5 Heresies for a Better World: some playful challenges to everyone's assumptions about building for the modern web.
(From some time back in 2008, so some of the references have been forgotten by now. The points about having to think, and not just following the crowd without thinking, and cats being evil and about to make us all obsolete slaves, are still pretty relevant thought.)
This document discusses Opera Mobile and HTML5. It provides an overview of key HTML5 features such as geolocation, video, CSS3, forms, storage, graphics, and others. It also references demos and specifications. The presentation introduces HTML5 capabilities in Opera Mobile and questions are invited at the end.
This document discusses building APIs for mobile applications using Python and Django. It recommends designing APIs that return hierarchical data, support authentication and authorization, use mobile-specific error codes, accept arrays of data, and return pre-calculated data. It provides examples of implementing these recommendations using the TastyPie framework, including limiting data by user and handling errors.
The document discusses the rise of internet-connected devices and online video. It notes that in 2010 there were 425,000 internet-connected TVs sold, rising to 820,000 in 2011. YouTube uploads were increasing exponentially from 2007 to 2010. The document also discusses new services like Apple TV, internet TV channels through services like Yubby, and the ability to live stream video from vehicles.
The document summarizes Tim Wright's presentation on the future of HTML5. It discusses emerging technologies like Web Workers for improved JavaScript threading, WebGL for 3D graphics in the browser, and Device APIs for accessing device capabilities. While some of these are still works in progress, they have the potential to enhance the user experience and push the capabilities of the web platform. Wright encourages the audience to get involved in developing these new standards.
Do you write JavaScript? Congratulations, you're probably awesome at Node.js! While thinking about things from a server-side perspective might feel off-putting and unnatural, things like callbacks, storing data in JSON, and implementing actual websites probably do not. We'll go beyond getting Node installed and talk about how to quickly build a working web application, and demonstrate that Node can offer frontend developers more than just a new prototyping tool or way of creating endless chat servers.
Javascript Views, Client-side or Server-side with NodeJSSylvain Zimmer
The document summarizes a presentation on building applications that can render on both the server and client using a single codebase. It discusses how traditional server-side and client-side apps are structured, then shows how server-side JavaScript allows building a single app with a shared core that can adapt for the server or browser through the use of adapters. It demonstrates this approach with a sample app and discusses benefits like serving HTML versions for search engines or legacy browsers. Key aspects covered are rendering on the server/client with a View class and handling browser history across environments.
This document discusses the benefits of scripting such as speed, accuracy, consistency and scalability. It covers various scripting languages like Ruby, JavaScript, and Python that can be used for automation. The document also mentions Apple Events, OSAX, dictionaries and provides hands-on examples and a recap. It directs the reader to a GitHub page for the code and provides the author's Twitter handles for further information.
Taking SM to Next Level - Governor's Conference 2011Andrew Hoffman
The document is a presentation about taking social media to the next level. It discusses establishing a solid foundation for social media use, including purpose, content, calls to action, and design. It also covers specific social media tools like Google Alerts and Analytics, social sharing platforms, email marketing, video, mobile apps, digital fundraising, and cloud-based collaboration tools. The presentation aims to provide practical strategies for nonprofit organizations to effectively manage their social media presence.
The document appears to be notes from a presentation on social media and the internet. It discusses topics like the rise of user-generated content sites like YouTube and Tudou, the growth of internet-connected TVs, and the power of online video. It also covers Google AdWords, new companies like Yubby that allow creating custom video channels, and the increasing number of daily YouTube video uploads.
The document appears to be a slide deck presentation on social innovation and following consumers. It discusses topics like live streaming an electric vehicle trip, social media 2.0, the power of online video including statistics on YouTube usage, multi-screen media usage, and the rise of internet-connected TVs. Several technologies and companies are mentioned like the iPhone 4, Yubby for company video channels, and 3D television findings from the FIFA World Cup on ESPN.
I've given different versions of this talk at different venues over the past 12 months. This is the most recent version as presented on 18/10/2011 at the Belgian ISSA chapter meeting.
SLA11 CID Division program encore 080211 webinar slidestonilwilson
The document summarizes key takeaways from several sessions at the 2011 SLA Annual Conference on competitive intelligence. The sessions aimed to dispel myths about CI and provide examples of useful mobile apps for librarians and information professionals. Some of the main points included that CI involves analyzing various information sources to gain insights, rather than espionage. Effective market intelligence relies on developing an expert network to share relevant information. The document also provided a sample search strategy to uncover hidden information and examples of potential information leakage points to consider.
The document appears to be a slideshow presentation discussing trends in online video, social media, and television. Some key points discussed include the growth of online video uploads and viewership on YouTube, the rise of internet-connected televisions, and the potential for companies to create their own video channels. The presentation also examines emerging technologies like 3D television and e-readers.
The document discusses open source enterprise content management and how it can be enhanced by integrating semantic web technologies. It describes how semantic technologies can help extract meaning from unstructured content, connect information to form knowledge, reason about the knowledge, and present it in an actionable way. The document also provides an overview of Nuxeo's work on semantic ECM through various research projects and their semantic engine which extracts metadata from content.
10 basic rules of avoiding hackathon fail finalMashery
This document provides 10 rules for avoiding failures at hackathons: no PowerPoint presentations, provide icebreakers for introverts, ensure the hackathon reflects your company culture, co-organize with other companies, supply ample power sources and WiFi, have few clear rules but enforce them, avoid common faux pas, focus on projects not business plans, create a comfortable space for hackers, and don't advertise the event like a party.
Qwerly is an API-only business that provides an API allowing companies to mine public social web data for information about customers, users, and leads. The company's CEO, Max Niederhofer, outlines how Qwerly started in 2010 with the goal of building a universal address book of social profiles. Now, Qwerly generates all of its revenue through its API, which is used by various companies and over 2,000 API users to gather social data for their businesses.
ASOS is a global online fashion retailer and the number one online fashion retailer in the UK. It has revenues exceeding $500 million and is growing 142% year-over-year. ASOS is launching a public API to allow developers access to its product catalog, shopping basket functionality, and other data to create new experiences for customers and satisfy growing demand. The public API will power ASOS mobile apps and allow third-party innovators to build on ASOS's assets and data.
Nature Publishing Group is a family-owned scientific publisher with over 100 journals. It aims to provide the best scientific information to both the general public and researchers. Nature Publishing is launching a developer portal and APIs to enable new applications and tools that increase access and reuse of its scientific content. The portal will provide documentation, support, and keys to allow developers to build both non-commercial and commercial tools using Nature's content within set quotas and limits. The future plans include expanding the set of available APIs and growing an active developer community.
This document welcomes attendees to the Business of APIs Conference 2011 in New York City. It provides 4 tips for fueling an API with rocket fuel: 1) Find the fit, 2) Remove friction, 3) Market differently, and 4) Go where the consumer lives. Traditional marketing practices won't work with today's consumers who want fame, money, curated content and great tools.
This document discusses how to build a developer community from scratch. It recommends (1) assuming users know nothing about APIs and explaining concepts like REST and HTTP, (2) being clear about what is supported and not supported, (3) explaining authentication, (4) highlighting integrations, (5) being open about upcoming projects and feedback, (6) maintaining an internal FAQ, (7) using social media focused on developers, (8) providing code demos, (9) having an excellent developer website, and (10) showcasing examples of apps built with the API.
HubSpot moved from an application-focused company to a platform company by building an app marketplace. They saw marketing transition from an outbound push model to an inbound pull model, and their own tools fragmented across different vendors. Their solution was to create an integrated platform and open their APIs, allowing partners and customers to build apps. They released over 40 apps in 4 months, seeing rapid growth in installed apps. To successfully build an app marketplace, HubSpot focused on good customer experience, compelling incentives for developers, strong developer support, and internal commitment to APIs.
This document discusses Klout's API and platform strategy. It notes that Klout has 3000+ API partners and 6 billion API calls per month. It outlines Klout's approach to measuring consumer value, controlling the platform through terms of service and tariffs, incentivizing consumers, and growing the platform. The document provides details on Klout's REST API design, how it measures and segments consumer value, controls the platform, incentivizes consumers, and plans to grow through partnerships, data, and further integration of Klout scores.
Business of APIs Conference 2011 - UnicornsMashery
This document discusses unicorns, which are defined as developers, fanboys, early adopters, hackers, and community members who are passionate about a product. Unicorns are valuable for their community support, institutional memory, beta testing, potential as future employees, and passion. However, supporting large numbers of people can be difficult due to increasing support costs, divergent views, and development time. The document suggests empowering unicorns by making them forum moderators, allowing them to write blog posts, giving them early access to features, and rewarding them with presents. It also advises iterating the product, API, and community based on unicorn feedback.
Business of APIs Conference 2011 - SwordfishMashery
This document profile introduces Ben Metcalfe, the founder and lead consultant of Swordfish Corp, and discusses recent trends in mashups built using popular APIs from Twilio, Twitter, Facebook, and Google Maps. It suggests that Swordfish Corp is now both a customer and partner of these API providers, and that they will continue to be important to the company's future work.
The document discusses the Netflix API and its transformation of streaming. It describes how the API handles over 1 billion requests per day across hundreds of devices. The API provides personalized recommendations and metadata about movies, TV shows and similar content. Netflix is focusing on redesigning the API to improve its scalability and efficiency to support continued growth.
The document discusses strategies for marketing APIs to developers and IT operations professionals. It advocates targeting individual "doers" rather than large enterprises, providing self-service sign up and documentation, and having an easy-to-use SDK. It also notes that adoption involves attracting visitors to the website, getting them to sign up, pay, and eventually having a sales team to provide full service support for larger customers. The focus is on empowering developers and operations staff rather than traditional enterprise software sales approaches.
Business of APIs Conference 2011 - ProgrammableWebMashery
The document discusses the growth and state of the open API market. It notes that the number of APIs has grown exponentially in recent years and is now over 4,000 tracked by ProgrammableWeb. It also discusses the diversity of API types across sectors like ecommerce, travel, music, enterprise, shopping and social. Additionally, it outlines the evolving business models for APIs, noting a shift towards APIs being the product themselves rather than an extension of existing products or websites.
Mashery Presents: The Evolution of Distribution - Edwin Aoki, Chief Architect...Mashery
Whether you are in retail, media, publishing, technology or travel, the ability to distribute information onto the multitude of internet connected devices has become a challenge for even the most nimble of companies. Everyone is vying for the attention and eyes of the consumer. It is a new world and consumer expectations have changed when it comes to the way content/data/inventory is distributed, discovered and consumed. This change in distribution, in part, is due to the adoption of APIs (Application Programing Interfaces). Businesses who have leveraged APIs have made it more than just a "database of stuff", but rather, have created a platform by which they are now basing their business strategy. Speakers from Mashery, Best Buy, eBay/PayPal and Netflix joined to explore the "Evolution of Distribution" and examined the notion of "why every brand needs an API".
Mashery Presents: The Evolution of Distribution - Kumar Kandaswamy, Director,...Mashery
Whether you are in retail, media, publishing, technology or travel, the ability to distribute information onto the multitude of internet connected devices has become a challenge for even the most nimble of companies. Everyone is vying for the attention and eyes of the consumer. It is a new world and consumer expectations have changed when it comes to the way content/data/inventory is distributed, discovered and consumed. This change in distribution, in part, is due to the adoption of APIs (Application Programing Interfaces). Businesses who have leveraged APIs have made it more than just a "database of stuff", but rather, have created a platform by which they are now basing their business strategy. Speakers from Mashery, Best Buy, eBay/PayPal and Netflix joined to explore the "Evolution of Distribution" and examined the notion of "why every brand needs an API".
API Leader Mashery Captures Application Developer Trends with Developer PulseMashery
Mashery, the leading provider of API (Application Programming Interface) management and strategic services, revealed key insights from the Mashery API Developer Pulse, a study that polled more than 550 mobile and Web application developers at the South by Southwest Interactive (SXSWi) event in March 2010. The Mashery Developer Pulse asked industry leading developers to sound off about the APIs they choose to build with and why as well as asking general questions about the development environment today. Developers put Google, Twitter and Amazon at the top of the list for the “best APIs” available for application development, and also revealed a long tail of dozens of APIs that developers enjoy working with on a regular basis.
Mashery, the leading provider of API (Application Programming Interface), polled more than 550 mobile and Web application developers at the South by Southwest Interactive (SXSWi) event in March, 2010 to track trends in API.
What can be done with an API is limited only by imagination. However, what should be done using your API may have a more definable answer. Whether you are planning to leverage your API to extend your business model into new channels or to capture new revenue, it is The Business of APIs.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
1. Why Your API Sucks
Business of APIs Conference, NY, 10/19/2011
An API developer survey opens Pandora’s Box
http://bit.ly/trove-survey-results
Jesse Emery, Co-Founder
www.yourtrove.com
j@yourtrove.com
@ejesse
#apisuck
10/19/2011
1
Thursday, October 27, 2011
2. We did a survey on API Pain
It made some waves
You can view it here:
http://bit.ly/trove-survey-results
10/19/2011
2
Thursday, October 27, 2011
3. “Facebook Wins ‘Worst API’ in Developer Survey”
- TechCrunch
“Developers relate a tale of woe with Facebook's
API”
- The Inquirer
“Developer survey finds Facebook has the worst
API”
- ZD Net
10/19/2011
3
Thursday, October 27, 2011
4. Booooring
It’s no real secret that Facebook’s API is widely loathed
10/19/2011
4
Thursday, October 27, 2011
6. Developers Hate Your API
“Every integration is its own
[expletive-deleted] adventure.”
10/19/2011
6
Thursday, October 27, 2011
7. APIs don’t live in a vacuum
10/19/2011
7
Thursday, October 27, 2011
8. APIs don’t live in a vacuum
10/19/2011
8
Thursday, October 27, 2011
9. “different idiosyncrasies, ie rate limiting, terms
of service, data format, old documentation etc.”
“REST vs. XML-RPC vs. SOAP,
JSON vs. XML vs. Random POST data.
Every API seems to be different”
“REST uses the HTTP spec, but few API providers
actually follow the spec properly.”
10/19/2011
9
Thursday, October 27, 2011
10. “Guarantee me that any API you
support will exist in its current form
(bugs and all!) for at least 12
months, and I will give you so much
fucking money.”
10/19/2011
10
Thursday, October 27, 2011
11. “Guarantee me that any API you
support will exist in its current form
(bugs and all!) for at least 12 months,
and I will give you
so much fucking
10/19/2011
11
Thursday, October 27, 2011
13. Where else are you losing
Developers’ $$$?!
10/19/2011
13
Thursday, October 27, 2011
14. Your Documentation Sucks
“poor documentation” mentioned 41 times
“lack of good examples + sandboxes”
“Documentation and examples. Give me those,
keep them up to date and I’m happy.”
10/19/2011
14
Thursday, October 27, 2011
15. Y U No Update Documentation?????
10/19/2011
15
Thursday, October 27, 2011
16. Your Error Handling and
Test Environments Suck
“error handling” a frequent complaint
“Complete lack of test environments.”
“The ones that you can’t test from a localhost
suck”
10/19/2011
16
Thursday, October 27, 2011
17. We suck more together
Inconsistent standards, libraries, and
documentation
“REST vs. XML-RPC vs. SOAP,
JSON vs. XML vs. Random POST data.
Every API seems to be different”
“Change is good, but change when it breaks
existing 3rd party API’s is a nightmare.”
10/19/2011
17
Thursday, October 27, 2011
18. We suck more together
“Random 3rd party outages that take you out as
well”
Error Codes differ between services.
On bad Auth, Some 404, others 401 or 403.
And some 500. This is hell on devs.
“Different data formats from different services
for essentially the same data.”
10/19/2011
18
Thursday, October 27, 2011
19. And there’s so much other
confusion
Authentication vs. Authorization
Oh do developers hate OAuth
(users, too!)
Actually getting through to stakeholders (that’s
YOU)
Rate limiting and billing
10/19/2011
19
Thursday, October 27, 2011
21. “Paypal. Sweet god, fuck paypal.” “OMFG Salesforce
“Digg is basically a giant API sucks. That is
example of ‘this is how to not all”
do it’.”
“Affiliate + API —
“Netsuite SOAPs almost no one does it
documentation is, umm… right.”
completely fucking incorrect”
“We’re still working on
“Too many to relate.”
it.”
10/19/2011
21
Thursday, October 27, 2011
29. Developer Bill of Rights
What can they expect from ALL of us?
10/19/2011
29
Thursday, October 27, 2011
30. Hold our own accountable
10/19/2011
30
Thursday, October 27, 2011
31. Better APIs = Happier Developers =
Happier Customers = more $$$
10/19/2011
31
Thursday, October 27, 2011
32. Recap
We’re not in this alone
We need to start thinking like team players
Cooperation amongst ourselves makes developers’ lives
easier
Which means better adoption, retention, and revenue
10/19/2011
32
Thursday, October 27, 2011
33. Your Business is NOT your API. It is
what that API provides access to.
So fix your API and the ecosystem around it!
10/19/2011
33
Thursday, October 27, 2011
34. Thank you #BAPI!
http://bit.ly/trove-survey-results
Jesse Emery, Co-Founder
www.yourtrove.com
j@yourtrove.com
@ejesse
10/19/2011
34
Thursday, October 27, 2011