Chapter 3. Componentizing
Our app has lifted off and taken flight—hooray! We’re going to continue our adventure of learning Blazor by scrutinizing code. In this chapter, you’ll learn how to author Blazor components and various data-binding approaches. Now that you’re familiar with how the app starts, we’ll evaluate the default route of the app. This just so happens to serve the Index.razor file, which is the home screen for the app. You’ll learn how to limit what a user has access to by protecting components with declarative attributes and security-semantic hierarchies. You’ll see native JavaScript geolocation services in use with JavaScript interop. As part of this chapter, you’ll also learn about some of the peripheral services and supporting architecture that the Blazor app relies on, such as the “Have I Been Pwned” service and Open Weather Map APIs.
Design with the User in Mind
All graphical-based applications have users, but not all applications prioritize the needs of their users. More often than not, apps use your information to drive advertisements or sell your information to other companies. These apps view you (the user) as a sales opportunity or a data point.
The Learning Blazor app was designed with its users in mind. As such, it authenticates the user’s identity to determine what actions the app takes (for more information, see “Identity and Authentication”).
When users log in to the app, meaning, once the web server has authenticated a user with the Azure AD B2C ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access