It looks like they are falling into the trap of trying to have one app do both. They need to divide this into a desktop app, one that needs the horsepower for planning and reporting and a second that runs on mobile devices for data collection and light weight reports.
If they do that they can then expand into collecting preflight checks, flight logs, pilot time, etc.
There is functionality I want as a manager in the office that is not needed in the field. Example, assign flights to pilots. The pilot downloads flight detail. The pilot can plan and fly ad-hoc flights as well.
Perhaps these are functions of the enterprise license but they should carry down in the design. Perhaps Business license can have only one pilot, but there is still a division between desktop work and field work.
Fine line, I know and it will be different from business to business. Problem is the mobile devices have a horsepower limit.
Out flying this morning. Looks like some of the UI delays are directly related to device temp. The app pulls so much processing it is heating up the devices complicating the issue.
Off my soap box now.