2. Jamie Parkins – Product Manager (@jamieparkins)
- Introduction to JustGiving
- Growing API adoption in a new market
Pawel Sawicz – Developer Evangelist (@sawiczpawel)
- Making your API a first class citizen
3.
4.
5.
6.
7. What is JustGiving?
•World’s largest donation platform for charities & not for profits
•24 million users, across 164 countries
•>100,000 new registrations a week
•1 million fundraising pages created in per year
•£1m+ a day raised for global causes
•£3bn+ raised for global causes since launch
•Our technology enables people to build #tech4good
8.
9. Diving into the numbers
5k strong developer community
Top 50 UK charities using our API
1m + pages created via the API
API partnerships (Co-Op, Spotify etc)
25% of revenues via API created apps
10. But this was not always the case!
50% of charities had
limited or no
understanding of APIs
50% of charities had
limited or no
understanding of APIs
Source: JustGiving API survey Feb 2014
11. • Cancer Research - our # 1 charity
• Raised > £60m on JustGiving in 2014 alone
• Big enough to have an innovation team
• In 2010 expressed a desire to “stay ahead of comp” and to “leverage tech”
• Today all their fundraising campaigns are driven by JustGiving API
• Took 3 years to get to this stage
• Lots of blood, sweat and tears
• Test & learn, test & learn…
• This trust in our system was a industry wide game changer
• They singularly validated our API stack
Lesson 1: Pick a significant launch partner
13. • Get out and meet your future clients (e.g. charities, agencies)
- Show them real life, tangible examples
• Find ways to get round lots of red tape / bureaucracy
- Test things quickly (prove/disprove, move on)
- Co-fund projects
• Be prepared to coach, guide, review and tweak
- Demos, flow diagrams etc
• Train up those that can broadcast the API message
- Account Managers, Bus Dev, PR etc
• Prepare for a slow life cycle of development
- And meantime plan for what they will want next
Lesson 2: Be prepared to put in the hard yards
15. • Focus on “time to Hello World”
• Pick an API service provider that suits your needs
• Live or die by your documentation
• Provide a reliable sandbox
• Build and nurture your community in help groups or forums. Zero in on your biggest
advocates
• Empower other staff to answer questions – grow the knowledge
• Plan for CRM & Developer outreach (emails, customer care, doc updates etc)
Lesson 3: Invest in making life easy for others
28. What’s next?
1. Encourage, amplify and celebrate innovation
2. Building and getting behind the #tech4good movement
• Hacks
• Meetups
• PR
3. Continue to extend the JustGiving platform to meet need
4. Growing number of partnerships
5. International
In short, we have built a platform, that supports a world where everyone can give will give.
We enable the traditional fundraising model of sponsorship by bringing it online
We are NOT a charity. We reinvest our profits into technology
£1bn raised since 2002
Can donate in multiple global currencies
So who exactly are JustGiving? Some quick stats.
Questions to ask :
Who here has an API at their company?
Then
Who here uses that API internally?
dogfooding - Eating your own dog food, also called dogfooding, is a slang term used to reference a scenario in which a company uses its own product to test and promote the product. (source wikipedia).
In short way, you use your product in your daily job, like github does, they keep github srouce code in Github :) Incepction....
First benefit that I can spot now is that you can very easy prototype and experiment new projects,
instead of messing up with internal infrastructure all you need to do is consume existing public API.
The bigest benefit, in my opinion is that dev team that use public API for their work become your client,
and they can very easy evaluate everthing what you have done. If you introduce something new they will quickly evaluate this, constant feedback.
By having dev team as your customers I have to mention about finding bugs,
it's another great pro, you will find bugs erlier than before and it may affect less customers of your API.
By having dev team as your customers I have to mention about finding bugs,
it's another great pro, you will find bugs erlier than before and it may affect less customers of your API.
Wider knowledge about public API across dev team, it's very hard to keep whole dev team aware of API and customers that consume our API,
especially when only API team is contribution to code, or were building software.
Questions to ask :
Who here has an API at their company?
Then
Who here uses that API internally?
Next step in dogfooding was to consume our SDK and tools that we have created for our community, http://widgets.justgiving.com/ is using https://github.com/JustGiving/JustGiving.Api.Sdk.JavaScript. Also we created a complete collection of our resources for postman https://github.com/JustGiving/JustGiving.Api.Tools.Postman and loads of developers in JustGiving