Conversation organization with tabs/folders
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 28/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- mobile, mobile-dev
Direzione di ricerca
This is a product-level conversation-organization feature for Fossify Messages (Kotlin Android SMS/MMS app): ALL and UNREAD tabs, user-created folders, one custom folder per conversation while still showing in ALL, per-folder pins, and unread badges on folder names. Start by reading the existing conversation list UI and how unread/pinned state is stored, then agree a data model and navigation with maintainers before coding. Done means the described tabs/folders work without dropping the current ALL view; UI details are left to maintainers.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Add a conversation organization system using tabs/folders:
- ALL — the default tab showing all conversations.
- UNREAD — a built-in tab showing conversations with unread messages.
- Custom tabs/folders — users can create folders and organize conversations into them.
- Each conversation can belong to one custom folder while remaining visible in ALL.
- Each custom tab/folder can have its own pinned conversations.
- Custom tabs/folders should show an unread indicator on their name or icon when they contain unread conversations.
- Tags/Labels could optionally be considered for cases where additional cross-folder organization is needed.
Why do you want this feature?
As the number of conversations grows, it becomes difficult to quickly find and manage specific conversations. An UNREAD tab would make unread conversations easier to find, while custom folders/tabs would allow conversations to be organized into categories such as work, family, friends, and services.
Keeping ALL as the main tab would also preserve the current simple view while giving users more control over how they navigate their conversations.
Additional information
I see UNREAD and custom folders/tabs as parts of the same broader conversation-organization feature.
The exact UI/implementation can be decided by the maintainers. The main goal is to make conversations easier to organize and navigate without removing the existing ALL view.
An unread indicator on each custom tab/folder would make it possible to quickly see which categories need attention without opening each one.
- Lingua principale
- Kotlin
- Stelle
- 1.6k
- Fork
- 187
- Merge medio
- 1g 16h
- PR unite (30g)
- 20
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di FossifyOrg/Messages
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
FossifyOrg/Messages#929 ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
FossifyOrg/Messages#927 ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
FossifyOrg/Messages#919 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
FossifyOrg/Messages#897 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug needs triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
FossifyOrg/Messages#761 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di FossifyOrg/Messages
Issue simili
-
[Submission] 悠悠有品Apertasubmit-adaption submit-adaption-pre
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
BetterAndroid/android-notification-icon-project#763 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
scarif-labs/horus#61 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
damontecres/Wholphin#2093 ·
I maintainer di solito rispondono entro 1 giorno
-
cr:missing-repro cr:platform:android missing-repro platform:android
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
software-mansion/react-native-screens#4950 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
software-mansion/enriched-markdown#1033 ·
I maintainer di solito rispondono entro 2 giorni