Skip to content
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

Change Input system with increase/decrease system #356

Open
8 tasks
PierreBresson opened this issue Mar 9, 2022 · 2 comments
Open
8 tasks

Change Input system with increase/decrease system #356

PierreBresson opened this issue Mar 9, 2022 · 2 comments
Labels
🆕 Feature New feature - approved by the team

Comments

@PierreBresson
Copy link
Member

PierreBresson commented Mar 9, 2022

Summary

Change the input system from a slider to increase/decrease input with buttons / input field

Proposed feature

Split Add Emission screen into two screens like so :
Screenshot 2022-10-28 at 18 26 53

Change Input system with increase/decrease input :
Incremental Input

  • if user click on + or - button, value should go +/- 1
  • if user press the value or the rectangle around, the keyboard should appear (with done button, I don't know if it's possible on iOS but should be possible on Android)

Min and max value should be the same as the slider, and if the user inputs values outside the limits, the value should be the closest min/max value.

Screens should look like as followed

  • for plane and streaming, duration should be showned :

Screenshot 2022-10-28 at 18 27 52

  • for electricity

Screenshot 2022-10-28 at 18 33 42

  • for items in the meal category

Screenshot 2022-10-28 at 19 05 14

  • for items in the food category

Screenshot 2022-10-28 at 19 05 38

  • for items in the purchase category

Screenshot 2022-10-28 at 18 38 58

  • for items in the custom category

Screenshot 2022-10-28 at 19 10 59

Entire design, see figma.

@PierreBresson PierreBresson added 🆕 Feature New feature - approved by the team 🚧 Pending Planned but not ready to be enterely coded yet labels Mar 9, 2022
@henriques4nti4go
Copy link

Can you give more details about this task?

@PierreBresson
Copy link
Member Author

@henriques4nti4go thanks for taking a look, I've updated the issue above with clearer instruction ☝️
Let me know if you need more clarification 🙂

@PierreBresson PierreBresson removed the 🚧 Pending Planned but not ready to be enterely coded yet label Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🆕 Feature New feature - approved by the team
Projects
None yet
Development

No branches or pull requests

2 participants