Multiuser support: collaborative field layout
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- ios, swift
- Domain
- distributed-systems, mobile
Research direction
Start with the MVP described in issue #1 and map how a field placement and cone progress could be shared across devices. Compare the listed lightweight backend, CloudKit sharing, and MultipeerConnectivity options, then define the session join flow and cone assignment rules. Done means multiple participants can join one field, see identical placement, and observe shared progress.
Written by the indexing model from the issue text.
Description
Follow-up to the MVP (#1), which is single-user.
Feature
Let two or more people lay out the same field simultaneously:
- One user places the field; others join the session and see the identical placement.
- Each participant is guided to a different cone (claim/assign cones), with live progress shared across devices (cone placed / in progress / remaining).
- Roughly halves (or better) the time to set up a field.
Notes
- Candidate transports: shared session via a lightweight backend, CloudKit sharing, or peer-to-peer (MultipeerConnectivity) for offline fields.
- A field placement is tiny (anchor coordinate + rotation + spec id), so sync payloads are trivial; the interesting part is session join UX (QR code / share link) and cone assignment.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from jaraco/Perfect-Fields
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
jaraco/Perfect-Fields#5 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
jaraco/Perfect-Fields#3 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
jaraco/Perfect-Fields#2 ·
All issues in jaraco/Perfect-Fields
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hoiekim/turnip-ios#321 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OneBusAway/onebusaway-ios#1749 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Crash when searching subtitles with the assrt provider (force unwrap of nil in AssrtSubtitle.swift)Openbug: crash feature: subtitle
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day