Changing av PoC App existing code is in Swift. Need some design changes and minor

Unnamed Air Mobile Application Proposal Our proposal is based on the following statement: Most airline mobile apps today are centered around the PNR which traditionally has been THE container for a booked trip. It contains all the details around a specific trip and over the years travel agencies and airlines has used this as the main storage for trip data whether it is information about transfer or special meals. Because it is PNR centric it sometimes does not make sense to a traveler, so in our proposal, we have flipped everything around and thought about what makes most sense to the traveler not depending and not the PNR We suggest the following main tabs Book - Native input dialogue and deep link to the mobile web booking engine - keep as is Me - Your profile page in the center of the application. All the information you need as a traveler will be there. If you have an upcoming flight this will be displayed as a card on the top. Your frequent traveler number and lates transactions etc. Ability to ‘Add booking’ if it is not displayed automatically. Check-in shall not be possible unless you have added a booking. If you add a booking on the web or in the app it shall be immediately available in both channels and this feature calls for a ‘Super PNR’ store where we keep track of one customer’s all orders and activities. This will also be used for data mining to provide each traveler with the most relevant information at the most relevant time (In Tune. On Time). If top tier level a contact button will be visible with you dedicated top tier service number More - Everything that is not related to booking or to your personal data will be listed here with a one to one relationship e.g 1 function can only be accessed in one way. Examples: Flight Status Contact us Airport information [Illustration] Book Me More It is also our suggestion that the app should require either a mobile number or an email address when opening it the first time and a one time password will be sent either as an SMS or an email. Same procedure on the web. The first time you sign in you will have the choice of creating a new frequent account OR associate with an existing frequent account Developer notes We have already developed a PoC for another customer in Swift and some of the functionality has already been developed, and the source code will be available to review before project start. The scope for this project is to alter it and update it to be suitable for a new customer. A subject matter expert will be available during the whole time for the project. The total time for this project is 5 days. First Screen when starting the app Sign up / Sign in (if time allows) E-mail or mobile number - one time password sent either via e-mail or SMS When Signed in Book - Native input then deep link when clicking “Search” as in EY PoC - Willes concept of banners in first step deep-linking into the mobile web (Special Offers) Me - Circle in the middle “My Sinbad” - Edit picture (in circle) - Sinbad number - Sinbad miles amount and expiry date - Next upcoming flight - Upgrade my flight (when available) - Check-in (when available) - Seating (when available) More Flight status - Native input then link to FlightStats via Goran’s API Feedback - Native form Contact US - Native menu as is but nicer design Flight Schedule - Deeplink Terms of use - native text page Share - Native share component Settings - Language, notification settings