MAFO (Mobile App Development Forum) is a community platform for mobile app developers, offering discussions, tutorials, and resources on mobile app development topics. With a focus on iOS and Android app development, MAFO provides insights, tips, and best practices to help developers build high-quality mobile apps. Developers can learn about mobile app design, development frameworks, and platform-specific features, and engage with fellow developers to share knowledge and solve problems.

Martin Fowler

Architecture Decision Records (ADRs) are short documents that capture a single architectural decision, its context, rationale, alternatives considered, and consequences. They should be kept brief (one page), stored in the source repository in a lightweight markup format like Markdown, numbered sequentially, and never modified once accepted — instead superseded by a new ADR. Writing ADRs serves both as a historical record and as a tool to clarify thinking and surface disagreements within teams. Each ADR has a lifecycle status (proposed, accepted, superseded) and should include trade-offs, confidence levels, and triggers for re-evaluation. Martin Fowler traces the term to Michael Nygard's 2011 article and points to tools like adr-tools for managing them.

Architecture Decision Record

<p>Isnt this just documentation?</p>
<p>&amp; Dont get me wrong the idea of key decisions being documented sounds nice but you’ll have hundreds of pages for a medium sized project in a month…</p>
