Disconnected service information
Customers need visibility, administrators need control and technicians need clear assignments. Combining these needs in one application can quickly become difficult to follow.
Featured case study
HomeStride Services
A full-stack platform that connects customers, administrators and technicians through one structured home-services workflow.
- Project type
- Full-stack web application
- Role
- Design and development
- Core stack
- JavaScript, Node.js, PostgreSQL
- Deployment
- Cloudflare and Render
Operations overview
Service management made clearer.
Project overview
A complete workflow, not just an interface.
HomeStride was created to demonstrate how a service request can move clearly from customer submission to technician completion.
Customers can create accounts, save addresses, select a service and submit requests. Administrators review incoming work and assign technicians whose recorded skills match the requested service. Technicians then update the work from assignment through completion.
Each role receives its own protected dashboard and only sees the information and actions relevant to its responsibilities.
The challenge
Coordinating three user roles without making the experience confusing.
Role-specific dashboards
Authentication and authorization direct each user to a focused dashboard while a shared request status system keeps the complete workflow connected.
Key functionality
Features designed around the service journey.
Secure account access
Registration, password hashing, JWT authentication and protected role-based routes.
Service booking
Customers select services, manage addresses and schedule requests through a validated workflow.
Skill-based assignment
Administrators only see available technicians whose saved skills match the requested service.
Visible progress
Status history records submission, assignment, active work, completion and accompanying notes.
Technician management
Administrators can add, edit, deactivate and reactivate technician accounts safely.
Responsive experience
Public pages and all three dashboards adapt to desktop, tablet and mobile screens.
Technical approach
Structured across the full application stack.
Frontend
Semantic HTML, responsive CSS and modular JavaScript connect the public website and three dashboards to the API.
Backend
Express routes, middleware, controllers and validators handle authentication, permissions and service-request operations.
Database
PostgreSQL stores users, services, addresses, technician skills, requests and status history using related tables and constraints.
Deployment
The frontend is deployed with Cloudflare Pages, while the API and PostgreSQL services run on Render.
Outcome
A deployed portfolio project with an end-to-end working process.
The finished project demonstrates more than visual design: it shows authentication, authorization, data relationships, business rules, API integration and production deployment.
Building HomeStride strengthened my understanding of how frontend and backend decisions affect one another, especially when several user roles share the same underlying workflow.