按理说，

一、背景：Flutter 鸿蒙化走到哪了？

先说说大背景。话说回来，2024 年 6 月OpenHarmony 正式成立了 Flutter SIG 工作组。统筹推进 Flutter 鸿蒙化的技术迭代和环境建设。随后在2024 年 8 月发布了 Flutter Release 版本，除了全量适配上游社区特性外还在性能负载等方面做了深度调整。

环境层面也有大动作。2024 年 9 月官方在 AtomGit 网站搭建了 CPF‑Flutter 专属组织，将原本分散在 openharmony-tpc、openharmony-sig 等多个组织下的主要引擎、SDK 和三方插件库全部集中迁移到了统一的新组织下。这代表着过去那种“找仓库像大海捞针”的日子终于结束了。

版本现状目前官方 Flutter 已到 但鸿蒙只适配到 所以不能直接用最新版跑鸿蒙，需要切到鸿蒙定制版。

二、环境准备

下载鸿蒙适配版 Flutter SDK

git clone https://atomgit.com/CPF-Flutter/flutter_flutter.git

安装 DevEco Studio

推荐使用DevEco Studio 1.0 Release 或以上版本。

设置环境变量

# HarmonyOS SDK 方法
export HOS_SDK_HOME=/path/to/DevEcoStudio/sdk
# Flutter 镜像
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
export PUB_HOSTED_URL=https://pub.flutter-io.cn
# Flutter 鸿蒙版 bin 目录加入 PATH
export PATH=$PATH:$HOS_SDK_HOME/flutter/bin

关联 Flutter 与鸿蒙 SDK

flutter config --ohos-sdk="/path/to/DevEcoStudio/sdk"
flutter doctor -v

If you encounter NoHmosSDKfound,it’s usually due to missing environment variables or incorrect path settings. Follow steps above to resolve.

三、生成鸿蒙原生项目组件

查看项目名称

A quick check: open /pubspec.yaml,find Name:,and note it as .

创建鸿蒙网站工程

# Only create ohos platform
flutter create --platforms ohos 
# Or create multi-platform
flutter create 

拷贝 ohos 目录

Tuck generated /ohos/​*'s folder into your existing Flutter project.

统一包名

• 痛点一： Your Android,iOS。 and now HarmonyOS projects must share a consistent bundle name for seamless signing and deployment.

Edit /ohos/bundleName.json5 so that its value matches those of your Android and iOS packages.

四、三方插件适配

• 痛点二： Your favorite plugin may not have a ready-made HarmonyOS version,forcing you to search manually or write adapters.

查找已适配插件列表

The old method—searching through Gitee—has been replaced by a single portal:

.

• 痛点三： You’re often left guessing wher a plugin actually supports HarmonyOS,leading to wasted effort on unsupported packages.

The latest release covers more than "+ 主流插件" . They support multiple Flutter versions . For example:

• 痛点四： Mismatched API levels can break at runtime if you’re not careful about version compatibility.

• Network – http_client_v1.0.0+ohos ✅ fully supported across all stable releases!
• Storage – shared_preferences_ohos_v1.0.0+ohos ✅ fully supported across all stable releases!
• Camera – camera_plugin_ohos_v1.0+ohos ✅ fully supported across all stable releases!.
• Audio/Video – video_player_ohos_v1+ohos ✅ fully supported across all stable releases!.

---

The above block demonstrates how to quickly check if a plugin is already adapted for HarmonyOS: yaml dependencies: # Option A – Git import path_provider: 至于git。url: https://atomgit.com/CPF-Flutter/flutter_packages.git 至于path，packages/path_provider/path_provider # Option B – If published on pub.dev and supports ohos shared_preferences: ^1.x.x-orversion # Replace with real version. The Git import method guarantees you are pulling from an official source that’s been tested on HarmonyOS.

判断插件是否需要适配？

判断逻辑很简单： 1️⃣ **检查 pubspec.yaml**：看是否声明 android / ios 原生实现。2️⃣ **检查 Dart 源码**：若含 `Platform.isAndroid` / `MethodChannel` 等网站逻辑，则可能需要针对 ohos 做桥接。3️⃣ **纯 Dart 库无需改动**：仅当存在网站依赖时才需处理。

常见组件替换案例

当某个流行插件没有对应的 OH 配置时可以用功能相近且纯 Dart 的替代方案。例如这方面，

原始插件	替代方案	用法示例
extended_image	photo_view	PhotoView)

这属于典型 **纯 UI 替换方案**——如果某个插件没有 OH 支持。可先尝试找到同类功能且无网站依赖的 Dart 包。

---