New App roadmap

structures due to
major changes in
backend
A Simple view to get it right
Major backend changes
We’ve received some words major changes on backend even in
changing communication protocols, so this brings us Blockers in our
roadmap, in this atmosphere, we have no API to start with and
backend team should provides us as their plan.

These are their words from meetings that we could act on:

1. Delivery of Contracts and Mocks ( Ord. 15th) (RISK 1)

2. Delivery of APIs ready for production (Kho. 15) (RISK 2)

Also we could count on helping Mehdi Khademloo as the Backend of app in mocking
APIs or to develop some features
Major backend changes
We also, know that using mock APIs would rattle in our road to
deliver product and lower delivery speed, (RISK 3) so we need to make a
little changes in our roadmap

P.s: As I experienced, even finalized APIs may have some back-and-forth

needed conflicts and changes.(RISK 4)

With considering all 4 mentioned risks, we should try to minimize

our backend dependency before Delivery of new backend APIs,
SO Plan A
We start our first month with:

➔ Remaining Works (OTP, Deeplink) 1W

➔ App infrastructure 2W

➔ Design system implementation 2W

Then resume the plan with new mock APIs

and use new protocols on our APIs, As
But we need plan B
If we take risks for at least 15 days in their
Delivery: (Risks 1 and 2) plan till Ord. 30th
will be:

➔ Remaining Works (OTP, Deeplink) 1W

➔ App infrastructure 2W

➔ Design system implementation 2W

➔ INBOX 2w

And meanwhile the most independent work

for 15 days will be Inbox that we could have
it for all of the organization with the help of
M.Khademloo with on new protocols and
contract.
So our monthly Work Plan: (Android)

Second Month (Ord 15 - Kho 15)

First Month (Far 15 - Ord 15)
Inbox
Remaining works of OTP and deeplinks
Home page/ Landing Page
Project Architecture
My trips page - Refund process
Design System implementation

Third Month (Kho 15 - Tir 15) Fourth Month (Tir 15 - Mor 15)
Profile page
Sign up / Login process Dom flight Available - Int Flight available

Search Pages For all businesses Train Available

Bus available Hotel available - Hotel page PDP

We will experience extension of the dead line ( appx. Till End of Mehr)

Fifth Month ( Mor 15 - Sha 15) Sixth Month (Sha 15 - Meh 15) Seventh part ( 15~30
- Common app elements
- Finalizing PDPs in application mehr)
- Calendar
- External Services (Push and ...) - Referral Plan in app
- Passenger selection package
- Handle build automation - Train price calendar
- Payment process
- Enhanced Analytics - Train info / Image
- Deep-links
- Sync system messages in Web and app - Bus seat selection flow
- Analytics
- Align all analytics funnel and events
- Unit test
- Price changed Alert to user.
- Online ticketing (web view)
- Multi Language

Also, new Release dates would be communicated separately

Please be advised, If we made to plan A, it
will be postponed to the fourth month and
the the rest of plan will execute 2 weeks
earlier till inbox implementation