mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #392] Refine UI coloring #176
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#176
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @Rokt33r on GitHub (Mar 27, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/392
Originally assigned to: @Rokt33r on GitHub.
The current UI coloring is not useful at all. It is too difficult pick a proper color easily. Also lots of colors are using transparency. It makes much more difficult because I have to worry about the background color.
Also background color of Primary button is too bright. So I'm guessing some people probably have problem to read label of it.
Anyway, once we fix this properly, development speed should become much faster. If there are anyone interested about this, please help us. I really want to discuss about this with someone professional.
@MahmoudFahiem commented on GitHub (Apr 3, 2020):
I can help with ui. I am a web designer and developer, so I have a little experience with colors.
@Rokt33r commented on GitHub (Apr 5, 2020):
@MahmoudFahiem Awesome! Could you join our slack and ping me? I'll notify you when I start working on this.
@Rokt33r commented on GitHub (Apr 23, 2020):
It is partially fixed in v0.4.0 But I'll fix completely in v0.5.0