Where are we at with iOS8?

While I’m working with Engineering on this, they suggest that since the keyboard is a fixed and known height in each OS, a simple check to see if your’re iOS 8 or not and adjust accordingly will work.

You need to know the OS, device and orientation to set the height:

iPhone Portrait:  216 points high (based on a 320 x 480 point content area)

iPhone Landscape: 162 points high (based on a 320 x 480 point content area)

iPad Portrait: 264 points in a 768 x 1024 point content area

iPad Landscape: 352 points in a 768 x 1024 point content are.

These are for iOS 7 and earlier.  iOS 8 will add some to this, but it’s a fixed amount.  I would start with an additional 44 points (the standard touch area) and go from there.

Rob

Good discussion. In addition to possible new default screen sizes and naming, we will probably see new icon sizes & names. 

Hi Rob,

Yes, I’ve done that at this moment. But you can drag this new ‘suggestionbar’ down. So you have a lot of ugly empty space. It’s not ideal. My application has chat functionality, so the input field is just above the keyboard.

Looks like Gold Master is available now!

A good article here: http://bgr.com/2014/09/09/ios-8-gm-download-link-iphone-ipad/

Here’s a topic for new iOS screen sizes and aspect ratios:

http://forums.coronalabs.com/topic/50951-new-iphone-6-6-plus-sizes-and-aspect-ratios/

To me, the bigger question is… where are we with the goodies being delivered with the IOS 8… Healthkit, Storekit, the new Apple Pay and access to thumbprint events… These are all critical in delivering near native experience in this very hot space!!! Anyone listening?

YES!!!

Our first, primary mission is to make sure the existing product runs on iOS 8 with no problems and to address any things that need to be done to keep our apps submittable.

Engineering is going to look at the various new technologies and see what is reasonable to do and what isn’t.  There is a lot to consider and a lot to research.  I can’t give you a time frame on any of this or speculate on what options.  In the mean time, our Enterprise subscribers will likely blaze a trail and move ahead with these technologies.

Rob

I take a backseat to nobody (or very few, at least) when trying to get Corona to fix bugs and improve the performance of components that should by now work across iOS and Android. Scrollview, webview, etc. are still not as useful as they should be at this late date: you can’t set the scroll speed for scrollview – this is different from friction – and webview doesn’t let you deny location requests.

That said, I think it’s unrealistic to try to get Corona to support iOS-specific stuff like Healthkit, Storekit, thumbprint, etc. If you want to access those APIs, start using Xcode and learn Swift. Or Xamarin if you like. Or Corona Enterprise. But until Android has similar features that show up on a lot of devices, Corona staff likely won’t (and probably shouldn’t) spend their time trying to match platform-specific features.

(If Microsoft were smart, they’d buy Corona Labs outright, let Walter buy a private island in the Caribbean and a jet to go with it, and try to make Corona the platform of choice for most mobile development. They could build out standard cross-platform libraries that implemented things like search boxes, which ksan is bravely trying to do right now, and create a nice GUI builder. Build a nice way to handle different device sizes gracefully, implement the best of Material Design and iOS 8, and offer lots of developer assistance. Then developers that switch to Corona would magically find their apps work – surprise! – on Windows Phone too. It might not actually work, but it’s better than their current strategy. Unfortunately Microsoft does not have a history of being smart about these things.)

I fully agree. A very strong argument. Thanks for reminding me of our sad reality! :slight_smile:

@corona273, you need a better username if you’re going to be dropping KNOWLEDGE.

I daren’t dream of a day when you can publish Windows apps across the board. Next stop is Steam, and you can take it from there. :wink:

Apple says “New apps and app updates submitted to the App Store should support iOS 8…”

Now, does this mean we need to build with iOS 8 or that the app should run on iOS 8 devices (even if it’s built on previous iOS). In the first case, our only option right now is to publish with the daily build whose stability is not guaranteed. Our app should be submitted by the end of the month. Any advice is appreciated.  

What about iOS 8 keyboards that have suggestions turned on? Are we able to know if the user has keyboard suggestions turned on or not?

Well, we also have custom keyboards now. So we really need to get the keyboard height from Corona.

see related post: http://forums.coronalabs.com/topic/51066-screenshots-and-new-iphone-size-compatibility/

Yes, new icons and launch images are needed when submitting for iPhone 6 and 6+.

see related post: http://forums.coronalabs.com/topic/51066-screenshots-and-new-iphone-size-compatibility/

Re: keyboard height

Moving discussion here: [http://forums.coronalabs.com/topic/50905-detect-keyboard-height/?p=271622]

HealthKit, HomeKit, and other new (and existing) iOS SDKs might be somewhat complex and specialized for Corona Labs to deal with right now, but Touch ID really looks like a game changer that might actually be simple to expose. Although it only works on one platform (iOS), users will start to expect the functionality on that platform very soon. 

I give a huge vote to an effort for Touch ID API access.

I know Engineering is looking at trying to figure out what we can and can’t do.  The first step is to get things working just for regular SDK users first.

Rob

Any news on when we will get a public build that supports ios8 and the new iPhone sizes ? Still holding on submitting apps after the problems two weeks ago and need to push them out soon