Replies: 2 comments 1 reply
-
|
I probably won't implement this in Candybar myself because I now have my own UI and icon request pipeline but if anybody feels like taking this on, do it! Super worthwhile and one of the most useful features I've added in a while. After the release, I received 68 such mappings in 2 days and could approve every single one of it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Good idea indeed. I'm afraid we'll never see it in CandyBar though. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After implementing a new UI for my icon pack myself, I included an experiment. Instead of having one icon request interface, I split it up into two components:
My initial fear was that users could perhaps "abuse" the Report feature and submit insane mappings but turns out they don't. All missing links submitted so far are 100% matches to correct apps. I'm really pleased, because finding these in normal icon requests is difficult (as they might not get many votes) and now with over 4000 icons drawn for my pack, it's becoming increasingly harder for me to remember which icons I already drew.
Screenshots of my UI:
You can see that there are already suggestions in the Overview screen. I make these based on the package name of the app and let users submit those with a single ✓ click. Otherwise they can tap the pencil icon and pick one of the existing icons in my pack. The search bar reacts to both app labels and package names.
Here's a snapshot of the mappings submitted by my users this way. On the left the original icon. Right next to it the matching icon of my pack.
Beta Was this translation helpful? Give feedback.
All reactions