Shay Weiner, Product Manager @ Wix Code
An API is not "yet another
feature"
shayw@wix.com linkedin/shayweiner
For Engineers
Netflix is able to
stream to over 200
different device types
thanks to its API.
60% of eBay’s listings
are done through their
API.
50% of Salesforce
transactions are done
through their API.
Twitter receives over
13 billion API calls
daily.
The special role of engineers
in adding an API to a product
TODAY
Software
Engineering
at BGU
Full Stack
developer
Team
Leader
Engineering
Manager
Product
Manager
@Wix Code
About me
Unique experience
Unique business logic
Configuration hell
Unique experience and
flows
Wix Code
Wix Code
▪ Wix elements
▪ Site database
▪ 3rd party services
▪ Wix solutions (e.g., Wix Stores)
▪ Node server
▪ Site API
▪ Report events (Facebook pixels)
import wixData from 'wix-data';
$w.onReady(function () {
return wixData.query("myCollection")
.find()
.then( (results) => {
$w("#myTable").rows = results.items;
} );
} )
Wix.com/code
Business
Justificatio
n
Wix Code APIs
allow Wix experts to offer unique
experience and flows for their clients
Business
Justification
Slack APIs
allow 3rd party applications to push / pull data
Business
Justification
Netflix is able to
stream to over 200
different device types
thanks to its API.
60% of eBay’s listings
are done through their
API.
50% of Salesforce
transactions are done
through their API.
Twitter receives over
13 billion API calls
daily.
Business
Justification
Engineers should help answer the question:
Who is going to make money using the API?
Business
Justification
New type
of users
A developer user
persona is different
from existing users, and
they’re the ones who
use the APIs.
Developer
User Persona
Existing experience Developer Experience
Developer
User Persona
Documentation
Existing users
How to videos & articles
Inline tooltips
Integration/application engineers
on site (B2B)
Developers
API Reference
Code examples
Developer
User Persona
Developer
User Persona
Developer
User Persona
User experience
Existing users
Consistent UX patterns
Consistent look & feel
On boarding
Developers
Getting started tutorial
SDK for multiple programing languages
Test console
Test kits
Developer
User Persona
Support
Existing users
Call center
Ticketing system
On site
Developers
Forum
Community
Developer
User Persona
Marketing
Existing users
Paid ads
Related industry conferences
Developers
Meetups
Developers forum (Stackoverflow, Hacker
news)
Hackathons
Educate your organization and take
the lead on developer experience.
Developer
User Persona
Product
scope
Usually goes like this
Dear developer, here are 5 features solving a user problem
please provide an effort estimation.
...
...
...
Product
Scope
IN
Feature 1
Feature 3
OUT
Feature 2
Feature 4
Feature 5
Product
Scope
IN
Feature 1
Feature 3
OUT
Feature 2
Feature 1
Feature 3
Feature 4
Feature 5
API
Product
Scope
Feature 1
Feature 2
Feature 3
Feature 4
Feature 5
API First
Product
Scope
Feature 1
Feature 2
Feature 3
Feature 4
Feature 5
IN
Feature 1
Feature 3
API First
Product
Scope
Wix Registration form
Product
Scope
Custom Registration form
Product
Scope
IN
Custom Registration UI
OUT
Custom Registration UI
with no code
Register new user
API First
Product
Scope
Community video
Product
Scope
API-First forces you to focus on the most
critical functionality
Product
Scope
When the API
goes public
Ariel has limited resources
When API
goes public
As long as she controls the access
she doesn't need to scale
When API
goes public
Introducing API means you lose control
of how customers use your product
When API
goes public
Prepare to scale...
When API
goes public
...and scale more
When API
goes public
Measure
Success
Unique business logic
Measure
Success
Count unique developers
Measure
Success
Measure conversion to active usage
Measure
Success
Talk to your users and non-users
Measure
Success
Q&A
shayw@wix.com linkedin/shayweiner
Thank You
shayw@wix.com linkedin/shayweiner

An api is not "yet another feature"