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

It is but not an "architecture" talk

It is but not an "architecture" talk

#105 December Meetup - BlrDroid + BlrKotlin
https://www.meetup.com/blrdroid/events/256468726/

Ragunath Jawahar

December 01, 2018
Tweet

More Decks by Ragunath Jawahar

Other Decks in Programming

Transcript

  1. TEAM SIZE • Lone wolf / she-wolf • 2 /

    3 member team • 4 / 5 member team • 5 - 10 member team • Greater than 10
  2. *Not drawn to scale Objects in front of you are

    closer than they appear Time Features Prototyping A/B Tests No architecture With architecture
  3. TWO INFAMOUS STATEMENTS (EXCUSES) 1. We don’t need an architecture.

    2. They don’t give us enough time for architecture.
  4. “ The goal of software architecture is to minimise the

    human resources required to build and maintain the required system. -Robert C. Martin
  5. IMPERATIVE FUNCTIONAL • MVC • MVP • MVVM • VIPER

    • MVI (One Way) • Redux *Not an exhaustive list
  6. IMPERATIVE FUNCTIONAL • Easy to learn • Mutability • Performance

    • Learning curve • Immutability • Predictability • Asynchrony *Not an exhaustive list
  7. MAKING & EVALUATING (ANDROID) ARCHITECTURES • Hello stranger • Counter

    • Login • BMI Calculator • Image chooser • Quiz with timer • Magnetometer
  8. SOME COMMON QUALITY ATTRIBUTES • Testability • Adoptability • Adaptability

    • Availability • Reliability • Performance • Scalability *Not an exhaustive list • Security • Manageability • Buildability • Reusability • Maintainability • Simplicity • Efficiency