cuappdev / cuappdev/pear-android

Fragment for MainActivity?

Aperta
#5 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Priority: Medium
Lingua principale
Kotlin
Stelle
1
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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_

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.