emidab/lullalink
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

Implement child device: capture and transmit streams and telemetry #4

New issue
Open
opened 2026-09-02 15:25:34 +02:00 by emidab · 0 comments
emidab commented 2026-09-02 15:25:34 +02:00
Owner
Copy link

Summary

Implement the child-device (near the baby) responsibilities: capture and transmit streams, plus sensor telemetry, over the secured P2P connection.

What to do

  1. Child app shell screen (runs the child role)
  2. Audio capture (microphone) and transmission
  3. Video capture (camera) and transmission — each independently toggleable on the transmit side
  4. Sensor telemetry: gyroscope/accelerometer stream (movement)
  5. Graceful handling when streams are toggled off / connection drops

Acceptance criteria

  • Child can toggle audio on/off independently
  • Child can toggle video on/off independently
  • Child streams audio, video, and sensor telemetry per the architecture doc
  • Streams go over the mTLS-secured connection
  • UI reflects capture state; failures are surfaced
  • Tests use fake platform plugins (no camera/mic on CI)

Notes

  • Depends on networking architecture and mTLS/connection issues
  • Testing via the established strategy (fake plugins, golden/widget tests)
## Summary Implement the child-device (near the baby) responsibilities: capture and transmit streams, plus sensor telemetry, over the secured P2P connection. ## What to do 1. Child app shell screen (runs the child role) 2. Audio capture (microphone) and transmission 3. Video capture (camera) and transmission — each independently toggleable on the transmit side 4. Sensor telemetry: gyroscope/accelerometer stream (movement) 5. Graceful handling when streams are toggled off / connection drops ## Acceptance criteria - [ ] Child can toggle audio on/off independently - [ ] Child can toggle video on/off independently - [ ] Child streams audio, video, and sensor telemetry per the architecture doc - [ ] Streams go over the mTLS-secured connection - [ ] UI reflects capture state; failures are surfaced - [ ] Tests use fake platform plugins (no camera/mic on CI) ## Notes - Depends on networking architecture and mTLS/connection issues - Testing via the established strategy (fake plugins, golden/widget tests)
emidab added this to the v0.1 — MVP: P2P baby monitor milestone 2026-09-02 15:28:02 +02:00
emidab added the
area: child
size: l
priority: high
 labels 2026-09-02 15:28:03 +02:00
emidab added a new dependency 2026-09-02 15:35:08 +02:00
#3 Design P2P networking architecture and domain model
emidab added a new dependency 2026-09-02 15:35:09 +02:00
#6 Implement mTLS-secured stream transport and connection lifecycle
emidab added a new dependency 2026-09-02 15:35:10 +02:00
#7 Implement QR-based pairing and mTLS trust establishment
emidab added a new dependency 2026-09-02 15:35:16 +02:00
#5 Implement parent device: receive and render streams
emidab added a new dependency 2026-09-02 15:35:40 +02:00
#10 Render live movement graph from child sensor telemetry
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
area: child

   
area: networking

   
area: parent

   
area: setup

   
area: testing

   
area: ui

   
priority: high

   
priority: low

   
priority: medium

   
size: l

21-34 points

  
size: m

8-13 points

  
size: s

3-5 points

  
size: xl

55-89 points

  
size: xs

1-2 points

No labels
area: child
area: networking
area: parent
area: setup
area: testing
area: ui
priority: high
priority: low
priority: medium
size: l
size: m
size: s
size: xl
size: xs
Milestone
Clear milestone
No items
No milestone
v0.1 — MVP: P2P baby monitor
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#5 Implement parent device: receive and render streams}
emidab/lullalink
#10 Render live movement graph from child sensor telemetry}
emidab/lullalink
Depends on
#3 Design P2P networking architecture and domain model
emidab/lullalink
#6 Implement mTLS-secured stream transport and connection lifecycle
emidab/lullalink
#7 Implement QR-based pairing and mTLS trust establishment
emidab/lullalink
Reference: emidab/lullalink#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?