12 Deploying apps to production with GitHub Actions

 

This chapter covers

  • Preparing your apps to be used by other people
  • Providing your own icon and splash screen
  • The Apple, Google, and Microsoft developer programs
  • Continuous integration and continuous delivery with GitHub Actions

Congratulations! You have built a complete, nontrivial app in .NET MAUI. Building apps is fun, but sadly, very few people get paid to build apps just for fun; usually, there’s an expectation that you will deliver a working app to users.

We’ve come a long way since the start of this book. We began with “Aloha, World!,” and we’ve built a location-sharing app, a to-do app, a movie recommender, and now an enterprise stock-taking app. Getting to where we are now has been a long journey, and the last, and arguably most important, step is to get our app deployed. Once you have a build of your app that’s ready to deploy to your users, there are a few final pieces of polish you need, outside of the app’s functionality, before you have a finished product.

12.1 App icons, splash screens, and app identifiers

12.1.1 Replacing the default app icon

12.1.2 App icon composition

12.1.3 App icon resizing

12.1.4 Replacing the default splash screen

12.1.5 Application identifiers and version numbers

12.2 Deploying apps with GitHub Actions

12.2.1 Setting up the workflow

12.2.2 Build and sign the Android job

12.2.3 Build and sign iOS job

12.2.4 Deploy to stores job

12.3 Next steps

Summary