Hydro Sdk Save

Author Flutter experiences in Typescript. No native bridge, no V8. Just Dart. From runtime to virtual machine.

Project README

Hydro-SDK

Logo

Author Flutter experiences in Typescript. No native bridge, no V8. Just Dart. From runtime to virtual machine.

Sponsored by

Possibly you! See sponsoring Hydro-SDK

Documentation and Tutorials

https://hydro-sdk.io/

Features

Hot Reload, Incremental Compilation

Action Gif

Function Maps

Function maps screenshot

Roadmap

Hydro-SDK is a software development kit (SDK) enabling Flutter developers to write portions of their app (or their entire app) using Typescript. It is a project with one large, ambitious goal. "Become React Native for Flutter". It aims to do that by:

  1. Decoupling the API surface of Flutter from the Dart programming language.
  2. Decoupling the development time experience of Flutter from the Dart programming language.
  3. Providing first-class support for over-the-air distribution of code.
  4. Providing an ecosystem of packages from pub.dev, automatically projected to supported languages and published to other package systems.

Hydro-SDK is currently only suitable for simple content. A few dozen Flutter widgets are supported. Content built with Hydro-SDK can be updated over the air using Hydro-SDK's built-in codepush. Content can be authored in a similar manner as in Dart with hot-reload and limited IDE debugging support.

Near Term

API Support

Continue expanding available Dart and Flutter APIs with automatic language projection (ALP) using Structured Wrapper and Interface generator for Dart (SWID). This effort is where the overwhelming amount of focus currently is. Having a stable and high quality ALP will allow for the re-use of existing packages from pub.dev in Typescript. This will also allow for expanding support for authoring Hydro-SDK content to other programming languages.

This work is tracked at a high-level in the Binding Generator project and in other sub-projects. This work is required to expand support for Flutter 2.8 (and 2.10) and is directly related to the following umbrella issues.

Medium Term

Developer Ergonomics

Improving developer ergonomics with more affective testing workflows and support for Typescript language features like async / await interop with Dart. This is being scoped and tracked at a high level in umbrella issues.

Performance

Establishing performance baselines through benchmarking. Some efforts to improve performance. This is being scoped and tracked at a high level in umbrella issues.

Long Term Projects

Developer Ergonomics

Lower the barrier to entry for developers with non-mobile backgrounds that are interested in trying out Flutter and Hydro-SDK.

Services

Registry

A closed-source component registry for first-class support for hosting and running over-the-air (OTA) update packages built using the open-source Hydro-SDK. This service is already live as a basic MVP.

Registry Value Adds

In the future, building paid features such as targeted distribution, analytics, feature flagging and logging directly into Registry are expected to be a viable path to monetization.

Language Support

Hydro-SDK is language agnostic. In the future, it should be possible to support authoring content in other programming languages to attract users from other ecosystems (Flixel, .NET, Xamarin).

Tier 1 (hot-reload, programmatic debugging, function maps)

Tier 2 (hot-reload, programmatic debugging)

Prior Art for Common Flutter Runtime

Prior Art for Structured Wrapper and Interface generator for Dart

Interesting Links and Resources

Open Source Agenda is not affiliated with "Hydro Sdk" Project. README Source: hydro-sdk/hydro-sdk
Stars
668
Open Issues
164
Last Commit
2 months ago
Repository
License
MIT

Open Source Agenda Badge

Open Source Agenda Rating