cuappdev / cuappdev/pear-android

Fragment for MainActivity?

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
Priority: Medium
Dominant language
Kotlin
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Since this activity is quite sparse we should just have it as a fragment pushed by the scheduling activity (or vice versa, I don't have all of the designs so I'm not sure which would make more sense)--creating activities takes a lot of resources so we should avoid having many of them.

For the sake of merging in all pending changes before the semester's end, feel free to make an issue for this and not change it now.

_Originally posted by @jmf373 in https://github.com/cuappdev/pear-android/pull/3_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.