How o-abdelaaziz/flutter-development-fedora-windows-11 works
This repository is not an application codebase; it is an end-to-end setup guide for a two-machine Flutter development environment. The “architecture” is the workflow it establishes: Fedora 43 as the development workstation inside VMware, and Windows 11 as the Android emulator host.
1. Purpose and scope
The repo documents how to build a Flutter toolchain on Fedora without Android Studio, then connect Flutter to an Android emulator running on a separate Windows 11 host. The key architectural concern is cross-OS device connectivity over the network.
2. Primary runtime boundaries
There are three distinct runtime zones:
• Fedora 43 guest VM: where Flutter CLI, Android CLI tools, and app development run.
• Windows 11 host: where the Android SDK command-line tools, emulator, and ADB server run.
• VMware networking layer: bridges or proxies traffic between Fedora and Windows.
3. Fedora-side toolchain subsystem
Fedora installs native build dependencies for Flutter Linux development, plus the Flutter SDK itself under ~/Development/flutter. This side is responsible for running flutter doctor, flutter devices, and eventually flutter run. It also hosts Android command-line tools under ~/Development/android.
4. Android SDK subsystem on Fedora
The guide manually installs Android command-line tools into a specific directory layout: ~/Development/android/cmdline-tools/latest. This matters because sdkmanager expects that structure. Fedora then uses sdkmanager to install platform-tools, platform APIs, and build-tools, making the local machine capable of Android CLI operations without Android Studio.
5. Environment configuration boundary
The repo standardizes access through shell environment variables and PATH updates in ~/.bashrc. ANDROID_HOME, Flutter bin paths, Android platform-tools, emulator tools, and browser-related variables are all set here. This is the central integration point that makes the CLI tools discoverable across the Fedora session.
6. Windows-side Android subsystem
Windows is treated as the emulator host, also set up without Android Studio. It has its own C:\Android\cmdline-tools\latest layout, its own ANDROID_HOME, and its own sdkmanager, avdmanager, and emulator binaries. It installs the Android emulator package and a system image, then creates an AVD such as MyEmulator.
7. Emulator execution model
The emulator does not run on Fedora; it runs on Windows. Fedora only connects to it as a remote Android device. This separation is the main architectural decision in the repo and drives the networking and firewall requirements.
8. VMware network path
The Fedora VM must be able to reach Windows directly. The guide prefers VMware bridged networking so Fedora gets an address on the same LAN subnet as Windows, enabling direct adb connect <windows-ip>:5555. NAT is treated as a fallback that requires port proxying.
9. ADB transport and device discovery
ADB is the control plane connecting Flutter on Fedora to the emulator on Windows. The Windows side enables TCP mode on port 5555, and Fedora uses adb connect to register the remote emulator. Once connected, flutter devices can see the emulator as a target.
10. Firewall and port exposure
Windows Firewall must allow inbound TCP traffic for ADB-related ports, especially 5555 and sometimes 5037. In NAT scenarios, the repo adds a Windows port proxy so Fedora can hit the Windows VM/NAT address and forward into the local emulator port.
11. Verification and health checks
The guide uses flutter doctor, adb devices, and flutter devices as the main validation checkpoints. These confirm that the Flutter SDK, Android SDK, licenses, network connectivity, and remote device visibility are all working together.
12. Troubleshooting as architectural evidence
The troubleshooting section reveals the brittle points in the design:
• SDK directory naming must be exact.
• ADB can get stuck offline if multiple servers or conflicting ports exist.
• VMware NAT can break DNS or device reachability.
• Linux emulator warnings may require extra compatibility libraries.
These are the likely failure boundaries in the system.
13. Overall data flow
The setup flow is: download toolchains from Flutter and Android distributions, install them locally on Fedora and Windows, configure environment variables, create an Android virtual device on Windows, expose it over the network, and then let Fedora Flutter tooling discover and deploy to that remote emulator.
14. Technology and infrastructure summary
Relevant technologies are Flutter CLI, Android SDK command-line tools, ADB, Android Emulator, Fedora 43, Windows 11, and VMware Workstation networking. The repo is fundamentally about orchestrating these components across OS boundaries rather than implementing application logic.
Main entry points: README.md README
Components 16
Guide
Repository scope and the end-to-end setup workflow it documents.
- README · The single source of instructions for the two-machine Flutter development environment.
README.md
Fedora 43 VM
Development workstation running Flutter and Android CLI tools.
- Flutter SDK · Flutter installed under the Fedora home directory for app development and device discovery.
- Build deps · Fedora-native libraries and packages required for Flutter Linux development.
- Android tools · Fedora-side Android command-line tools installed into the expected cmdline-tools layout.
- Shell config · ~/.bashrc exports that make Flutter, Android tools, and browsers discoverable in the Fedora session.
- Doctor checks · Flutter and ADB checks used to confirm the Fedora-side toolchain is healthy.
- Flutter run · The final execution path where Flutter discovers the remote emulator and deploys the app.
- Device list · flutter devices and adb devices output used to verify the emulator is visible as a target.
Windows 11 Host
Emulator host running Android SDK tools, AVDs, and ADB.
- Android SDK · Windows-side Android command-line tools installed outside Android Studio.
- Android Emulator · The emulator engine running on Windows 11 rather than inside Fedora.
- AVD image · A configured Android virtual device such as MyEmulator.
- ADB server · ADB endpoint on Windows used to expose and control the emulator over TCP.
Connectivity
VMware networking, ADB transport, and firewall exposure between the two machines.
- Firewall rules · Inbound allowances for ADB-related ports such as 5555 and 5037.
- VMware bridge · Preferred bridged network path that places Fedora and Windows on the same LAN subnet.
- Port proxy · Fallback NAT forwarding path used when direct bridged reachability is unavailable.
- ADB connect · TCP-based connection from Fedora to the remote Windows emulator on port 5555.
Connections 20
- README → Flutter SDK: documents · Explains installing and using Flutter on Fedora.
- README → Android tools: documents · Covers manual Android command-line tool installation on Fedora.
- README → Android SDK: documents · Covers Android SDK setup on Windows without Android Studio.
- README → VMware bridge: documents · Describes VMware networking as the bridge between machines.
- Build deps → Flutter SDK: supports · Native packages provide the Linux dependencies Flutter expects.
- Android tools → Shell config: exposed by · Android CLI paths are added to the Fedora shell environment.
- Flutter SDK → Doctor checks: validated by · flutter doctor and related checks confirm the SDK is functional.
- Android tools → Doctor checks: validated by · sdkmanager and adb usage are confirmed from the Fedora side.
- Shell config → Device list: enables · PATH and environment variables make device discovery commands work.
- Android SDK → Android Emulator: installs · Windows Android SDK tools provide the emulator binary and related packages.
- Android SDK → AVD image: creates · The SDK tools create the virtual device definition.
- ADB server → Android Emulator: controls · ADB manages the emulator runtime over a TCP transport.
- Firewall rules → ADB server: permits · Firewall rules allow inbound ADB traffic to reach the Windows host.
- VMware bridge → ADB connect: enables · Bridged networking gives Fedora a direct route to the Windows host.
- Port proxy → ADB connect: fallback path · Port proxying substitutes for direct bridged access in NAT setups.
- ADB connect → ADB server: reaches · Fedora connects to the Windows-side ADB endpoint over TCP.
- Android Emulator → Device list: appears in · Once connected, the remote emulator shows up as an Android device.
- Device list → Flutter run: feeds · Visible devices become valid deployment targets for Flutter.
- Flutter SDK → Flutter run: executes · Flutter on Fedora performs the final run and deployment step.
- AVD image → Android Emulator: boots into · The configured AVD is what the emulator launches.