feat: introduce wizard

[sansan88]

New wizard

other ticket: https://github.com/project-owlly/cloud/issues/63

New Pages (david):

• /start (place signature button)

• /return (most of the changes are already done by @sansan88 ) you can add the owllyId=state. this.navCtrl.navigateForward('/next', { state: { userData: userData, pdfData: pdfData, owllyId: owllyId }

• /next: get data from storage, (session key is owllyid + sub = userid.) and display name. click on next navigates to /finish shall we use a navigation param? or do we pass data with the routing?

• /finish (add qr code for document import to the page if desktop and use button, if on mobile). example code for native this.helper.openBrowser("eidplus://did:eidplus:undefined/document?source=" + encodeURIComponent(JSON.parse(pdf).url)); on mobile use deckgo-qrcode to display a qr code for document import. it's the dataurl of the document.

Design and content from figma (tbd) https://www.figma.com/file/JytQQfL4c12pJanZHzisp0/Prototyp_2_wecollect_wizard

[sansan88]

First Step:

[sansan88]

Next Steps: create pages:

• /retun (exists) -> get user data + generate pdf, if done naviate to /next. during loading data, show spinner.
• /next (display user data, eg. name). navigate to finish
• /finish -> Button for opening eID+ and import pdf if on mobile. show QR Code if on desktop.

[peterpeterparker]

Mockups: https://www.figma.com/proto/JytQQfL4c12pJanZHzisp0/Prototyp_2_wecollect_wizard?node-id=328%3A0&scaling=scale-down

[sansan88]

the /return route is used for the EID+ Callback. So we need the /return for data exchange and login via eID+.

[sansan88]

The /return and the /next page could be the same. The loader is is displayed as long the pdf data or login is in progress..

[sansan88]

@peterpeterparker check the latest update here: https://drive.google.com/file/d/1tKbRPCRr9BplawgbG9LIRSjONYNDkN7Q/view?usp=sharing we can go through tomorrow

[sansan88]

wie besprochen mit scully & Tailwind umstellen..