Learning Mobile Development
Checklist Before Adding A Library To Your App
Libraries don’t come for free. They can be costly in the long term.
Recently, on the iOS front, Apple introduced a bombshell requirement, mandating app developers to integrate libraries with their Privacy Manifest. This posed a significant challenge, as some of the libraries the app relies on do not yet have any Privacy Manifest. This could potentially jeopardize the app’s ability to ship updates after May 1st!
Meanwhile, in the realm of Android development, while not yet implemented, significant changes are on the horizon. Android is contemplating the introduction of a new SDK framework dubbed SDK Runtime. This initiative aims to verify the safety of libraries before their integration into applications.
The Checklist
Therefore, in light of this consideration, it serves as a reminder that dependencies on libraries come with associated costs. Prior to adoption, thorough due diligence is imperative.
I initially shared my thoughts on Reddit regarding a potential checklist, and received relatively positive feedback. I will now expand upon it here for greater clarity.
