One Set of Listings, Two Front Ends: Planning a Real Estate App with Flutter and the WordPress REST API

Real estate agencies often have a WordPress site filled with property listings. When they request an app, the common mistake is developing a separate backend with its own database, admin panel, and duplicate property data. This leads to discrepancies between the website and app prices. As a WordPress and Flutter developer in Famagusta, North Cyprus, I use the following approach when planning an app alongside such a site. The key is to make WordPress the single source of truth and have Flutter read from it.

1. Make listings accessible through the REST API. If properties are a custom post type, ensure it's available in the REST API. Register the required fields for the app, such as price, bedrooms, and area, to avoid leaking unnecessary data and keeping responses small.

2. Keep the Flutter side simple and testable. A clean separation between the app's layers makes future changes easier:

- Data layer: a repository that calls the REST API and translates JSON into a Property model.

- Domain layer: plain Dart entities and use cases (search, favorites, view requests).

- Presentation layer: a BLoC per screen (list, details, favorites).

3. Implement multilingual and right-to-left support from the beginning. International buyers expect listings in their language. With WPML, each translation is its own post, so the app can request the appropriate language. Flutter automatically adjusts the layout for Persian and Arabic when the locale changes, but it's crucial to test all screens in RTL mode to catch any potential bugs.

4. Prioritise features that buyers will actually use for the first version:

- Search with filters (area, type, bedrooms, price, sea view, pool)

- Map view with pins along the coast

- Property pages with a gallery, key facts, and floor plan

- Favorites and sharing a listing on WhatsApp

- One-tap viewing request and phone/WhatsApp buttons

- Alerts for new listings matching a saved search

- Video tours, side-by-side comparison, buyer accounts, and agent areas can be added later once people are using the app regularly.

5. Implement notifications without a separate database. Saved-search alerts can be handled by storing each saved search (filters plus the device token) in a small table or service and running a scheduled job that checks for matches and sends a push notification when a new property is published. The actual listings remain in WordPress.

6. Focus on performance on both sides. The app's speed is only as good as the API behind it. Cache REST responses on the server, serve only the required fields, and deliver images as WebP in appropriate sizes. On existing websites, implementing these optimizations can significantly improve the mobile PageSpeed score.