API

  1. 8:00am

    Registration & Coffee

  2. 9:00am

    Keynote Coming Soon!

    Speaker to be Announced
  3. A photo of Joe McCann
    9:50am

    API First Development

    Joe McCann

    Description Coming Soon!

  4. 10:35am

    Morning Break & Networking

  5. 11:15am

    Session Coming Soon!

    Speaker to be Announced
  6. A photo of Kirsten Hunter
    11:50am

    Designing Irresistible APIs

    Kirsten Hunter

    When creating a new REST platform, the planning process frequently gets skipped (or is misunderstood) resulting in an ill-conceived API. I'll walk you through the steps needed to create an API that developers love, and point out the common traps to avoid. The presentation will cover creating user stories, deciding on metrics, planning the API, design decisions, documentation and developer support. I will focus on teaching you how to create a developer experience that will delight and amaze your developer partners and increase engagement with your platform. This talk will focus on higher level choices rather than HTTP architecture, and is appropriate for developers, product managers, or anyone else with an interest in achieving success for their API program. The Open API Ecosystem is an amazing opportunity for companies to partner with developers, but you really only get one chance to impress, so come learn how to make your company's API an "A List" destination. What should the audience expect to learn from your talk?: *API Developer Experience *API Use Cases *Measuring Success

  7. 12:35pm

    Lunch & Activities

  8. 1:35pm

    Device APIs - Contextualize your Apps

    Speaker to be Announced
  9. 2:25pm

    Session Coming Soon

    Speaker to be Announced
  10. 3:10pm

    Afternoon Break

  11. 3:45pm

    Session Coming Soon!

    Speaker to be Announced
  12. A photo of Keith Casey
    4:20pm

    12 Reasons Your API Sucks

    Keith Casey

    Those first moments of using an API are pivotal. There’s nothing like downloading this week’s PDF of the documentation, setting up a SOAP client, reconfiguring all your URLs, and decoding the latest binary payloads. It makes your heart sing and your blood pressure rise. Just like there are code smells through the rest of your project, there are API smells that make them hard to design, hard to launch, and hard to maintain. We’ll use this time to explore a few common APIs to highlight those issues and demonstrate strategies to fix the issues before they become problems.

  13. A photo of John Sheehan
    5:10pm

    Keynote - Dealing With Problems Whilst Working With APIs

    John Sheehan

    Description coming soon!

Modern Dev

  1. 8:00am

    Registration & Coffee

  2. 9:00am

    Main Stage Only

    Speaker to be Announced
  3. A photo of Keith Casey
    9:50am

    REST Best Practices

    Keith Casey

    When we discuss APIs, most people immediately think of OAuth, GET and POST, and JSON. A few people think of the underlying concepts of nouns and verbs, idempotence, and uniform interfaces. But even less consider how we can combine these concepts into hypermedia to build APIs that are useful, logical, and future-friendly. Luckily a number of people are already on the outer edge building and experimenting with these concepts to give us perspective on what's to come. In this presentation, we'll begin with the basics, combine them to describe the larger concepts, and look at the standards that are leading the way.

  4. 10:35am

    Morning Break & Networking

  5. 11:15am

    Main Stage Only

  6. A photo of Jason Lengstorf
    11:50am

    You Need a Development Process. (Yes, You.)

    Jason Lengstorf

    We've all had the meeting: ""At some point (in the distant to far-distant future), we need to standardize our development process."" Everyone nods, someone jots down a note to ""keep this on our radar"", and everyone leans back and thinks about how great it will be when there's a common setup. Then, of course, nothing actually happens, and the utter chaos of process-less development resumes. We're better than this. In this talk, we'll cover some of the problems we can solve with a standard process, some of the solutions that can quickly make your life easier. Some of the issues that can be solved include: • Busywork — like image compression and JavaScript minification — that you have to do on every project • Rewriting emails that you've written a hundred times before • Rebuilding that one feature that you built before but removed during the last round of feedback before the client changed their minds again • Remembering how what's-his-name names variables so you can debug his code • Forgetting how your manager wants projects to be turned into her for review All of these problems can be fixed — or at least vastly improved — with simple processes, standards, and templates. Whether you work on a large team, or as a solo freelancer, you will benefit from adding processes to your workflow.

  7. 12:35pm

    Lunch & Activities

  8. A photo of Alex Sexton
    1:35pm

    Client-side Security Best Practices

    Alex Sexton

  9. 2:25pm

    Session Coming Soon

    Speaker to be Announced
  10. 3:10pm

    Afternoon Break

  11. 3:45pm

    Main Stage Only

  12. 4:20pm

    Session Coming Soon

    Speaker to be Announced
  13. 5:10pm

    Main Stage Only

Thanks to our amazing sponsors
Sponsors
Media Temple