digidem / digidem/comapeo-core-react-native
Move peer discovery into core-react-native
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
Context
Milestone-doc nice-to-have: "Moving discovery into core-react-native".
Today peer discovery (mDNS / local-network) lives outside this module. Pulling it into core-react-native would let the FGS own the full discovery + sync lifecycle alongside the backend it already manages, rather than splitting it across the host app.
Scope (to refine)
- Inventory where discovery currently runs and what it depends on.
- Decide what moves into the native FGS layer vs. the Node backend.
- Handle Android local-network / nearby-devices permissions and the iOS local-network prompt.
Exploratory — needs a design pass before estimating.
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
Start by inventorying where peer discovery currently runs and what it depends on across the host app, native FGS layer, and Node backend. Then define what moves where, including Android local-network or nearby-device permissions and the iOS local-network prompt; done means the design is agreed and the scope is estimable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios, kotlin, node.js, react-native
- Domain
- mobile-dev, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100