Whether you are building a prototype or a business critical product, Heroku makes it easy to deploy and scale web applications. If you’ve never run a production web application before this might sound intimidating, but don’t worry—we’re going to use Heroku, a platform that makes deploying apps incredibly easy. But first we have a little preparation to do.
In a previous screencasts, we built out a simple but full-featured web service. We have several tables of related data, validation, default values, and authorization. This is great, but it’s also starting to get complex enough that we might break something! Luckily, Rails’ testing support is second-to-none. In this screencast, we'll learn how to set up automated testing for our Rails web service.
In a previous screencast we set up a simple Rails web service for todos and deployed it to production. But right now there's no authorization on it, which means anyone can come along and modify our data. In this screencast, we’ll use the Doorkeeper gem makes it easy to add authentication to Rails APIs using the OAuth 2 standard.
In part 1, we began simplifying our React Native native iOS code by separating an idiomatic Swift class from a React Native adapter. We’re going to finish this extraction by moving over a method that returns data. By the end of this screencast you should be comfortable with writing idiomatic Swift methods that return data synchronously or asynchronously, and adapting them to React Native.
In this screencast, we’re going to look at how to write your native iOS code for React Native in a more idiomatic Swift way. By the end of this screencast you’ll be able to refactor your React Native Objective-C code to be Swift code that isn’t React Native specific.