Start with their choice to use Unity. It's a nightmare for its memory consumption and wasted CPU cycles. It is utterly unsuitable for an app that is concerned w

Start with their choice to use Unity. It's a nightmare for its memory consumption and wasted CPU cycles. It is utterly unsuitable for an app that is concerned with battery life. I say this as an individual who has made something of a career out of fixing/polishing mobile Unity apps from utterly unshippable garbage to decent products. More than a few have called for significant native code accessed via the FFI, because Unity just can't cut it. I would recommend not using Unity at all, but that would mean losing out on the cheap labour pouring out of the dime-a-dozen game development schools.