4rent

The experience centers on making listings feel scannable before they feel exhaustive. Large imagery, clear pricing emphasis, and concise property metadata help users sort promising options early instead of opening every listing just to discover the basics.

That product decision matters because rental search is usually a narrowing process. The interface should help the user reduce uncertainty, not prolong it with unnecessary friction.

4rent was built with SwiftUI using MVVM and Combine so the app could stay declarative while still handling asynchronous view updates and state changes cleanly. That stack kept the presentation layer readable and made it easier to iterate on screen composition without accumulating too much controller-heavy logic.

The architecture was especially useful for list-driven and detail-driven flows. Search state, selection state, and view updates could be coordinated without turning the product into a maze of tightly coupled screens.

The browsing layer focuses on images and rental essentials first, because those are the cues users use to decide whether a listing deserves attention. Detail views then expand into richer content with a more spacious layout, letting people evaluate a property without losing track of the basics that brought them there.

This creates a clearer two-step rhythm: discover quickly, evaluate carefully. The app feels more intentional because it does not try to solve both tasks with one overloaded screen.

Search tools matter more when they behave like commitment tools, not decoration. In 4rent, filters were treated as part of the core product logic because narrowing by budget, location, and preferences is central to whether the product feels useful.

That meant keeping the interaction model straightforward and predictable. Users should be able to tell what is being filtered, what changed, and how to revise the query without re-learning the interface every time.

4rent became a strong exercise in native mobile product design for a high-browse, high-comparison category. It demonstrates how a cleaner information hierarchy can make a familiar marketplace feel more decisive and easier to trust.

It also reflects a pattern I return to often in product work: reducing interface clutter so the user can judge options faster, not just scroll through more of them.