Skip to content

Hierarchy to distinguish between should-know vs nice-to-know #3

@namclu

Description

@namclu

As a beginner to Android, it would be good if the user could look at the hierarchy and be able to identify what they should-know vs nice-to-know vs experimental-phase. This could be in the form of design or colour-coding.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthow to readRelative to understanding of the roadmap.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions