Improve the request wizard
As mentioned by @baltpeter in !23 (comment 2006):
The wizard (well, my understanding of what it should look like, anyway) is now mostly done. Some things still left to discuss and implement:
-
I have some ideas about restructuring the start page and the "default flow" of users but would like to discuss that with you first, ideally via phone rather than text. There's also quite a few areas where I don't know how to implement them cleanly design-wise. -
As mentioned in #42 (closed), the consent mechanism for the search bar now needs to be moved out of the generator tutorial and into the wizard (or maybe even be present in both places, depending on where the user goes first). This also heavily depends on the first point.
I am kind of starting to regret choosing Algolia but I don't really see a good alternative, either. Our own Elasticsearch instance would be nice but is very costly. Maybe that would be a good thing to raise money for… -
I am thinking that maybe saving the companies selected in the wizard in the user's browser (probably local storage, although cookies would work, too I guess) might be a good idea. For one, the list generated will tend to be quite long and we might run into GET
query string limitations (in addition to long ones not exactly being good practice anyway). Also, having the list persist across browser reloads and the like is very useful as well obviously.
That would have to be configurable in the privacy controls, though so the challenge is to design a proper UI for that. -
Oh yeah, and my explanation texts are horrible. I am just not good at writing stuff like that. -> Apparently, we are leaving them… *shrug*
Edited by Benjamin Altpeter