Well, first you need to decide what you should put in different places. ie: watchos2 requires a different way of thinking. What are you calculating? If the inputs for the calculations come directly from Apple Watch, then it is much better that the extension runs on Apple Watch itself. If the inputs do NOT come directly from Apple Watch, you may think about doing calculations in parent app in background (or even on a server) and using WatchConnectivity to send them to Apple Watch from the parent iOS app.For instance, we (at Mouseaddict) track where the user goes inside of Disneyland when they are visiting. This type of data can be displayed on Apple Watch in a glance or watch app. (it does not now, but it could). This would be perfect for running on the parent app because the datam we are crunching does not come directly from Apple Watch itself - it is lat/lon and the phone provides that because Apple Watch doesn't have a GPS. Hence this should be crunched