Mark/kimi_agent_kin_app_sync
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases 2 Packages Wiki Activity Actions

[Capture] Android share-sheet receiver for one-tap logging #109

New issue
Closed
opened 2026-06-29 19:24:07 +00:00 by Mark · 4 comments
Mark commented 2026-06-29 19:24:07 +00:00
Owner
Copy link

Problem

Every Android share menu (URL, photo, contact card, text snippet) currently can't hand off to Kin. Logging "shared a link with X" requires a separate trip into the app.

Scope

  • Register a <intent-filter> on the Capacitor Android shell for ACTION_SEND (text/plain, image/*)
  • Receive shared text/URL in app via Capacitor App plugin's intent handler
  • Boot to a LogInteraction prepopulated with the shared content + suggested person based on contact/email match

Why this is its own issue

Spec'ing a share-sheet receiver is its own design surface (manifest changes, intent routing, conflicts with existing share targets). Worth scoping before code.

Out of scope

  • iOS share-sheet (separate issue if wanted)
  • Multi-image / multi-file share (single text/URL for v1)
## Problem Every Android share menu (URL, photo, contact card, text snippet) currently can't hand off to Kin. Logging "shared a link with X" requires a separate trip into the app. ## Scope - Register a `<intent-filter>` on the Capacitor Android shell for `ACTION_SEND` (`text/plain`, `image/*`) - Receive shared text/URL in app via Capacitor `App` plugin's intent handler - Boot to a `LogInteraction` prepopulated with the shared content + suggested person based on contact/email match ## Why this is its own issue Spec'ing a share-sheet receiver is its own design surface (manifest changes, intent routing, conflicts with existing share targets). Worth scoping before code. ## Out of scope - iOS share-sheet (separate issue if wanted) - Multi-image / multi-file share (single text/URL for v1)
Mark commented 2026-06-29 20:38:06 +00:00
Author
Owner
Copy link

Open design questions (for the design thread)

  1. Which mimeTypes does the share-sheet receiver accept? Proposed: text/plain, image/*, text/uri-list, application/* (only if a custom filter can disambiguate).
  2. Single share per intent, or batch? Proposed: single.
  3. Conflict with existing share targets — is Kin added to the chooser every time, or only when the user toggles? Proposed: chooser default; user can pin in Android share sheet.

These need an answer before kilo-gsd can dispatch. Listing inline so the design session can resolve them.

## Open design questions (for the design thread) 1. Which `mimeTypes` does the share-sheet receiver accept? Proposed: `text/plain`, `image/*`, `text/uri-list`, `application/*` (only if a custom filter can disambiguate). 2. Single share per intent, or batch? Proposed: single. 3. Conflict with existing share targets — is Kin added to the chooser every time, or only when the user toggles? Proposed: chooser default; user can pin in Android share sheet. These need an answer before kilo-gsd can dispatch. Listing inline so the design session can resolve them.
Mark commented 2026-07-02 07:10:53 +00:00
Author
Owner
Copy link

Decomposed 2026-07-02 into 4 sub-issues. Parent stays as architectural record; needs-decompose removed since sub-issues now exist.

Decomposed 2026-07-02 into 4 sub-issues. Parent stays as architectural record; needs-decompose removed since sub-issues now exist.
Mark commented 2026-07-02 16:16:10 +00:00
Author
Owner
Copy link

Auto-triage: needs decompose

Marked triage-approved + needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.

## Auto-triage: needs decompose Marked `triage-approved` + `needs-decompose`. decompose-executor will pick this up and break it into implementable sub-issues.
Mark commented 2026-07-03 14:45:37 +00:00
Author
Owner
Copy link

Share-sheet parent — decomposed into #125 (S1), #126 (S2), #127 (S3), #128 (S4). Closing parent; sub-issues tracked separately.

Share-sheet parent — decomposed into #125 (S1), #126 (S2), #127 (S3), #128 (S4). Closing parent; sub-issues tracked separately.
Mark closed this issue 2026-07-03 14:45:37 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.1.0
v1.0.0
Labels
Clear labels   
blocked:depends-p1

Depends on #139 (P1) landing first. Picker should not auto-dispatch.

  
blocked:gate-research

   
blocked:lint-failed

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:verify-failed

   
bug

   
data-loss

Data integrity or data loss risk

  
documentation

   
enhancement

   
feature-request

   
in-progress

   
needs-decompose

Issue needs decompose processing

  
needs-triage

   
pwa

Progressive Web App functionality

  
quickfix

   
security

Security vulnerability or hardening

  
security/high

High severity security issue

  
security/medium

Medium severity security issue

  
test

   
test-coverage

Test coverage review / gap report

  
triage-approved

Approved for automated fix pipeline

  
vault

Requires vault/LBB authentication (#26) — discretion-sensitive feature

No labels
blocked:depends-p1
blocked:gate-research
blocked:lint-failed
blocked:needs-decision
blocked:needs-human
blocked:verify-failed
bug
data-loss
documentation
enhancement
feature-request
in-progress
needs-decompose
needs-triage
pwa
quickfix
security
security/high
security/medium
test
test-coverage
triage-approved
vault
Milestone
Clear milestone
No items
No milestone
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.

Dependencies

No dependencies set.

Reference
Mark/kimi_agent_kin_app_sync#109
No description provided.