New answers tagged

0

I think you're going to have to think a lot about states. If the user can return, they'll need some sort of index page where they can see what they've completed so far and what is left to complete. Will they have to log back in to do that? Will they have created an account? Will there be notifications to prompt them to do either of those things? You might ...


1

Firstly I think either approach could work, but you maybe should think about things like how your are going to maintain and communicate the state of the system across days. For example, if I return on a set day to complete the final piece, do I get taken straight to my final step?, or do I review the previous data? I think if the previous steps are set in ...


0

It looks like you may be using Material Design, is that true? If that is the case, refer to this link, https://material.io/design/components/buttons.html#hierarchy-placement for a better understanding of primary, secondary and tertiary buttons. Look at the do's and don'ts section. You are on the right path. The primary button should correlate with the ...


Top 50 recent answers are included