Engineering case study · Frontend
HostFlow
A property-management landing site with composed responsive sections, interactive pricing and a contact flow.
- Next.js 14
- React
- TypeScript
- Tailwind CSS
- Formspree

The problem
A property-management service needs clear information, pricing and contact actions that remain usable on small screens.
The implementation
A Figma-led Next.js landing page brings navigation, pricing, reviews, FAQs and contact into a reusable section-based frontend.
System structure
Architecture in practice.
The App Router page composes independent marketing section components.
Interactive frontend state drives pricing, FAQs, review navigation and calendar controls.
The contact component submits FormData directly to Formspree with loading, error and success states.
Engineering decisions
- Keep the page section-based so individual layout and interaction changes remain contained.
- Use local state for presentation-only interactions.
- Integrate an existing form service for the landing-page scope.
Challenges & tradeoffs
- Translate the provided visual design into a responsive layout while preserving hierarchy.
- Make interactive pricing and contact states clear without introducing a custom backend.
What the project teaches
- Component composition gives a marketing page a maintainable structure.
- Responsive typography and interaction states matter even when a project has no backend.
Current scope & limits
- The public repository implements a landing site, not a property-management dashboard.
- JWT authentication, MongoDB, REST data models and TanStack Query are not present in the inspected source.
- The live page contains placeholder marketing content; no business outcomes or production customer usage are claimed.
Contribution & source evidence
Independent frontend hiring exercise submitted by Zahid Hasan. Source and documentation contributions are recorded in the repository history.
- Page composition (opens in a new tab)
- Interactive pricing (opens in a new tab)
- Contact handling (opens in a new tab)
- Project scope (opens in a new tab)
The case study reflects inspected source. External project test suites and business outcomes were not independently evaluated.
Let's talk about practical engineering.
Contact Zahid