watchOS1 to OS2 app transition/migration strategy

Hi everyone,


I have an existing watch OS1 app on the store and I'm trying to figure out the best path forward. My OS1 app uses deprecated architecture, such as MMWormhole (shared group container) and the openParentApplication:reply: method of the WKInterfaceController class. When adding the new watch OS 2 app, is it better to keep deprecated OS1 app (no more updates) or remove OS1 app?


I know you can maintain OS1 & OS2 side by side, per the Transition Guide:

  • Do you need to support earlier versions of Apple Watch?
  • You can deliver Watch apps for both watchOS 1 and watchOS 2 in the same iOS app bundle, but doing so means maintaining separate targets and executables for each. Because it runs on Apple Watch, a Watch app for watchOS 2 must be completely recompiled into a separate executable. And because of the architectural differences between the platforms, sharing code may be more effort and add more complexity than having two separate apps.


Pros of keeping OS1 app

More customer base reach (but Apple customers will most likely update their phone & watch soon after OS2 is available)

Cons of keeping OS1 app

  • May cause confusion in the app description (OS1 vs OS2 features)
  • Complex code base for two watch apps


Thank you for feedback

I had also the MMWormhole framework in my Watch OS 1 app and used a lot of data syncing between iPhone and watch. Start migrating to Watch OS 2 and you will get you answer automatically. I decided not to maintain the old API any longer. I think the Apple Watch users will switch directly to the new OS 2 as soon as this version will be released. MMWormhole was really an amazing framework and we could be thankful that this developer wrote the class for us. But I am happy that with the new WatchConnectivity framework we don't need it anymore and I could get rid of the one and only third party code in my app.

Thanks Arnfried


Your response helps a lot and I agree that the bidirectional communication with WatchConnectivity is amazing/essential for syncing state

watchOS1 to OS2 app transition/migration strategy
 
 
Q