Skip to content

Curated Flutter/Dart engineering Q&A for study, interviews, reference, architecture, internals, patterns, state, security, and situation-based scenarios.

Notifications You must be signed in to change notification settings

axah710/flutter-engineering-questions

Repository files navigation

📚 Flutter Engineering Questions

Curated Q&A for Flutter/Dart engineering — study, interviews, and reference.


💡 Why this repo?

📖 Study Deep-dive into architecture, internals, and best practices
💼 Interviews Prepare for Flutter / mobile engineering roles
🔖 Reference Quick lookup for patterns, lifecycle, and tooling

Each topic is in its own file per folder. Open a folder’s README for the full list and links.


📂 Topics

🛠️ 01 · Engineering practices

→ Open

MVP to long-term growth · quick hacks for demos · reactive principles · one-file app → engineering · rushed features · Flutter vs native · WebAssembly


⚙️ 02 · Flutter internals

→ Open

Core principles · lifecycle · reactive/declarative UI · “everything is a widget” · rendering · constraints · keys · platform channel


🔗 03 · Native interop

→ Open

Platform channel · Dart FFI · FFIgen · JNIgen


🧩 04 · OOP & design patterns

→ Open

OOP · SOLID · creational / structural / behavioral patterns


🏗️ 05 · Architecture

→ Open

Architectural decisions · Clean Architecture · feature modules · state management · event-driven · microkernel


⚡ 06 · Concurrency, offline, state & DI

→ Open

Concurrency · isolates · offline strategy · state scope · dependency injection


📋 07 · Rules, CI/CD, testing & envs

→ Open

Coding rules · CI/CD · documentation · testing strategy · flavors & environments


🔒 08 · Security & performance

→ Open

Security · crypto · privacy · accessibility · performance · rendering · memory · app size


📄 Format inside each topic file

  • Q: — full question
  • Key answers: — short bullet list

🎯 Situation-based interview style

  • Q&A use concrete situations (e.g. “List screen is laggy with real data”, “Stakeholder wants a quick demo hack”) and ask how you’d handle them.
  • Why: Shows real solution knowledge (not just theory), reasoning and trade-offs, and how you’d behave on a real team.

About

Curated Flutter/Dart engineering Q&A for study, interviews, reference, architecture, internals, patterns, state, security, and situation-based scenarios.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published