Native clients, designed from the contract out.
The client direction starts with documented service contracts, proposes a typed Dart SDK, and plans a native Flutter client without positioning Flutter Web as another Kumwe front end.
Define behaviour before wrapping endpoints.
Client work begins with authentication, site context, capabilities, errors, concurrency, idempotency, pagination and lifecycle behaviour written as stable contracts. Generated convenience must not hide security semantics.
A typed proposal, not a released dependency.
The Dart SDK repository records the intended package shape and client boundary. Applications should not treat that proposal as a stable published SDK until its status changes.
A planned native experience.
The Flutter client is planned for supported native targets after the service and Dart boundaries are proven. Flutter Web is deliberately excluded: Kumwe’s existing web surfaces remain the web delivery path.
Review the direction while it is still being shaped.
The client and SDK repositories make scope and maturity visible before implementation claims are made.