Apple Maps Guides

YES, you MUST support the 3.5 screen. The iPhone 4s is still amongst the supported devicesand will continue to be when iOS 9 ships this fall, Apple has said so very clearly. Also, unlessyou're writing a universal app, your iPhone app MUST run in 3.5 1x/2x compatibilty mode onthe iPad family.

You can now import simd to get access to the same functionality that C/C++/ObjC programs get via #include <simd/simd.h>The Swift syntax seems to be similar to the C++ syntax, except that some functions and initializers have named arguments:import simd let vec1 = float4(1.0, 2.0, 3.0, 4.0) let length1 = length(vec1) let vec2 = float4(1.0, 1.0, -1.0, -1.0) let dotProduct = dot(vec1, vec2) let elementwiseMultiplication = vec1*vec2 let matrix1 = float4x4([[0,1,1,1], [-1,2,0,3], [-3,0,-4,5],[-1,-1,2,2]]) let matrix2 = float4x4(diagonal:[1,2,3,4]) let matrix3 = matrix1 + matrix2 let matrix4 = matrix3.transposeI haven't found any Swift documentation yet (aside from option-clicking a symbol to get the popup description or command-clicking to get Xcode's pseudo-header thing), but through trial and error (and Xcode's autocompletion) it's pretty easy to figure out how the C++ version maps into Swift.Also, it looks like it's not done yet. while simd.vector and simd.matrix work fine, simd.logic doesn't seem

For me it give me some error about how this Apple ID can't use this service and that I should go make a new Apple ID. (Um, no. THIS is the Apple ID for which I pay my $99/year to access the developer program…)Anyway, it seems that the Log in link In the upper-left of forum pages is broken in some way. But if you've logged into any other part of the developer site (e.g., the Member Center link in the upper-right corner) then you can get into the Forum just fine. (Until your session cookie times out and it's time to log in again.)

Dont know what you mean by watch 3. There won't be a watchOS 3 until next year.watchOS2.0 will never work with iOS 8.xright now your choices are:- live with a bricked watch- continue to use iOS 9 and hope it gets less buggy soon. For me this is not really an option.- Hope that Apple releases some way to downgrade the watch back to OS 1.x

Apple needs to realize that this forum is very much a part of what we are paying for. A very simple CSS change to make this forum easily readable would be a good start.

I read somewhere that developers are now allowed to ship apps that require 64 bit hardware (I didn't see the WWDC video where this was announced, I read it on some blog so...it could be misinformation, though I have no reason to believe it is).In theory, Apple could release a 3.5 inch iPhone in the future with 64 bit support, so relying on that could cause problems in the future (and your app would also have to be universal...if it's iPhone-only it may still run on the iPad in compatibility mode...though I'd think by now they would change that to have the iPad scale up the iPhone 6 Plus layout instead.....I imagine that would look better than using the 3.5 inch).Handling the old 3.5 inch iPhone can be a pain for some designs...because it's smaller and the proportion isn't the same as the other iPhones so certain design things cannot be solved with math.

I've watched the Creating Complciations with WatchKit video and while I have a functioning 3rd-party complication I'm still unsure how and when the WatchKit extention is opened in the background to check if the data is stale. Apple doesn't seem to mention this in the videos and the documention seems to be pretty vauge on the topic only stating that the extention will be woken up. Anyone know if there is a delgate call or notificaiton that is triggered when ClockKit wakes up your extention?

There was a talk on What's New in Core Location yesterday that covered it:https://developer.apple.com/videos/wwdc/2015/?id=714Also, Apple have posted a sample project on how to do it with watchOS 2.0:https://developer.apple.com/library/prerelease/watchos/samplecode/PotLoc/Introduction/Intro.html#//apple_ref/doc/uid/TP40016176