-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Could show the price in the explore page, no need to enter the prod page #2765
Comments
➤ Kenny Hung commented: As discussed on slack ( https://dt42-numbers.slack.com/archives/C0323488MEJ/p1686637357593569?thread_ts=1686300199.895919&cid=C0323488MEJ ), this task should need to UI/UX suggestion first. I'll ask for Noir's suggestion. (cc Ethan WuTammy YangScott Yan) |
➤ Kenny Hung commented: See the expectation in this task. Basically we want to display product price on the explore page. |
➤ Kenny Hung commented: Tammy Yang ^ ^ How do you think? |
➤ Tammy Yang commented: Looks good to me! Mike Mellor I suggest to move the Capture badge to the right-hand side, how do you think? |
➤ Mike Mellor commented: This also works 🙂 I've moved it to the right so you can check. |
➤ Ethan Wu commented: Tammy YangMike Mellor capture app currently doesn't support Capture Titles. We only display username and the badge. As a result we cannot follow the 2-line design proposed in the Figma. What I've done is the following: {username} | {NUM Price} {Capture Verified Badge if available} all in a single line. See image attachement. Another design consideration to consider is the overflow that happens when the username is too long or when the NUM price is 6 digits long. What I've done is I truncated the username depending on the number of digits the price is however I am unsure if cutting off the username is something we want to do. Alternatively we can do the following 2 line layout: {username} {capture verified badge if available} {NUM Price} Please let me know which direction we want to go. Thanks! |
➤ Ethan Wu commented: This is what it currently looks like without the badge and with the badge |
➤ Ethan Wu commented: pending feedback, the above is what is implemented. |
➤ Ethan Wu commented: Mike Mellor done see attachment |
➤ Ethan Wu commented: Mike Mellor how about the situation where the username is long and the price is 100,000 NUM. in these situations there will be overflow. what are your suggestions in these situations. currently we truncate the username to make all the contents fit in one line however i am unsure if that is something users will want. |
➤ Mike Mellor commented: Truncating the username was my first thought too, I don't mind it, but let's get some other opinions? |
➤ Kenny Hung commented: Ethan Wu Current test on browser.
|
➤ Ethan Wu commented: ok i can make the adjustment |
➤ Ethan Wu commented: Kenny Hung done |
➤ Kenny Hung commented: Ethan Wu
|
➤ Ethan Wu commented: Kenny Hung thanks for the catch. i will adjust. basically we set some general rules. I will see if i can adjust so that it shows up better. also what screen size are you using to view? |
➤ Kenny Hung commented: Ethan Wu It looks good! My test device:
Summarize QA testing the information of maximum characters
QA pass. |
➤ Kenny Hung commented: Ethan Wu QA conditional pass. My test device:
Summarize QA testing the information of maximum characters
Currently QA found there is display issue on some specific devices.
|
➤ Ethan Wu commented: Mike Mellor i think the current design for the explorer page to show price is a bit awkward. many of the users have pretty long usernames as a result truncating will make it be like 4 characters .... with the badge and price. i think maybe a better design might be a two line approach. i've provided screenshots for reference. if you can provide your thoughts and maybe a new design for 2 line format that would be great! |
➤ Ethan Wu commented: Kenny Hung do i make the above adjustment? and than you can retest? |
➤ Kenny Hung commented: Ethan Wu Yes, please. |
➤ Ethan Wu commented: Kenny Hung ok i will work on this a bit later. i need to finish some slides for bofu first. |
➤ Ethan Wu commented: Kenny Hung done |
User story:
As a user, I want to see the price of each capture in the Discover section of the Capture app without having to click on each individual capture, so that I can quickly browse and find the specific capture.
Your email:
[email protected]
Is this a general issue/FR report or a ticket that involve your personal account?:
No personal information involved
Select product:
Capture App
One line to describe the issue you see or the feature you want to add:
In the Capture app, when we click on Discover, we cannot see the price without clicking on the capture. It would be great if the price appeared without opening the capture.
Let us know what do you expect to see?:
When I go to the capture app and when I click on the search icon I get to see different captures taken by the photographers it would be good if there would be an option for the cost currently if I want to see the cost of each capture I need to open each photograph which can be time consuming so it would be a good option if the price of the capture would be mention directly in the discover section it will be good to compare different captures
Please provide some simple steps to help us reproduce the issue or understand how do you want to see the feature.:
Open the capture app gold click on the search icon then when you go to the discover section you get the captures taken by various artist and photographers but in order to see the price which they haveli to click each photograph which can be very time consuming since there are lot of capsule so should be good if the captures the price is listed
What's the device or browser do you use?:
Iqoo 7
Provide some additional context that can help us clarify the issue or the feature you expect:
The feature which are expect is I should be able to see the price in the discover section
———————————————
This task was submitted through Issue Report/Feature Request
https://form.asana.com/?k=OlNjzNIasZt0uOT5gzb7pw&d=1200886955782960
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: