Building your next mobile app, SaaS product, or web app using an API first philosophy is a great decision. It can allow your team to develop in parallel, enable expansion to multiple platforms, and create opportunity for outside integration. But once you've made that decision, what's next? How do you actually do it? What options are there for authentication? How do you reset a password with an API? Is hypermedia worth considering for internal APIs? How do you handle unauthenticated access from a client side javascript application? What format is best for API requests and responses? Should you version your API now, or later? In this hands on workshop we'll talk about all those questions, and the answers that give your API a solid foundation. Because your API may start out serving the needs of internal mobile clients, or single page web apps, but one day (and probably sooner than you think) you'll be turning it into a public API.


Comments are closed.

Very informative and made me think of how our API was designed. Can't wait to take some of these ideas and concept and implement. While I know that not many people develop on windows, I have to and would recommend looking into Fiddler as an API tool for Windows.

Ryan Howe at 09:46 on 20 Nov 2018

Great discussion on API design. I did get a little lost getting the source code to the correct branch when we were following along. The discussion format felt a little forced and I think it could have been guided a little more but the over all concepts are great and the tools and ideas presented are very useful and sound. I am excited to utilize these ideas in the future.