Hi Scott, I already know about background limits and restriction in iOS. I know that are some possibilities (listed in your reference in response). The problem that i have to solve is launch and opening my app without user interaction in scenarios where my iPhone is not fully accessible from everyone at every moment without engage some technicians on demand. I have to make sure that on iphone boot my app is launched and ready to accept commands from remote source Only for clearance i read that in order to make this happen on jailbroken iphones you can add a .plist file in which you specify what is going to execute, when and how (with the options specifying whether or not the app should be launched on system boot) then this file is added to launchDaemons folder and then load into services that launchd can handle via launchcctl load command. Now I'm not working on jailbroken device and I don't want to, but my company gave me the requirement in which iPhone app should be launched on system boot ( neither automations works since you have to swipe up or unlock dev on iphone boot). Before telling to my team leader that this requirement is not achievable I wanna make sure that's really true. So my final question is: There's a way to achieve on UNJAILBROKEN iPhone something similar to what is done for jailbroken ones ? (any special entitlement or configuration payload via MDM supervising my iPhone?) Thanks for reading

Hi Eskimo, What if i create a widget extension of my app, creating one on home? The idea is using widget as a <> launcher. Let me explain better. We all know that some widgets on springboard home are always displayed (unless you delete it o delete its parent app); For example weather app widget uses location in order to display actual weather info about our current position. So if I build a widget for my app with app subset functions, where this subset is made up of a minimal features that allow me to communicate with it. In this way my app needs to be "awake" due my interactions via code? Let me clarify, how does the state of my widget affect the main app state? Thanks to everyone for response and support!