API Product Manager
Give wrong viewpoint that APIs are seen as pieces of other products, explain why it's flawed
Traditionally, but wrongly, APIs have been considered pieces of other products. - They've been built by the IT team at the request of product owners every time a project came up that required one. -When the funding spigot is flowing, APIs generally receive support. - But once the project runs its course, the APIs are neglected and quickly grow outdated.
Custom information and transactions example?
offers information and transactions that are tailored to the customer using the app. -mapping specific vehicles to required services, managing recalls, assessing trade-in value and scheduling service appointments.
What to do once vision is finalized?
- clearly communicate the benefits to developers, consumers, and business stakeholders. -promote and launch the API for use in appropriate ecosystems and manage the integration pipeline. -They also seek feedback and optimize the experience of everyone in the ecosystem. -By applying all of these practices, the manager can ensure the API is used by a sufficient audience and sustains long-term business value.
the product manager helps the overall organization develop a vision for its API products. How?
- identifying which APIs are required, based on the needs of the business, internal and external developers, and consumers—which may be customers or internal end-users. -Another key factor is the cost to develop APIs and the value they will produce. Like any business, an API must generate a significant ROI.
API Development?
-Develop API proxies using UIs -test and debug -documentation of use
One of the biggest challenges API product managers face is that they need to make sure APIs deliver the value that's expected from a wide range of stakeholder groups:, give some examples
-Developers who create and maintain APIs, including adding new features and fixing issues. -Internal developers who consume private APIs to integrate business systems. -Partner developers who consume APIs restricted to use within strategic business relationships -Third-party developers with access to public APIs. -Internal end-users who rely on APIs to enable business processes spanning multiple applications to run smoothly. -Customers who rely on APIs to conduct online business efficiently. -The business unit leaders that own the APIs
Monetization
-Different plans and charges, tiered approach -API usage -track and billing
After an API is launched, the product manager should?
-FEEDBACK, analyzes consumption data and gets feedback from developers and end-users to identify necessary improvements and fixes and to see how well the API integrations are generally working. -PRIORITIZE IMPROEMENTS, Any required changes should be prioritized to make sure the biggest pain points and opportunities are addressed first. -DOCUMENTATION, And as changes are implemented, update the API documentation so consuming developers can easily take advantage of the changes.
API quick win strategy?
-Product-minded companies frequently launch APIs as minimum viable products in order to get ideas to market faster, -then use API consumption analytics to understand developer engagement -and refine APIs to be even more attractive, powerful, and intuitive.
Monitoring?
-Quality spills, -Tracking and trend usage -Root cause analysis
Security?
-Security, protecttion against Denail of service and hackers,maybe machine learning ability -digital signatures and encryption -END GAME, cross-functional internal groups and third-party partners are comfortable using it
Three questions lead to a good API:
-Who is the f*cking audience? -WTF do they want? • - Under what terms and conditions are you willing to make the asset available
Implications of neglecting APIs? (think cross functional implications)
-Without consistent resources, APIs can't be adapted to fluctuations in the enterprise and market dynamics. -Worst of all, project-oriented APIs often end up siloed within the business unit that gave birth to them, -which defies the benefit of modern APIs: to not only allow enterprise assets to be reused by other business units and partners but also accelerate the business's innovation by increasing the number of developers interacting with its capabilities
Tasks associated with the API product manager role include: (five key attributes)
-Working with the domain owners to identify desired business APIs to bring to market • Working with the API developer to drive the creation of the API • Reporting to executives on metrics • Defining the product characteristics of the API (monetization, rate limits, audience and so on) • Communication (SCOPE, CREATE, EXECUTIVE REPORTING, REQUIREMENTS, TRANSPARENCY)
WTF to do begnning of lifecycle?
-creating the business and product requirements based on all stakeholder needs - understanding the API technical specifications that developers will need to adhere to. -While working with the developers who create APIs, ensure they follow standards, naming conventions, design principles, and consistent development methods. This will give the developers and end-users that consume the APIs more uniform experiences.
developer POV?
-easily to find and integrate APIs and -determine if they deliver the required functionality they seek for their applications. -ALUE while MINIMIZE FRICTION
API life cycle management?
-inception abd implementation from cradle to grave -versions to deal with changing requirements
Socialization?
-self registration and subscription -Blog, rating, comments -incident tickets -Social media
Application programming interface (API) is a very old term that has been used to.......
API technical interfaces for software programs where one software program calls another through its API. Often, these APIs were extremely complicated and not really meant for wide consumption. A few other software programs inside the enterprise might use the API to invoke the program; a partner outside the company might use it as well, but with great difficulty.
What links all of them together?
API, Application Programming Interface APIs are a foundation of modern application architecture, supporting application composition, multi-experience development, integration, and ecosystems
How do APIs act as the glue?
APIs can be the glue that binds a company's resources together and the mechanisms through which an enterprise's data, functionality, and other digital assets are accessed and distributed. They enable software systems to communicate and let developers leverage software for new applications and digital experiences, abstracting underlying complexity into a consistent interface that allows data and functionality to be combined and reused with unprecedented flexibility.
WTF is API MEAN?
An API is a piece of software within a system that defines how other components or systems can use that system. The API defines the types of requests that can be made, how to make them, and the data formats that must be used. As the acronym suggests, an API consists of three components: -Application refers to the primary service you are accessing, whether it's a website application, a spreadsheet, a mobile app, kiosk, or your company's internal ERP application. The application lets you access information and input data to complete a specified task. For an application to execute transactions, it needs to interface with you and other applications it relies on to run certain functions and grab the required data—such as a back-end database. -Programming refers to the software code that allows the service you are using to communicate with you and other applications. The code translates your requests into a language that other applications can understand so they can fulfill the request—such as asking an ATM to withdraw cash. The ATM uses the API code to check with the bank database to make sure you have sufficient funds. -Interface is the view you see when you interact with the main application. This could be a set of fields into which you key-in data, or it could be a touchscreen or a keypad. It could also be the chip reader on a credit card processing device or a barcode scanner. All these graphical user interfaces enable you to communicate with applications.
Virtually all traditional product ownership responsibilities can be easily applied to an API. how?
An API product owner is responsible for galvanizing the entire company around their API's value. Their team can answer any questions users may have about the API's value proposition or how to use it.
Public API examples?
Auto companies can deploy many of the same APIs used internally and with partners as public APIs to drive additional business and help obtain new customers. Car purchasing is extremely competitive. Apps from Autotrader, Cars.com, Edmunds, Kelley Blue Book (KBB), TrueCar and many others enable buyers to compare cars from multiple manufacturers to enhance the buying experience. -All can benefit by accessing public APIs to obtain car offerings and accessories, details, prices, reviews and so on
Devices questions
Devices - Does your company handle devices such as cars, appliances, sensors or meters? - What scenarios can apply to the device? For example, needing repair/supplies, needing to send status information, controlling device behavior or enabling interaction between the device and enterprise systems. - How are you positioned to integrate the next UI technology, such as wearables like smart clothing or augmented-reality glasses?
end users and customer POV?
For internal end-users and customers, APIs always operate seamlessly in the background. In other words, they should never know the APIs are even there. If someone from one of these groups reports a problem that points to an API as the culprit, the product manager isn't doing their job! -NO FRICTION OR FOOTPRINT
Internal developer (mobile app development) example
General information is information that is not tailored to the specific customer using the app. It may include general information about the auto manufacturer and its offerings, such as product catalog and product descriptions, available accessories, incentives, owner's manual information, service locations, product pricing and availability, and ratings and reviews. For dealerships, sample APIs include location, open hours, available inventory and prices.
Give some examples of what API connects?
It's a core man! Mobile devices, connected homes, tablets, COnnected Auto, Big Data, Web Application, Business Partners
Infotainment partners example?
Partners supply many automotive components such as the radio, navigation system, phone integration and entertainment systems as well as safety capabilities such as lane warning systems, close vehicle alerts and so on. -These partners need to access auto APIs to integrate with the car's activity, and the partner offerings provide APIs for hands-free controls to help improve safety. -All of these components add value to the car and generate revenue for both the auto manufacturer and the partner.
Public questions?
Public - What apps might others write that could use your data and transactions? - What information are you currently making available on your website? - If there was a comparison app for you versus your competitors, would you want to be listed as an option? What data would the app need? - What other industries or processes might also use your products? One example might be offering your APIs to businesses that target families preparing to send a child to college—a process that might also involve purchasing a new vehicle. The college preparation site or app can use your APIs to market your automobiles to that target customer. - Think mashups: What other APIs might make sense with yours? Mapping? Social
Mobile advantage API examples?
Sample device functions include the camera, GPS services, near-field communication (NFC) and digital wallet
Key takeaway of API relation to cars
The automotive industry is one of the most active industries in the API economy. Car-shopping apps are prevalent, and it is becoming common for APIs to supply the necessary information to compete for customer business. Connected car scenarios— supported through APIs—are also exciting the marketplace. If your enterprise has not started strategizing and planning for business APIs, the time is now. Do not wait until you know all the answers and have everything in place to begin. The market is moving too fast. Plan stages for the rollout that build on what you learn
Best way to keep stakeholders happy?
The best way to keep all stakeholder audiences happy is to pay close attention to the day-to-day details of API product management. - The manager monitors each stage of the API product lifecycle from development to testing (functional, security and performance), deployment, iterations/release management, and retirement
Remote services example?
Theft, impact alert, tire pressure, oil pressure, remote start, lock/unlock, vehicle finder,
Why are business or web APIs so coveted?
These business or web APIs are easy-to-understand interfaces for a recognizable business asset—for example, a customer record, an account, a product catalog, a price, an order and so on.
After determining who can access an API and preparing for monetization, if applicable, the product manager determines how to expose the API and make access easy for consuming developers. how?
This includes creating mockups or prototypes for testing, which lets developers build integrations faster. It also helps to post sample use cases, documentation, and release notes. -PROTOTYPES and MOCKUPS -CASES AND EXAMPLES
Give examples of how APIs are underestimated
Unfortunately, many business leaders see APIs as middleware and thus as undeserving of the resources of a full-fledged digital product. -Their organizations create APIs as one-off projects, with engineers moving on to other projects when they are done and no one looking after an API's maintenance or whether it offers utility beyond the bespoke use case for which it was created.
Because both consumers and developers will abandon products that do not meet their needs, an outside-in perspective is increasingly non-negotiable. The product owner needs to do what? (key, 50% of his time should do this)
analyze rapidly-changing market trends, understand the competitive landscape, keep a pulse on customer and stakeholder needs, and facilitate a backlog of changes that can help the company satisfy the market. Essentially, API product owners are the end-user advocate — and that's for both for developers using the APIs and the people touching the applications powered by those APIs.
Why is API managment important? (think about quantity, and structure, and execution)
enterprise has hundreds of digital assets as APIs, and demand skyrockets. So you need a strong framework able to leverage full potential, with scalability upwards for demand.
Implication of embrasing APIs?
if an API is treated as a product in its own right with its own owner lobbying for consistent funding, the API can be iterated according to shifts in internal and market trends.
Role of API product manager?
just like running a business. Product managers need to - direct the production (development) of APIs and cultivate a market of users— -which may or may not involve selling (monetizing) the APIs to generate revenue. - also responsible for customer service, making sure developers and end-users that access the APIs get what they need.
Perhaps the most important role an API product owner must fulfill is maintaining a staunch outside-in approach. Explain
outside-in approach requires the company to listen to what the market is asking for and to respond appropriately. Outside-in thinkers start by asking what the customer needs, then build strategies from there. Because customer preferences are moving targets, an outside-in perspective is constantly evolving and seeking new data. In the case of API programs, product managers should find ways to align API user data with business KPIs, which can be essential to organizing stakeholders and achieving buy-in for the program throughout the organization
5 themes defining today's digital spectrum?
social, mobile, analytics, cloud, internet of things
What would a good API owner do? (think about data and analytics and how it relates to engagement)
the product owner should continually monitor an API's engagement and collect and synthesize analytics to improve quality of service.
Business leader POV
there are the leaders of the business unit that API product managers ultimately answer to. They "own" the APIs and expect them to enable business processes to work more efficiently and/or produce sufficient revenue.
• Internal developers (mobile) questions
• - What data and transactions would your own mobile apps need? - Does generic data exist that is the same for all app users, such as business locations, rates and so on? - Is there data specific to existing customers that should be accessible through your app, such as when to schedule service or check on repair status? - What features of the mobile device—for example, the GPS or the camera—might be useful in conjunction with your APIs?
• Social questions?
• Social - How do your systems interact with social media? Can you spot trends in social media and raise alerts or take action? - Can you gain insight on your brand and your competition through social media? - Can you do real-time analytics combining current customer status, behavior and history with social interactions?
