See how the app to be built through this course is going to be laid out. We'll explore how the Azure Services we will configure will interact with the client UWP app.
- [Instructor] Before we get the tools for the job, let's get a high-level understanding of what we are going to build first. This will help us pick the right tools. At the end of this course, we will have a collaborative project management app with four main views and a navigation view. LoginView, to allow the user to login with Facebook, MyProjectsView, to allow the user to add a new project and view their existing projects, ProjectDetailsView, to view a project's details and allow the user to add a new task or collaborator, and OtherProjectsView, to allow the user to view projects they work on, but do not own.
To tie it all together, we'll have a NavigationView that handles page navigation. Each view will have a view model to handle the business logic. We'll learn more about that as we get closer to the app. We'll also create a Server/Client Abstraction layer to organize our code. Our server code will have a table controller for each of our SQL tables, one for each of the objects we'll be dealing with. We'll also build a Custom REST API for our app to store the user's name and email in our database, so we can easily cache user credentials and not require Facebook authentication on every sign-in.
Finally, we'll heavily use the Azure Mobile Service Client, SDK, to expose a lot of what we need to do in C#. Now that we have the high-level blueprint for our app, let's get the right tools.
- Working with .NET for UWP app development
- Establishing application architecture
- Configuring Azure services
- Configuring the mobile app service backend
- Testing and publishing the service backend
- Using Facebook authentication
- Using XAML
- Client server abstraction API
- Using the UWP community toolkit
- Styling app views
- Creating adaptive views
- Testing an app for multiple user accounts
- Publishing to the Windows Store
- Sideloading app packages