Hearthlane Services.
A clearer brief before the work begins.
A completed personal home-services project that brings service discovery, task details and request summaries into a coherent customer-facing experience.

- Project type
- Independent personal build
- Project focus
- Home-services website and request experience
- Presentation
- Two representative interface visuals
- Viewing mode
- Portfolio case study
A clear purpose.
A considered build.
The challenge
Customers need to understand what a service includes and what happens after an enquiry. Introducing a booking calendar too early can create expectations before the task, location and availability have been understood.
The approach
The experience moves from service categories to a considered request brief. This case study focuses on scope, information order and the handoff between browsing and asking for help, rather than claiming a live network of tradespeople.
Who the experience is for
A local home-services business use case. Names, availability examples and residential artwork in the portfolio are illustrative.
Real development experience. Independent projects.
I have built client websites and web applications as part of an agency team. Those deliveries are separate from the independently branded projects shown here; client code, screenshots and private data are not reused.
A closer look at the project.
Explore the next screen below, or open the gallery to browse all project previews.
Request planning
Illustrative interface · Sample content
The journey,
step by step.
The key experiences and information decisions covered by this case study.
Choose the right service
Service groups help a visitor distinguish common home-care needs before moving into task-specific questions.
Describe the work
The request presentation gives room for scope and preferences without treating a private address as the first piece of browsing information.
Review the request
A summary puts the task and next step in context. Sample slots in artwork do not represent a real service team's availability.
More than a
different colour palette.
Terracotta and cream create a warm residential identity. Original architectural artwork, consistent service cards and a compact request summary give the experience a practical shape. The design makes the chosen task and the expected next step visible together.
Scope before scheduling
A request starts with what needs doing, so scheduling is not used as a substitute for understanding the job.
Readable service choices
Consistent cards and clear category descriptions make different service options easier to compare.
No implied booking promise
The public showcase does not offer real booking slots, tradesperson ratings or binding estimates.
The work.
And its context.
This case study presents the project's purpose and interface decisions without requiring a public demo or account access.
These describe the work's subject and design priorities, not a list of unverified technologies or integrations.
- 01SCOPE & CONTEXT
Completed personal website/application project.
- 02SCOPE & CONTEXT
This is a case study, not an operating service marketplace.
- 03SCOPE & CONTEXT
No customer addresses, real availability or provider records are published.
- 04SCOPE & CONTEXT
Payments, dispatch and provider integrations are not asserted by the showcase.
About this project.
Personal implementation, representative visuals and live access are separate things. The case study makes that distinction explicit.
Is this project completed, and can I open the live site?
This is a completed personal project. The public page is a case study, not a live application demo. Live-site URLs, account logins and source-code links are intentionally not published.
How is the project credited?
This is an independent personal implementation by Ali Rehman, presented as a personal case study rather than a client engagement.
What do the project visuals show?
Representative interface artwork with illustrative content, retained from the design process. These visuals are not screenshots of the finished application or evidence of production results.
Can we discuss a similar project?
Yes. Use the contact page to describe your requirements. Any new work would have its own scope and original implementation; client code, confidential data and proprietary assets are not shared.
Planning something similar?
Explore the relevant service scope and a practical planning guide before describing your requirements.
Have a project in mind?
Let's discuss an original build around your requirements—not reuse an employer's work.
All previews stay inside this portfolio.

