Briar Desktop issueshttps://code.briarproject.org/briar/briar-desktop/-/issues2023-08-02T19:52:34Zhttps://code.briarproject.org/briar/briar-desktop/-/issues/460Investigate Compose best-practices for lists2023-08-02T19:52:34ZMikolai GütschowInvestigate Compose best-practices for listsShould we use or is it worth it using `mutableStateListOf` as currently done in, e.g., `ContactsViewModel`? How to combine two different such state lists as currently done in `ContactListViewModel`? Can we have a common way of expressing...Should we use or is it worth it using `mutableStateListOf` as currently done in, e.g., `ContactsViewModel`? How to combine two different such state lists as currently done in `ContactListViewModel`? Can we have a common way of expressing a "still loading" state?https://code.briarproject.org/briar/briar-desktop/-/issues/458Research on and decide for across-screen navigation libraries/pattern2023-08-25T13:33:35ZMikolai GütschowResearch on and decide for across-screen navigation libraries/patternE.g. needed for #453. Quoting @grote from there:
> I only know that there's hundreds of competing navigation libraries for compose, not sure we want add our own implementation to the mix. Many of those probably only work on Android.E.g. needed for #453. Quoting @grote from there:
> I only know that there's hundreds of competing navigation libraries for compose, not sure we want add our own implementation to the mix. Many of those probably only work on Android.Desktop 0.7.0https://code.briarproject.org/briar/briar-desktop/-/issues/342Briar Desktop Usability Audit2022-05-03T14:59:57ZElio Qoshielio@ura.designBriar Desktop Usability AuditWe worked with Kay from Blickwinkel Digital, an external UX expert group who tested Briar Desktop as part of their Usability Audit according to ISO 9241-110.They have been immensely helpful in identifying common usability issues on the B...We worked with Kay from Blickwinkel Digital, an external UX expert group who tested Briar Desktop as part of their Usability Audit according to ISO 9241-110.They have been immensely helpful in identifying common usability issues on the Briar Desktop app. As someone without prior experiences with Briar, their insights were refreshing and much needed after we ourselves have worked with Briar over 4 years. As part of this collaboration we produced a PDF presentation including over 17 UX issues identified by Blickwinkel (including commentary from our side for further context) as well additional 8 issues identified by our Lead UX Researcher, Renata according to the UX Heuristics framework by Nielsen Norman Group.
![image](/uploads/4e87ec2fe74911cb7fd63a8ae77d58fb/image.png)
In a similar manner to the accessibility audit, the usability audit includes an issue description, an annotated screenshot, a recommendation, the severity as well as the criteria/heuristics being violated in this case.
Majority of the review has been conducted on a Mac M1 (with apparently an older version of Briar Desktop), though most things apply on both versions.
Presentation:
https://docs.google.com/presentation/d/1tDmSPzW26luF3ySaGUwbNelhvkRwXAFJ/edit?usp=sharing&ouid=100104676494073512080&rtpof=true&sd=true
[Briar_Desktop_Usability_Audit.pdf](/uploads/78097e2dcba23fe82e2fd0384041ad14/Briar_Desktop_Usability_Audit.pdf)Desktop 1.0.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/237Use central place to show error dialogs by means of some ErrorManager2022-11-27T13:22:07ZMikolai GütschowUse central place to show error dialogs by means of some ErrorManagerThat would avoid having an additional state and two parameters per dialog we want to show.
I think @seb already had a working implementation for #81.That would avoid having an additional state and two parameters per dialog we want to show.
I think @seb already had a working implementation for #81.https://code.briarproject.org/briar/briar-desktop/-/issues/236Use native windows for dialogs2023-01-09T21:39:56ZMikolai GütschowUse native windows for dialogse.g. for the AddContactDialog and AboutDialog, which do not strictly require to be modal.e.g. for the AddContactDialog and AboutDialog, which do not strictly require to be modal.Desktop 1.0.0https://code.briarproject.org/briar/briar-desktop/-/issues/235Check if factoring out some scrollbar related logic makes sense2022-01-18T20:28:35ZMikolai GütschowCheck if factoring out some scrollbar related logic makes senseThe following discussion from !105 should be addressed:
- [ ] @ialokim started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/105#note_60777):
> Might be also good to have those scrollbar-related...The following discussion from !105 should be addressed:
- [ ] @ialokim started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/105#note_60777):
> Might be also good to have those scrollbar-related things as a reusable component in the future.https://code.briarproject.org/briar/briar-desktop/-/issues/49Basic Software Architecture2022-04-03T10:36:50ZMikolai GütschowBasic Software Architecture- decide on design pattern fitting to the UDF idea of Compose (interesting reads: https://proandroiddev.com/architecture-in-jetpack-compose-mvp-mvvm-mvi-17d8170a13fd, https://www.ericthecoder.com/2020/07/20/battle-of-the-android-architec...- decide on design pattern fitting to the UDF idea of Compose (interesting reads: https://proandroiddev.com/architecture-in-jetpack-compose-mvp-mvvm-mvi-17d8170a13fd, https://www.ericthecoder.com/2020/07/20/battle-of-the-android-architectures-mvp-vs-mvvm-vs-mvi/)
- decide on use of other third-party libraries to support design (e.g. Decompose, #25)
- restructure "root" function calls in `BriarService`
- (maybe) take later portability of parts of the code to Android/other platforms into accountMikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/25Investigate Decompose2022-04-03T10:36:53ZMikolai GütschowInvestigate Decomposehttps://arkivanov.github.io/Decompose/https://arkivanov.github.io/Decompose/