Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Separation of Concerns/ App Layering *Abstract concept applicable to iOS/Android as well Our Focus Today

Slide 8

Slide 8 text

We can think of an app as composed of 3 primary layers a. Presentation layer b. Domain layer c. Data layer Achieving separation of concerns

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

a. On taking 5 trips on cab service within a week, you get Rs. 50 cashback b. List of past food orders is coming in an api, we want to show cancelled and completed orders in separate tabs c. We want to change the api content type of an endpoint from xml to json d. On purchase of above Rs. 2000, you get a Rs. 500 coupon Can you identify a use case belongs to which layer ??

Slide 11

Slide 11 text

A. UI is designed first but is developed last in code B. UI helps in coming up with data models C. Development typically starts with inner layers (domain, data). In today’s case, domain layer. Approach For Application Design

Slide 12

Slide 12 text

A. Fork Repo B. If you are not OK with the pace, let us know Hands On

Slide 13

Slide 13 text

Some Concepts We Touched 1. Separation of Concerns 2. Dependency Inversion 3. Abstracting external dependencies 4. Liskov Substitution Principle

Slide 14

Slide 14 text

Further Discussions For discussion on today’s topic, code or flutter, we have two channels a. Github issues b. Gitter ● Links for the same are in at the below link ● Repo/Presentation link are available at below link https://sayeedhussain.github.io/flutter.html

Slide 15

Slide 15 text

No content