Skip to main content

anytype_flutter 0.0.2 copy "anytype_flutter: ^0.0.2" to clipboard
anytype_flutter: ^0.0.2 copied to clipboard

Flutter integration for the anytype SDK. Builds the manytype_quic_ffi QUIC bridge from source with cargokit, bundles it with the app, and re-exports the anytype API.

anytype_flutter #

Flutter integration for the anytype SDK. Adding this package builds manytype_quic_ffi, the Rust QUIC bridge that anytype synchronizes through, from source with cargokit and bundles it with your app. It re-exports the whole anytype API, so apps import only this package.

This is an independent implementation and is not made or endorsed by Anytype or the Any Association. Version 0.0.2 is an early release.

Getting started #

dependencies:
  anytype_flutter: ^0.0.2
import 'package:anytype_flutter/anytype_flutter.dart';

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  AnytypeFlutter.ensureInitialized(); // loads the bridge and checks its ABI
  runApp(const MyApp());
}

The plugin also depends on sqlite3_flutter_libs, which bundles the SQLite library that anytype's storage needs; Android has no usable system copy.

AnytypeFlutter.ensureInitialized() is optional; without it the bridge loads on the first network operation. Accounts, storage, objects and sync are the anytype API, documented in its README. Set ManytypeStorage.directory to an app-owned directory, and give AccountRegistry a RecoveryPhraseStore backed by the platform keychain if recovery phrases must not sit in plaintext files.

example/ shows the bridge ABI and creates notes in a local account.

Building #

Builds compile the bridge for each target with cargokit, so the build machine needs rustup. Cargokit runs rustup's stable toolchain, which must be Rust 1.88 or newer (rustup installs it if missing), adds the Rust targets it needs, and builds with cargo build --locked against the shipped Cargo.lock (rust/cargokit.yaml). No prebuilt bridge binaries are downloaded: this release has no precompiled-binary configuration. SQLite is another matter: sqlite3_flutter_libs fetches it at build time, as a prebuilt Android library from Maven Central, as source from sqlite.org on Linux and Windows, and as the CSQLite Swift package (or the sqlite3 pod when Swift Package Manager is off) on iOS and macOS. The example's committed Podfile.lock and Package.resolved files assume Flutter's Swift Package Manager support is enabled.

Platform How the bridge ships
Android libmanytype_quic_ffi.so per ABI in the APK
iOS, macOS static library force-loaded into anytype_flutter.framework
Linux libmanytype_quic_ffi.so in the bundle's lib/
Windows manytype_quic_ffi.dll beside the executable

On iOS and macOS the bridge is force-loaded into anytype_flutter.framework, so apps must build pods as dynamic frameworks, CocoaPods' default use_frameworks! in Flutter apps. With static linkage the bridge is not linked in and NativeBridge reports that it could not load the library.

The Rust sources ship in this package under rust/: the manytype_quic_ffi crate with manytype_proto, manytype_core and manytype_transport under rust/crates/, and a locked dependency graph. Dart programs outside Flutter can build the same sources with cargo, as the anytype README describes.

Supported targets #

Target Build Bridge loads Loopback sync
Linux x64 Tested from the published archive Tested: the running app maps the bundled library Tested with the bundled library
macOS arm64 Tested from the published archive Tested: the running app maps the framework and reports the ABI Tested with the same sources built as a dylib
iOS Tested (example app, unsigned device build and simulator) Tested in the iOS simulator Tested in the iOS simulator (example integration test)
Windows x64 Tested (example app, release, with sqlite3_flutter_libs) Tested: the SDK loads the bundled DLL Tested in a Dart process with a cargo-built DLL and server built on Windows
Android arm64-v8a, armeabi-v7a, x86_64 Tested (example debug APK) Tested on an x86_64 emulator Tested on an x86_64 emulator (example integration test)

The example's integration_test/loopback_test.dart runs the two-device sync on a device or simulator; pass a base64 network config in --dart-define=ANYTYPE_NETWORK_YML_B64=.... A device reaches the server at the address the coordinator advertises, so for an emulator the server must listen on an address the emulator can reach, not 127.0.0.1.

"Loopback sync" means synchronization between two SDK instances through the ManyType repository's manytype_server. It is not compatibility evidence against an official Any-Sync deployment or Anytype's hosted network.

License #

First-party code in this package is MIT licensed. rust/crates/manytype_proto contains code generated from Anytype-heart schemas under the Any Source Available License 1.0 and from Any-Sync schemas under the MIT License, and anytype depends on manytype_protocol and manytype_core, whose Anytype-heart types and object replay files carry the same ASAL terms. ASAL allows use only for Non-Commercial Use or for Commercial Use in Allowed Networks. The vendored cargokit/ keeps its own license. See LICENSE before distributing an app built on this package.

0
likes
140
points
779
downloads

Documentation

API reference

Publisher

verified publishermanymath.com

Weekly Downloads

Flutter integration for the anytype SDK. Builds the manytype_quic_ffi QUIC bridge from source with cargokit, bundles it with the app, and re-exports the anytype API.

Repository (GitHub)
View/report issues

Topics

#anytype #any-sync #sync #ffi

License

unknown (license)

Dependencies

anytype, flutter, sqlite3_flutter_libs

More

Packages that depend on anytype_flutter

Packages that implement anytype_flutter