show when run

Does the WatchKit Extension have to run on the Watch? My app does a lot of heavy duty calculations -- I think the performance on the Watch would be terrible compared to running on the iPhone. It doesn't seem like 2.0 will have a 1.0 compatibility mode where 1.0 apps can run unmodified on 2.0 like they do now. Is that the case? Will every existing app have to be rewritten eventually to run on 2.0?

The phone software seems very solid so far, and I'm running it on an iPhone 5. A few tiny display glitches, no 3rd party apps with issues. As fast or faster.The watch software seems extremely slow and I've run into some pretty serious bugs already. Unlock keypad staying on screen overlayed on watch face. Pushing digital crown in doing nothing (stays on watch face). Can't get debuggin on watch to work. Notifications from Messages don't seem to come through (more testing needed).

I'm also curious about this. My Macbook Pro has a hardware problem with its FireWire port which prevents OS X from starting up if the FireWire drivers are present (it hangs indefinitely waiting for the FireWire port to respond.) The only way for me to run OS X on my laptop is to remove Apple's FireWire kernel extensions.

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 in the bkg on the parent iOS app and

You can still build a test your app on 2 and then submit using Xcode 6. I run beta iOS updates and then build production apps with the old Xcode - you don't need a device plugged in to do this. However you're risking missing bugs as your test OS doesn't match your build OS. As for switching between watchOS 1 and 2 - downgrades are not supported or reccomended.

You can perform an update from OS X Yosemite to OS X El Capitan without losing data. However it is a beta and there is a chance for data loss and corruption in an case so I advise making a backup of your system before installing the beta.I am slightly confused however as you mentioned it is a Yosemite beta. Yosemite is in public release so if you arent running that I can be sure what is going to happen. You shouldnt be running OS X Yosemite betas any longer with the exception of things like 10.10.4.

I agree.A beta is a beta. It is not a cause to slam apps that don't work under the beta. If this is NOT against the TOS then it should be! If you are running this on anything other than a dev iPhone it is a bad idea..If you ARE running it on a dev iPhone then there is absolutely NO reason for this list.Reporting this Apple to see if they will lock and/or remove this thread.

Same issue here on a 2010 mbp (hi-res).Running from the terminal, it spits out :Assertion failed: (ctx), function CIEAGLContextCreate, file /Library/Caches/com.apple.xbs/Sources/CoreImage/CoreImage-327.6/Framework/misc/CIEAGLContext.m, line 261. right before aborting trap 6.Photos runs fine on another (newer) machine.