Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am building a native iPhone application wherein this application will act as a standalone app on one device and act as a library on other device. Can you please guide me how should I design the app. Should the same method “applicationDidFinishedLaunching” be called in both the cases and just in the basis of some parameters I will be distinguishing from where the call was made. This is because, in both the cases, I have some different screen flows.
Library code has to be compiled into the running app to be used. No other app can access your code, as all apps are sandboxed and prohibited from accessing each other’s directories, and thus any code contained in such. If someone taps on another icon, it will be as if your library code does not exist to that app.
Another app can start your app by using a registered launch URL, but that will just result in your app being brought to the foreground. The other app will be put into the background or terminated.