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

Why should you car about writing Reactive Mobil...

Why should you car about writing Reactive Mobile Apps?

Reactive programming allows you to write event-driven code. When we think about a mobile app, we can see a lot of interactions are driven by events. The user pushes a button, a background service fires an event due to updated data, the user types into a form and we show suggestions. So let's dive into this event-driven world and have a look at how to write reactive mobile apps using Rx.Net and friends.

Avatar for Mark Allibone

Mark Allibone

June 29, 2021
Tweet

More Decks by Mark Allibone

Other Decks in Programming

Transcript

  1. @mallibone Demo Recap • Observables are just event streams •

    Completion and Error handling • Fluent Syntax • Filter, map etc. like LINQ • Work with multiple event stream • Timer e.g. for polling
  2. @mallibone Recap • MVVM Properties and Commands • 🔎 Debounce,

    Filter and Map with Rx • Multithreading • Completion Handling • Error Handling • Readonly Properties
  3. @mallibone = Rx + MVVM + “a ton of helpers™

    Navigation DI Container View Lifecycle Event Extensions Dynamic Collections Validation User Confirmation Auto Persistance
  4. @mallibone Criteria for Mobile Apps • Don’t Crash • Responsive

    • Work Offline • 10’000 other points depending on preference etc. (like design and fluff) 😱
  5. @mallibone Option 2: Cache the Calls Servericon made by prettycons

    from www.flaticon.com Request / Response Cache Request / Response
  6. @mallibone Demo Recap • Task has one result • Observable

    can have n results • Akavache uses SQLite (multithreading enabled) • Seamless Offline experience
  7. Thank you for your time! Mark Allibone @mallibone Rey Technology

    https://mallibone.com https://nullpointers.io http://reactivex.io/ https://www.reactiveui.net/