DuruGlobal

A property product has to bring together listings, images, location and category context, investment information, and a path to contact. The public store description emphasizes country and city search, filters, listing detail pages, and investment-focused presentations.

The engineering context is commercial delivery: the product has to serve different roles, languages, media states, and notification paths without exposing private client infrastructure.

My recorded work covers Flutter application implementation and the product integrations around listings, media management, role-aware access, onboarding, notifications, and deep linking. The work is described as a contribution to a commercial product, not as ownership of the client business or every product decision.

The recorded stack combines Flutter with Supabase and PostgreSQL. RLS-backed authorization, moderation workflows, media uploads, and structured onboarding are the public-safe architecture themes. Firebase / APNs notification paths and TR/EN/DE/AR localization extend the product beyond a single-language screen set.

The design decision is to keep authorization and content state close to data access. That reduces the chance that a listing, media item, or workflow appears in the app without the access rules that should govern it.

The main challenges are best understood as boundaries between product data, access, and device behavior:

• RLS-backed authorization and role-aware workflows had to protect company and moderation boundaries without making the app unusable.
• Media uploads and listing content needed predictable states across creation, review, and presentation views.
• Localization had to reach the application and its content model across Turkish, English, German, and Arabic contexts.
• Notifications and deep links had to connect a user’s device action to the relevant product context instead of ending at a generic app launch.

The project record remains conservative: DuruGlobal is published while client work remains ongoing. Public store and website links provide evidence of availability, while private source access, customer metrics, and operational outcomes are not presented as public facts.

DuruGlobal reinforced a practical rule: localization, authorization, media, and notifications are not separate polish layers. They shape the product model early, so the interface can stay clear when the business workflow becomes more complex.