Responsive frontend development

What this bullet means

The employer wants screens that work well on desktop and mobile, with readable layouts, accessible forms, and clear user flows.

Sample app idea

Responsive Claim Status Dashboard where users can search claims, review status history, update contact details, and view next steps on desktop or phone-sized screens.

Main build outline

1. Create a dashboard layout with claim search, summary cards, status history, and next-action details.
2. Design forms that stack cleanly on mobile and remain efficient on desktop.
3. Add loading, empty, validation, and error states for common claim workflows.
4. Check keyboard navigation, readable labels, and useful focus states.
5. Capture screenshots at desktop and mobile widths for the portfolio README.

Portfolio proof

• Desktop and mobile screenshots of the claim status dashboard.
• Screenshot of validation, empty, or error state handling.
• Short accessibility checklist covering labels, focus, and keyboard use.

Minimal documentation

• README with the business problem, screenshots, setup notes, and technology stack.
• One requirements note that maps the job bullet to the sample feature.
• One test plan note with happy path, validation, and edge case checks.
• One honest portfolio note that says this is self-directed practice, not employer work.

Modern .NET stack

• Blazor Server or ASP.NET Core Razor Pages.
• C# services with validation and dependency injection.
• SQL Server locally, then SmarterASP SQL Server or Azure SQL.
• Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.