Can I create a WatchKit app without a storyboard (entirely in code)?

My team is currently working on an iOS application in which we don’t use storyboards at all. We create the UI in code instead. So for consistency’s sake it would be great if we could create a Watch App target entirely in code.

However, both the “Getting started with WatchKit” video and WatchKit Framework Reference
mention that you need a storyboard for the Watch App target. Furthermore, in WKInterfaceObject.h the init method is marked as unavailable:

  • Invalid Apple Watch icon file names must match pattern “*<dimension>@<scale>x.png”
  • WatchKit apps must have a deployment target equal to iOS 8.2 (was 8.3)?
  • Playing sound in Apple Watchkit
  • Watchkit new session does not work
  • Selector not called on selecting menu item after force touch
  • WKInterfaceTable rendering issues. Both the scroll bar and last row are cut off
  • - (instancetype)init NS_UNAVAILABLE;
    

    So is it really impossible to create a Watch App without using storyboards? If so, what are the reasons behind this decision? I mean, we can create an iPhone / iPad app entirely in code, so why is it different for the Watch?

    Solutions Collect From Internet About “Can I create a WatchKit app without a storyboard (entirely in code)?”

    If you read the WatchKit programming guide you will see that you app is actually executing on the user’s iPhone and the app sends information to be displayed to the watch by WatchKit.

    As there is none of your code executing on the watch itself, you can’t perform programmatic layout – WatchKit uses a Storyboard to provide the layout and render the information provided by your app running on the iPhone.

    Apple has said that it will be possible to develop native Watch applications in the future, so it may be possible then.