google-research / google-research/CVD-paper-mobile-camera-example

[Code Health] Modular designing

Open
#65 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
44
Forks
9
PR merge metrics
No merged PRs in 30d

Description

This issue is to list down possible enhancements and things-to-think-about in the design of the sensing library.

1. uploadUrl, status columns in ResourceInfo: should they be in ResouceInfoEntity ?
2. separate capture and sync modules / library: common module to talk between the 2 modules (SensingEngine). Also move the zipping and UploadRequest creation to the sync module.

Contributor guide

Open the contributing guide

Research direction

Start by reading the sensing library around ResourceInfo, ResouceInfoEntity, and SensingEngine, then trace how capture, sync, zipping, and UploadRequest creation currently interact. Review whether uploadUrl and status belong in ResourceInfoEntity and document the proposed module boundaries and communication path. Done means the design decisions and required moves are clearly recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.