Conversation organization with tabs/folders
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 28/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- mobile, mobile-dev
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Kotlin
- Estrellas
- 1.6k
- Forks
- 187
- Merge medio
- 1 d 15 h
- PR fusionados (30 d)
- 20
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Messages
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
FossifyOrg/Messages#929 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
FossifyOrg/Messages#927 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 63/100
FossifyOrg/Messages#919 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Messages#897 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
FossifyOrg/Messages#761 ·
Los mantenedores suelen responder en 1 día
Todos los issues de FossifyOrg/Messages
Issues similares
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
-
documentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
jainam6610/calm-ui#11 ·
Los mantenedores suelen responder en 1 día
-
area:sdk bug good first issue priority:medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Kotlin-server-squad/vizcore#255 ·
Los mantenedores suelen responder en 1 día
-
Toast NotificationsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día