Have you ever been in a situation where you had some legacy iOS apps and Apple un-published them? There are scenarios like these happening lately to companies that are not updating their code line according to the latest requirements from Apple.
Isn’t this interesting folks? We nowadays got to call iOS code written around 2011 and 2012 “legacy code”!
If you have graphical-intense apps here are some things to keep an eye on:
- Older iPhone source code usually only has support for 3.5 inch screen sizesThe new code should support 4 “, 4.7″ and 5.5” screen sizes as well.
- Older iOS source code maybe deprecated since the project was built.Many times the code needs to be brushed up according to the latest calls, functions and procedures from Apple.
- The minimum deployment targets of older code are like 4.3.All current projects should set a minimum build target of 8.0
- Older code may not include auto layoutsAll current projects need to make the apps compatible with all the current screen sizes but also to keep in mind support for potential future screen sizes.
- Some of the third third party SDKs need to be updatesSDKs like Flurry have newer versions and they need to be updated.
- Suport for iPadOne overlooked aspect is that all the current code has to take into account iPad screen sizes as well.
- Apple recently introduced new must have configuration parametersThese new parameters have to be configured as well.
- Finally the newly updated apps need to be re-submitted to the itunes for Apple’s approval.
Also from a Project Management stand-point, when re-submitting iOS apps to the itunes please keep in mind Apple’s current QA review and approval times that are longer than Google’s. Apple has a stricter review process which can take up to a week.
Make it a great day!
Adrian @ Witty Web Solutions