Overcoming CPU power differences between iPhone 5 Series and iPhone 4 series. iPhone Optimisation

Question

My initial view is quite heavy in terms of UI. I have the main view, a map, and a tableView all in the one view. It takes approximately 30% cpu power on the iPhone 5s to launch this screen (is this bad?) but on the iPhone 4 it takes nearly double that, 50% + cpu power. Im concerned that my app will get killed by the system.

I am drawing most of the views in storyboard, would it be better to programmatically create them rather than using interface builder?

Basically is 30%cpu power high on the iPhone 5s on launch?

It decreases significantly from then on. And how would I accommodate for this on the iPhone 4 series? I realise that the 4 series is likely to be taken off the market in the next few months (with the launch of the 6 Series being predicted and that most apps on the app store say something like "Optimised for iPhone 5."

If I have let anything out please do not hesitate to ask for more information. I hope I have posted this question in the right place also.

Answer 1

The percentage CPU being used is irrelevant, for most cases. Your app will be killed if it takes too long to start up, which is time spent loading the storyboard, but it's time that matters, not CPU load as such. Unless you're pegging at 100%, don't worry about it.

Test on the device - if it launches, you're fine.

Building views in code is not necessarily faster or lighter on the CPU than using storyboards.

Answer 2

It shouldn't crash. If its taking loads out of your CPU, pop up a loading screen, load offscreen, and delegate back to your main and continue onward. An app shouldn't crash loading storyboards.