vercel-labs / vercel-labs/native
Application-defined external effects
Nobody has claimed this yet.
- Dominant language
- Zig
- Stars
- 7.7k
- Forks
- 314
- Avg merge
- 5h
- Merged PRs (30d)
- 13
Description
Native apps need a bounded way to run app-owned work through the existing effect lifecycle.
For example, melearner should send a list_courses request to its Rust core and receive the result as a normal Msg, without adding melearner-specific APIs to Native SDK.
I propose fx.external: each request carries an adapter ID, operation kind, schema version, and byte payload. Native SDK owns request IDs, limits, exact cancellation, UI-thread delivery, and deterministic session record/replay.
Requests are capped at 64 KiB, results at 256 KiB, and external work shares the existing 16 effect slots.
Does this boundary fit the shared effects API?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reading the existing effect lifecycle and shared effects API, then trace how Native SDK delivers a normal Msg and handles cancellation and record/replay. Done means the proposed fx.external boundary, limits, and lifecycle behavior are agreed and documented well enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, zig
- Domain
- api, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100