https://github.com/BohdanOrlov/architecture-checklist

Designing iOS architecture: The checklist
https://github.com/BohdanOrlov/architecture-checklist

Last synced: 3 months ago
JSON representation

Designing iOS architecture: The checklist

• Host: GitHub
• URL: https://github.com/BohdanOrlov/architecture-checklist
• Owner: BohdanOrlov
• Created: 2018-03-04T17:56:01.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-03-04T20:11:53.000Z (over 6 years ago)
• Last Synced: 2024-07-18T16:33:37.082Z (4 months ago)
• Size: 5.86 KB
• Stars: 186
• Watchers: 8
• Forks: 27
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# ☑️ Designing iOS architecture: Checklist

List of questions one should ask while designing an architecture.

The article explaining the motivation is [here](https://medium.com/@borlov/e984e4ebba4a).

#### 📈Is it scalable?

- [ ] Does it handle changing business requirements efficiently?

- [ ] Does it support gradual adoption in existing projects?

- [ ] Does it allow replacing third-party components easily?

- [ ] Does is encourage composition of small independent components?

- [ ] Does it allow adding UI to features later?

- [ ] Does it support breaking of retain cycles on integration rather than component level?

- [ ] Does it support people working simultaneously on different parts of a feature?

- [ ] Does it limit the use of event/notification systems to specific layers?

- [ ] Does it provide a strategy for cutting corners and tech debt?

    

#### 🚧Is it maintainable?

- [ ] Does it provide a tactic for fighting massive objects?

- [ ] Does it limit the number of dependencies for an object?

- [ ] Does it try to reduce the amount of boilerplate code?

- [ ] Does it minimize the number of different roles of components?

- [ ] Does it suggest project structure tolerant to changes?

- [ ] Does it feel right?

    

#### 🔱Is it prepared for navigation?

- [ ] Does it explain how to pass data between components?

- [ ] Does it allow describing and discovering app flow naturally?

- [ ] Does it avoid transient dependencies?

- [ ] Does it define how to store state?

- [ ] Does it minimize the amount of global state?

- [ ] Does it allow opening a stack of screens?

- [ ] Does it handle opening of a screen from a push notification?

    

#### 🌟Is it promoting quality?

- [ ] Does it maximize the amount of testable code?

- [ ] Does it encourages compile-time decisions over runtime decisions?

- [ ] Does it avoid force casting and unwrapping?

- [ ] Does it allow stubbing asynchronous code to run tests synchronously?

- [ ] Does it support testing of UI?

- [ ] Does it forgive mistakes?

## 🤝 How to contribute

 Feel free to make a pull request if something is missing!

## 📃 License

[![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/)