Skip to content

Data Management #296

Open
Open
@Harjot1Singh

Description

@Harjot1Singh

Motivation

Our database is several hundreds of MB currently, and this may grow in the future. It may contain data that the user is just not interested in consuming for the most part. We'd also like to keep our app size quite lean for initial download times, whilst balancing a reasonable first-launch experience. The user should ultimately be able to read Gurbani and other data regardless of their connectivity.

Goal

The questions that we have to answer are around:

  • How much data, if any, should we bundle with the app?
  • What is relevant data to the user and the "dimensions" of data?
  • How do we download relevant data to a user's phone?
  • Does the user's remaining storage factor into this at all?
  • Do we only want to download on Wi-Fi, factoring in the user's data plan/costs?
  • (How) does the data ever get removed?
  • Data updates & synchronisation
  • Can the user manage what data they'd like by themselves and see the breakdown?

Stories/Tasks

Metadata

Metadata

Assignees

No one assigned

    Labels

    ϟ Type EpicDescribing a big goal. A collection of issues. Should never end up in an iteration.

    Type

    No type

    Projects

    • Status

      In Refinement

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions