january as user request month suggestions #303
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#303
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, don't have a twitter account myself, so thought i could just paste some suggestions here :
1 tor
2 ui
3 functionality
4 bug fix
Thanks for the list, there are some good ideas in there! Answers to a few specific ones below:
Currently working on this (see attached)
This functionality is currently in nightly (prototype) and allows a fully custom torrc config.
This doesn't make sense given the way that file sharing is implemented. In future releases we will allow re-hosting of files and allow people in groups to share responsibility for distributing larger files (i.e. torrent-like) - as such there is no "download progress" - clients just fetch chunks from whoever advertises them.
We do plan to add a few UI updates to this e.g. for image sharing the image will display for the sender as in other messengers, for other files we may also display some indepth information regarding rehosts/chunks but it will not be a progress bar.
Any specific critques?
We do have a plan to implement auto-expiring / deletable messages as part of the new hybrid groups protocol work.
The UI already supports adding emojis. On devices without an emjoi keyboard they need to be copy and pasted in. In the future we may add a built in emoji keyboard.
No, everything Cwtch stores is encrypted with a key derived from the password associated with a profile. (Slight caveat when it comes to saved Global Settings which we are currently not able to encrypt as we do not allow for customized "master password")
Hi and thanks for the feedback !
Also wanted to thank you guys for developing such crucial software, so do keep up the good work…
I’ll try to reply to a few points you picked up :
Don’t quite get why. Why would the receiver to be the only one who receives visual feedback on the progress of the file being transferred ? The sender might be as interested to see how his transfer fares…
Well, don’t take it badly. I’m just comparing the ui to some other more established desktop messengers I’m familiar with, like element and signal. But upon your request, I’m ok with sharing the personal impressions of a simple (but probably picky) end-user. Just trying to be constructive here with an app I’d like to use on a daily basis (so I have to stare at it often…).
A I’ll start from the main window.
1 consistency in icons
there’s a mix of filled an outlined icons : onion and gear are filled, whereas padlock (and x) are outlined.
In Signal all is outlined, in element everything is filled.
2 background drop when hovering over icons
in cwtch, when doing so, you get a huge (round) background drop more than 3 times the size of the icon, eating into its neighbors. That’s not very sexy…
In both Signal and Element, the backdrop is constrained to the size of the icon, square with rounded corners in Signal), round in Element.
=> I’d actually prefer Element’s solution while dropping the background drop : a mere filling provides sufficient visual feedback making everything minimalistic and slick
B the unlock window
1 Both the text input field and unlock button have too much a rounded corners IMO, the latter being almost pill shaped.
2 Hovering over the eye lid icon triggers a background drop, which is mostly hidden by the text field itself.
3 The eye icons themselves aren’t that good looking, the outlines are thick and very different from the ‘standard’ icons in most IMs.
=> I’d use the ‘stock’ icons, with finer lines and drop the backdrop
4 bullets replacing password characters in text field are too small.
I’d make them bigger in order not to give them the looks of lilliputs compared to the size of the text field.
C profiles loaded window
1 same remark concerning fills and outlines for the pencil
D edit page
1 idem rounded corners
E chat window
cf. Initial post
1 conversation settings : icon filled/outlined
2 ugly send button : too big background. How about just keeping the paper plane ?
F color scheme
as it will be given a thought, no need to insist. The default reddish color scheme isn't very inviting for me, most messengers use blue or green theme, which i find nicer on the eyes
Thanks for this feedback, it is very useful!
We will definitely offer some kind of feedback, but a progress bar doesn't really capture what is going on in the backend - especially when applied to conversations with more than one member. We are stil working through some of the UI details.
My apoligies if it came off that way. I only meant that specific nitpicks are much more actionable than general statements.
Do you mean the (pink) splash? Or the tooltips?
I have fixed the size of the splash in my dev build which makes them the size of the icon - which is definitely much nicer.
For the tooltips there isn't much we can do.
Also agreed. I've trimmed these down in my dev build. I think there are still some work to do on the text fields.
Good observation. Turns out Flutter defaults to a very small unicode character that doesn't respect font scaling. Fixed this in my dev build. Should be in nightly next week.
Currently thinking about this. It is definitely something we've gone back-and-forth on. I've made it a little smaller in my dev build and I like it better. I'll chat with our designer about this.
Agreed.
Thanks again.
Thx for checking out my comments...
ok, just a live percentage + speeds of how the transfer is going should do the job.
just the splash.
Thx. Just comparing signal and element desktop again. I actually wonder whether the splash couldn't be dispensed with. In desktop Signal, on the bottom part of the chat window, the outlines of the icons (nice looking thin lines IMO) just change color (from grey to black) when being hovered over and/or selected. That looks really nice and gives it a refined and minimalistic look. In cwtch you might try out something similar with an extra, f.ex. to have grey/black icons as default (outlines) and have the outlines turn into the overall color scheme for the app you let the user choose from. That would add an extra visual consistency inside the app. Hope you like the idea... Adding link to short video clip showing how it goes in Signal :
https://streamable.com/jtjqg9
Did you guys consider f.ex. a sliced onion as the connection icon, which would be reminiscent of the TBB ?
sorry, didn't mean to close the ticket, dunno how to undo that...
and PS, the idea of being able to run a Tor middle node sounds great to me. I'd see it as a possible opt-in feature with some user customization such as the ability to set bandwith caps f.ex. ...
PS2 is there a way to permanently delete blocked users from the user interface ?
Don't find any settings ans clicking on the 'delete' icon next to the user in the chat window doesn't do anything...
I believe everything captured in this issue is captured in specific individual issues (or fixed). If not feel free to reopen new individual issues.