Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Frontend platforms @ realestate.com.au

Frontend platforms @ realestate.com.au

As our realestate.com.au audience has grown, so have the teams that build it. In this talk, I’ll present how we’re building and adopting micro frontends, design systems, and tooling together in our frontend platform products to build web and native experiences at scale. I’ll present the drivers behind our frontend platform strategy the lessons we’ve learnt along the way.

While microservices enabled REA to scale our technology and teams on the backend, our web and native apps have faced the scaling challenges of working in monoliths. Splitting out standalone experiences to solve this brought both technical and product divergence which led us to adopt an internal frontend platform strategy including design systems and micro frontends across React, iOS, and Android.

Stewart Gleadow

December 09, 2021
Tweet

More Decks by Stewart Gleadow

Other Decks in Technology

Transcript

  1. • 129m monthly visits1 • 12.6m monthly users2 • 650

    tech people • 60 squads • 75 initiatives (1) Nielsen Digital Media Ratings (Monthly Tagged), July-September 21, P2+, Digital (C/M), text, realestate.com.au vs Domain, Total Sessions. (2) Nielsen Digital Media Ratings (Monthly Tagged), July-September 21 (monthly averages), P2+, Digital (C/M), text, realestate.com.au, Unique Audience.
  2. 9 1. A mindset shift from local to company-wide tech

    thinking. 2. Approaching tech platforms as long-lived products.
  3. Number of Systems Year Aligned at small scale Aligned autonomy

    Unconstrained autonomy Shifted to an internal platform strategy 2000 2005 2010 2015 2020
  4. Different scaling journey for the front end Unique authors per

    system Pull requests per system Our main frontend systems for realestate.com.au
  5. Used for 56% of realestate.com.au experiences Powers 28% of realestate.com.au

    frontends Saved an estimated 213,000 hours of effort 30-40% less code required after migration 60% faster build and deploy cycle
  6. Integrated into all our mobile frontends Powers 5 separate micro

    frontends Helping drive visual consistency (and dark mode!) Fast feedback with fast local and CI build times
  7. Commit and merge, early and often Batch up changes Total

    build times in CI for Main App vs Micro Frontends
  8. Adopt: Continue to adopt and build out our frontend platform.

    Extend: Move towards building component-based experiences. Transform: Research Server Driven UI as a future direction. Where to from here…