Case study · 04
A unified city radar that turns place signals into decisions and editable outing plans.
The problem
Finding a place in Makkah or Jeddah requires more than a name and category. Users need practical context such as the place signal, atmosphere, opening hours, expected price range, location, and what to know before visiting. The decision becomes more fragmented when an outing includes multiple stops. Users must search for options, save them, compare their suitability, and manually arrange them around time, group size, and preferences. Traditional place lists expose information, but they do not connect discovery, evaluation, and planning into one continuous experience.
The idea
Pulse converts place discovery into a decision system built around live-feeling status signals, useful place context, comparison, saved collections, and multi-stop planning.
Ranked sections such as Top Signal and Moving Now surface places through status, distance, category, and why-now context instead of a static directory.
Place pages combine status signals, opening hours, price range, vibe, practical notes, menu context, gallery media, and comparable alternatives.
Users can save places into collections, compare options, and generate multi-stop plans under time, budget, city, and preference constraints.
Flutter, Riverpod, repositories, structured JSON, and SharedPreferences keep the frontend modular while supporting Arabic/English direction changes and persistent preferences.
Design decisions
Why?One signal language (status, movement, score) reads the same on the feed, the cards and the map.
Rather than organizing discovery around categories alone, Pulse assigns each place one of nine status families, a movement direction, a Pulse score, and an opening state. The same visual language is used across the home feed, viral view, cards, and map, allowing users to understand and compare places without relearning the interface on every screen.
Why?The questions that come before a visit are answered on one page.
The details experience was designed to answer the questions that come before a visit instead of presenting only a description and image. It combines a quick read, recommended move, value note, atmosphere, pricing, opening hours, menus, parking and seating information, galleries, and parent-child venue relationships. This reduces the need to switch between several sources before making a decision.
Why?Alternatives and actions sit under every place, so a choice keeps moving toward a plan.
Collections and planning are not treated as isolated tools. A place can become a plan anchor directly from its details page, while saved items or a specific collection can become the plan source. Users can compare two options before planning, then preserve preferred stops or replace unsuitable ones without losing the context of the original decision.
On mobile
How it's built
IntegrationsGoRouterArabic / EnglishFlutter Test
Outcome
Pulse delivers a connected functional journey across 66 structured place records for Makkah and Jeddah, supported by 544 local content images and organized data for opening hours, pricing, menus, and before-you-go details. Users can move from reading a place signal to reviewing its details, saving it into a collection, comparing it with another option, or using it as the foundation of an outing plan. The planning journey generates two to four stops based on the available time, group size, outing intent, and selected rules. Plans can use different sources, preserve locked stops, replace individual choices, and be copied or stored in local history. The project demonstrates the design and implementation of a multi-flow Flutter product with clear information architecture, connected state management, and complete Arabic and English interface support. Pulse is in active development, and the current version runs on local data and on-device persistence.
