Visitor Monitoring Are You Ready for iOS 8? | Keynote
Webcast

Are You Ready for iOS 8?

About the Webcast

iOS 8 is coming and it’s going to be a game changer!

Make sure you are prepared for the changes in iOS 8. This webcast is perfect for developers, testers and QA professionals who need to ensure the highest levels of continuous app quality and performance through the release of Apple’s latest mobile OS. iOS 8 bring new features to support and will require a renewed focus on ensuring that apps work together and ‘play nice’ within the new environment.

Keynote mobile testing and performance experts walk through the latest beta version of iOS 8 to help developers and QA teams understand how to ensure optimal performance with the new release, and how to:

  • Test the new Multitasking Interface in iOS 8 on multiple devices in the cloud
  • Support new features including Sharing Options, Photo Editing, and Interactive Notification Center
  • Test and interact with the new HealthKit and Health App
  • See the value and importance of testing and monitoring on iOS 8 on Day 1

Webcast Transcription

Josh:                  

Good morning and welcome to Keynote’s webcast, “iOS 8: Are You Ready?” My name is Josh Galde and I am the Senior Marketing Manager for Quality here at Keynote. Today our live demonstration will be led by two Keynote experts: Chris Karnacki, a Senior Solutions consultant who supports Keynote customers with their mobile testing requirements for iOS and Android, as well as Jason Shaw, an engineering manager and our resident iOS expert here at Keynote. Today’s webcast will help you understand the following: first, how to test the new multitasking interface or hand-off in iOS 8 on multiple devices in the cloud; second, how to test new features including sharing options, photo editing, and interactive notification center; third, how to test and interact with the new health app; and fourth, to see the value and importance of testing and monitoring on iOS 8 on day one.

Before we begin, let me review some housekeeping items. First, this webcast is being recorded and will be distributed via e-mail to you allowing you to share it or watch it again later. Second, your line is currently muted, so please touch star or zero for operator assistance if you experience any web or audio issues. Third, please feel free to submit any questions during the call. You can do this in the Q and A panel seen here in the bottom of your window. And fourth, as part of today’s webcast we invite you to join the conversation on Twitter. Join our community using #iOS8appquality. And comment live. Before we get to the live demo, we would like to cover four key areas of things to remember as it applies to iOS 8 specifically.

First, it’s important to know what’s coming—we’ll talk about and look at what’s going to be included in the iOS 8 release. Second, it is important to know your users’ experiences and we’ll talk about the importance of quality and how it applies to your consumers’ experience and what you can do to help insure this quality. Third, it is important to know that it will happen again—obviously, there will be future releases and we’ll talk about that as well. And fourth, how is Keynote getting ready? We’ll show you how Keynote is gearing up and getting ready for the much-anticipated OS release. We will then follow this with a live demo and Q&A.

First, let’s talk about what’s coming. If we can remember last year when iOS 7 was released it included over 1,500 new APIs. It included radically redesigned user interface and brand new enterprise features. And we all remember what a challenge that was. Apple’s new operating system for mobile phones, tablets, and even wearables is set to release very soon. By all accounts this far, we are facing yet another major hurdle. Let’s take a look at some of the major impacts we’re expecting with iOS 8. First, we have extensibility or app extensions. For as long as iOS and Android have been in existence, Android has had an advantage over iOS. It was called Android Intense and allowed Android apps to share data and functionality with each other and the OS.

More than 90 percent of Android apps and Google Play employ Intense. This has helped foster the idea that Android is a more open operating system. With iOS 8, Apple will change this with the launch of app extensions. Finally Apple is opening up iOS apps to allow for sharing of functionality, data, and access notifications. Apps extensions will be a bit more work for iOS developers but the impact of extensions can be far and wide on the app ecosystem and user experience. Second, this release will come with over 4,000 new APIs. As far as this new interaction Apple is also releasing thousands of its own developer kits for iOS 8, such as HealthKit and HomeKit, that will allow developers to integrate a suite of themed features and capabilities into their apps. The most ever for the company from Apple.

And third, this release includes an innovative new programming language called Swift. This language is support for Cocoa and Cocoa Text with concise yet expressive syntax. Writing Swift code within an excode six playground shows instant results while finished aps are compiled in to high performance native machine code. The Swift language is fast, modern, safe, and interactive. Security will also be a major focus of this release with expanded data protection to more apps, enabled finer control over mail encryption, and opening access of apps to use touch ID for log-in etc. The multiplying power of extensibility along with the thousands of new ATIs developed by Apple just for this release combine to make it a developer’s dream.

If iOS 7 adoption is any guide for what will happen with iOS 8, then we should definitely start to worry. IOS 7 recently hit 90 percent adoption as users prepared for the release of version 8. This high level of adoption is unique to Apple as Android continues to see fragmented adoption by its users. IOS 7’s adoption rate took many months to achieve, however. This graph shows the adoption rate within the first 24 hours. Compared with iOS 6, the last version release was adopted faster than any prior release.

What’s going to happen with iOS 8? So here’s a list of the major app extensions as part of the new extensibility framework. First there’s Share, which permits apps to show content. Photo editing, which includes in-app photo editing and saving in iOS camera app. There’s cut to actions, which allows you to extend, manipulate existing actions between apps, and the notification center, which allows for interactive notifications.

There's also custom keyboards, which enables third-party keyboards to be used in the OS and iOS apps, and documents, which allows you to open edit more documents to share without creating copies. And here’s a short list of the new capabilities Apple’s opening up for developer access interaction. They include photo kit, which allows you to work with photo and video access. There's the manual camera controls, gives you direct control of the camera. HealthKit, access to shared health related information. There’s HomeKit, which gives you control connected devices in the user’s home. There’s cloud kit, which allows you to securely store and retrieve app data from the iCloud. Hand-off which we referred to earlier, which allows you to start an activity on one device and finish on another. And touch ID authentication, which we discussed earlier. Also it will support new gaming functionality with sync kit user functionality, including quick type predictive text input, messages with audio and voice, updated calendar invites, updated mail, updated reminders, there’s a who’s important shortcut, third-party keyboard support, new Siri commands, business info and mail, and maps, and ability to answer calls on a separate device as well as augmented spotlight search.

All of these features add to the complexity of what iOS 8 supports and therefore definitely can become quite a bit of a problem when needing to insure the quality of your application while using these features.

It’s also important to understand maybe be reminded the value of the user experience and what can happen if the quality of the experience is not taken into consideration when updating the iOS 7 app or creating a new iOS 8 app. Insuring that quality can mean the difference between five star and….this. While there can be uncontrollable circumstances such as networks speed or relying on third-party applications, many times it can be simply the user’s experience as seen here.

Here you see some wonderful response once someone starts, but in the end some very dissatisfied customers. You definitely want to avoid this.

Second, apps crashing is unfortunate and is definitely becoming more common. This can mean life or death to many applications. And even after we were receiving the report you still need to take the time to understand it and acknowledge the issue. You still need to transfer information to engineering, validate the problem, build and test the fix. And obviously deploy a new version of the app. This is getting more and more complex. And according to E-Consultancies, only 16 percent of consumers will try a failing app more than twice before dumping it. A poor mobile app experience is likely to discourage users from using an app again. There is a very narrow window to get it right and no room for error.

Third, we must understand this will happen again, and I’m not just talking about iOS 9. See, it would be nice if we could build and test and ramp up for one release and be done with it; pretty much like desktop applications. But we all know that is not the case. It’s more like this. The reality is once you have launched a stable iOS app, there is an upcoming Android version out you need to update for followed by an iOS 8.1, Windows 9, etc. etc. etc.

And it’s not just the iOS versions but the form factors as well. Launching alongside iOS 8 this fall is rumored to be the next generation iPhone six expected to come in both a 4.7 inch and a 5.5 form factor. Also, it is being reported they are preparing a larger iPad release for early 2015. With so many releases and form factors to keep up with it is no wonder many developers, QA organizations, and even IT organizations are struggling to maintain balance.

“So, what’s the good news?” you might ask. How do I make sense of the madness? Well, here are five steps to that we think will help you in your development and testing process for both iOS 8, 9, 10 and beyond.

First, automate your test cases. If you’re in QA specifically, being able to perform regression testing of a functional test case is critical to being able to be more efficient resulting in even more testing and thus a better app. In Keynote’s 2014 mobile quality survey, we found that only 14 percent of respondents were automating more than 50 percent of their test cases. That tells me there’s a lot of manual testing going on and more automated testing is needed. Second, testing on real devices and those being available 24/7. Sure emulators have their place but nothing beats finding a bug in a real device, prerelease that can minimize cost the app fixes later.

And having devices available 24/7 can enable remote or distributed teams to run testing on the same device around the clock if necessary. Third, use best practices for continuous integration. Developers, testers, and managers are moving away from traditional testing especially late in the development to early agile testing practices especially in mobile. Many teams are adopting continuous integration tools such as Jenkins to speed up and streamline their development and testing processes in order to meet the demands of this condensed mobile-centered timeframe. Testing on real mobile devices through this integration tool gives you the most accurate view in to how your mobile app or website will perform in the real world—all in a preproduction environment.

As a side comment, we would like to invite you to join us on Thursday, September 11 for a how-to webcast on performing automated testing from Jenkins on real devices. You should check it out. Just send us a note about the webcast if you’re interested or look for the link.

On to No. 4. Use a central repository. This central repository of the ever increasing number of test cases, both manual and automated, that you want or need to run again through application. This one is pretty simple. There are tools that can help by centralizing all these test cases, depending on how many of the APIs and app extensions you utilize in iOS 8, we estimate that we could see up to a 10x increase in test case creation on one app alone.

So dump the spreadsheets and centralize what you have. Build it right and make it easier on yourself and your teams, especially if they’re distributed in other regions.

And lastly, continuously monitoring the quality of sources of your application. Post production. For QA developers, data analytics can provide valuable information to help refine, improve, and guide you to maintain success and staying above the fray. It’s also extremely helpful for operations teams to be able to support the applications deployed from your organization. Recently it was estimated by ComScore that roughly 65 percent of those consumers surveys downloaded one new app or less per month for their smart phone. This was from January to June of this year. Even as their total app usage time continued to rise. So while the app usage continues to rise the amount of new apps that consumers have been downloading since the beginning of 2014 has been one app or less per month. Consumers are getting more comfortable with the apps they have and this tells me that improving my app quality is critical to retaining customers.

All right. So now we’d like to hear from you. We’re going to call the poll question and this is all about iOS 8. We’re going to get your feedback. When it comes to iOS 8 what do you see is the biggest concern or are the biggest concerns?

Please select all that apply. You can choose updating or recoding our current apps to support new iOS functionality; proper test coverage from my application; troubleshooting issues in my production; and/or low no visibility into how users experience my apps. Please go ahead and continue to submit your responses. That’s great. Keep going. That’s awesome. Thank you. Looks like we’re seeing some more popular answers that’s awesome. Good coverage. Great. We’ll go ahead and post the response. Excellent. Looks like updating and proper test coverage are the biggest concerns and that is consistent with what we’re seeing and also with what we’re showing.

Let me go ahead and go back to the slides. So how is Keynote getting ready is the biggest question everybody is wondering. We’ve been working hard here as iOS 8 is been coming up quickly on us. We're getting ready for the September 9 launch. We just want to cover a few things of what we’re doing internally within Keynote to prepare for this much-needed testing that’s going to be needed for iOS 8 specifically. The good news is that we are ready. Keynote’s mobile testing platform on day one will support these models with iOS 8. That includes the iPhone 4s, 5, 5s, 5c, as well as the iPad second, third, and fourth generation. It will also include the iPad Mini and the iPad Air.

These devices will be ready and waiting to test monitor in the new iOS 8 environment. Also, existing Keynote customers are already working on beta iOS 8 versions on their devices. If you’re an existing customer this is something you can take advantage of; we can support updating your devices with iOS 8 beta 5, and as the final release comes out we will update accordingly. This is something we can do instantaneously, simple to update the device we update the firmware, and since there’s no software on the device we can do this very easily. And second, our engineering team is busy working iOS 8 support for object-level scripting. This enables our robust text automation framework, which allows you to automate across multiple devices and to do it all on the object layer as opposed to text or image based.

So what is Keynote’s mobile testing platforms? Understandable question. When it comes to functional testing of mobile apps and websites, there is no substitute for real devices or real carrier networks using real mobile browsers. Our platform gives you an efficient and easy way to test any mobile application including native, hybrid, or web from anywhere in the world. How do we do this? We have built the world’s largest cloud library of real mobile devices built on Keynote’s patented, direct to device technology. With this technology, we are able to integrate any mobile device via hardware electrical connection, no software required.

Any action that can be performed on a mobile device in hand can be done with Keynote mobile test. This technology is the reason we are able to give our customers the best and most accurate cloud-based mobile testing solutions available. And for closed production monitoring we offer a mobile application monitoring solution. Mobile app monitoring continuously interacts with your apps 24/7 exactly like a customer does in the real world. It is the only 100 percent cloud solution requiring no modifications to the app being monitored. This is perfect for your operations team to be able to monitor and report back to you the data you need to provide the best possible user experience.

Now I am pleased to turn it over to Chris and Jason for a live demo of the several iOS features. As a reminder please feel free to submit any questions during the discussion. You can do this in the QA panel at the bottom section of the window. Also, don’t forget to join the conversation on Twitter. Just join our community using #iOSappsquality.

Chris:                          

Thank you Josh. My name is Chris Karnacki. I’m a solutions consultant here at Keynote Systems. I’m going to be walking through a demonstration of Keynote’s mobile testing tool showing you how to use it to test your iOS 8 applications and be sure you’re ready on or before the release date of iOS 8. We’re going to touch on a few things here, some of the new features and functionalities that have been added to iOS 8. First, you see here is the HealthKit. That’s the health app first which is the dashboard for your health and fitness data. It’s the new iOS application to track not only your fitness and health activity but also go all the way in to your things like your medications and doctor data.

There’s also the HealthKit, which allows for that extensibility of existing applications, fitness applications from third parties to work together and actually be data sources for the iOS 8 health application. There’s also the new notification center, which includes interactive notifications. This is going to allow your applications to provides notifications in the iOS 8 notification center, but allow the users now to actually interact with that notification. In the example of an SMS notification, they can actually reply directly from the notification itself without having to switch to the application. There’s also the new hand-off feature. This is going to allow users to start an activity within your application on one device, maybe an iPad, and actually finish it on another device, say an iPhone, without actually starting over.

There’s also the new photo editing tools and APIs. This is going to allow you to embed custom filters and editing tools both in your application and also to the stock iPhone or iPhone or iOS 8 photo application. A few other mentions are the quick type predictive text input. This is going to make it easier for users to input text into your application. It will provide them with options to choose basically predictive on what they might be typing, and it’s actually going to be intelligent and use context on who they are actually speaking with or the context of that input. Also, another new functionality is going to be messages, so SMS or MMS or i-message with audio and voice. A quick voice clip or a quick video clip.

Let me go ahead and bring up Keynote’s mobile testing tool and walk through how to be able to test this new functionality within your application on iOS 8. Let’s start by taking control of this iPhone 5s. This iPhone 5s is running iOS 8 beta 5. You’ll see the new health application here. This is a real iPhone 5s with full voice, data, and messaging plan. What you see on this device screen is the actual screen the user would see if they were using their iPhone or their iPad. It’s just like having the device sitting in the palm of your hand. There’s no emulation or simulation here. This is a real live device just like you or your users would have.

Now in order to test your application, you need to install it on this remote device, which you can do from the Apple app store or by using the Keynote application installation utility built into the actual tool. This enables you to test both prerelease and production release applications. Once installed navigating the phone or tablet is just like having it in your hand. You just use your mouse and keyboard instead of your fingertip. You can launch your application by clicking on it. We’ll open up a little notepad application here. Keynote allows you to enter text with the device just like a real user would. We’ll go ahead and click on the phone, and again this is a real phone.

We’ll go ahead and type just like a user would. And because this is a device being controlled at the hardware level, we’re interacting directly with the same controllers that a real user would if they were interacting with that phone in their hand. We can also insure proper behavior based on the device orientation. If you want to make sure your application behaves properly, possibly different functionality based on the rotation of the device, we can rotate the phone and you’ll see that the phone responds accordingly. We can actually even remotely power cycle the device if your application hangs or you want to perform interrupt testing. We have control of the battery here.

An additional benefit to using Keynote to test your iOS 8 or other applications is the ability to easily collaborate with your team. You can take screen shots of the device either in real time or by utilizing our built-in DVR. We have options here to export frames or screen shots of the device in real time as we walk through or we have a built in DVR that allows you to pick and choose screen shots or created video to provide to your teams should you find a bug or a defect. This lets you create screen shots or videos from your recent interaction with devices. It’s a very powerful way to share testing results with other members of your team or organization.

Now let’s take a look at how you can test some of the new features and functions available to you and your application in iOS 8. One of the exciting new features of iOS 8 is the HealthKit. This new feature allows third-party applications to be a data source for the iPhone health app. Let’s go ahead and open up a Nike FuelBand application. You’ll see here that the Nike app is recording activity from a Nike FuelBand. You can test your application to be sure that it’s functioning properly and then also that it goes to the health application. So you can navigate your application just as we would with the phone in our hand by clicking on the device screen and then we can go into the health application and make sure that that data is actually being presented to the health application properly.

In this case the iOS 7 version of the Nike application cannot pass its data to the health app. Therefore the health app has no data sources currently but you would see here in these sources for the health app, on day one. Or if you’re testing your prerelease iOS application, you can be sure its function is working properly.

Another new feature in iOS 8 is the interactive notifications. This will allow iPhone and iPad users to interact with the notifications from your application without unlocking their device or even opening your application itself. Let’s take a look at how this works. I’m going to take control of the iPad running iOS 8 this time.

I’ll send a message from the iPad to the iPhone. Open up messages. As I’m typing you can see the new quick text predictive input keyboard here. If we had third-party keyboards, which is another functionality or new function of iOS 8, those custom third-party keyboards, we would see the option to use in here as well. Let’s send this text message. And coming to the iPhone 5 we see that the message has been received. Now we can slide down the notification center. And here we can check the application and be sure it works properly with this new interactive notification center. We can reply to the message itself directly from the notification. If I click in here or we come back to the notification we can actually reply directly from there. Let’s go ahead and reply.

Hit send. We can come back to our iPad and we see that the reply was received. There it is. The interactive notification center function is working with the application under test. This of course was the iMessage or messages application but the same testing could be done through your notifications provided by your third-party application. Now that I have two devices on my control I can test the new hand-off function that allows a user to start using your application on one device and then continue using it without starting over on another device. This can be easily tested using two devices as I have here in my control. Apple has also made improvements to its own photo filters and editing tools with iOS 8.

In addition to those improvements, developers can add their own custom filters and editing tools to the photos app on iPads and iPhones. Let’s open up the photos app. We can see a photo here. We select edit. We can see Apple’s new editing tools here on the bottom both filters and rotation and cropping. If your third-party application has its own editing tools or custom filters you can make them available in the photo app as well. And simply test them by interacting with this real device. Just as I would do here with the existing stock filters and editing tools. So remember it’s imperative to test early and test often. This is even more important with a major operating system release like iOS 8.

Your customers and users will expect your application to not only support the new features and functions of iOS 8 but also to work flawlessly. You can assure this stellar customer experience by being ahead of the curve and testing your applications with Keynote.

Josh:                  

Great things Chris. It was awesome—thank you for sharing that. Right now we’d like to go ahead and take some questions from you. Go ahead and feel free to please submit any last minute question you have in the QA panel. We’re getting a lot of great questions already. The panel is located at the bottom section of the window. And if we don’t have time to get to your question today we will certainly reply to it offline after the webcast. We also encourage you to join our Twitter community today using #iOS8appquality. All right. Let’s get to a few of the questions. The first question we have is why is app testing on real devices so important?

Chris:                          

Testing your applications on real devices is important. There is a place for emulators and simulators but to get the real user experience and find out how the application is performing and behaving on a real device is crucial because emulators and simulators do not always provide that exact experience. So the Keynote mobile testing tool you have access to a cloud of real devices to make sure that you didn’t miss a certain bug or defect that may not show or present itself from an emulator or simulator.

Josh:                  

Awesome. Thanks Chris. This one is for Jason. Jason why should developers test their apps on new iOS as early as possible?

Jason:                         

This is Jason. As earlier as Josh mentioned iOS 7 has the fastest adoption rate in the market compared to other OS. Here I want to also share some key points. One day after iOS 7 released the adoption rate was 1.84 and three days after was 15.42 percent. Four days after it was 38.02 percent adoption rate. Three months after release was 74 percent. And currently it’s 90 percent or greater than 90 percent. In structure of faster adoption rates customer would be expecting their apps working the new apps working on their devices. As an app developer you want to have those applications ready when the device iOS released. You should test as soon as possible to impress your customer.

Josh:            

Great. And for Chris I’ve got another great question. What automation tools does Keynote prefer and/or offer for testing on mobile devices both automation and manual?

Chris:                          

Sure. Keynote has its own mobile test automation framework from within our mobile testing tool. But we do also support testing using Selenium against these cloud devices as well as using UI automation for iOS devices specifically. That can be used using our visual interface as you saw here today or using an API to actually access those remote devices and run your automation tests.

Josh:                  

Great. Another question here from Mike. Does Keynote provide iOS 8 beta and final bills on various Apple devices for testing it? How does that work?

Chris:                          

Great question. If you are a current or existing Keynote customer for mobile testing and you are part of the Apple developer community Keynote can provide iOS beta for your real iOS devices both iPads and IPhones for you to test before the general release of iOS 8. Once the iOS 8 is out to the public or the general release is out, Keynote will be updating some of its devices both in the shared cloud or if you are a customer and have your own private mobile devices. We can provide both beta and the gold master release depending on your situation.

Josh:                  

Excellent. I’ve got another question here. Can the cloud test devices connected to iCloud and Gmail accounts like….can we do that?

Chris:                          

It’s another great question and the answer is yes. Because these are real devices out in the cloud you just have remote access to them and they absolutely can connect to an iCloud or a Gmail account or Google account just as the phones that you may be using today to test. Because they are real devices they have the same functionality.

Josh:                  

What changes should we anticipate in terms of if we’ve already scripted and already tested before iOS 8?

Chris:                          

Depending on the way you decided to create your automation scripts within Keynote there may be very little change or likely no change needed for iOS 8. Because they are real devices using the same testing framework there should be no changes. The only changes you may need to make are changes to the scripts to test the new functionality that you have added with the iOS 8 extensibility and new notification functions.

Josh:                  

Okay. Another question here around do you have to route the device to get hardware control? How does that work?

Chris:                          

Another great question. No. We do not have to jailbreak iOS devices or route Android devices. The control is all done at the hardware level. As you are interacting with this real device from your computer as you saw during the demonstration today you’re actually interacting with the hardware. For example when I clicked on the icon on the device screen to launch an application the phonies receiving the same electrical impulse that it would if a user’s finger were touching the screen. We’re not installing any additional software to the device to drive it or control it and because we’re not doing that we do not require root or jailbreak.

Josh:                  

Okay. So think like you’re using real devices and these are not emulators correct? If so how do you handle the accelerometer or how does that work remotely if people can access it? Maybe talk a little bit about sharing.

Chris:                          

Sure. Another great question. Because it is a real physical device that is integrated with at the hardware level again no software is installed we actually have full control of that physical accelerometer chip. When I rotated that device 90 degrees and we saw the notes application rotate with the device that is not doing an API call to the phone telling you to rotate the screen it is actually physically controlling the accelerometer chip of that iPhone or iPad or whatever device it is that you are testing. Because of that your application will respond just as though a user is rotating the device. It is a very important distinction because if your application has different behavior – maybe it’s a video application – when you rotate the device on its side then the screen goes full screen. If you’re doing API call to the device and not controlling it via hardware then that screen will not go in to full screen it will likely just rotate but not expand.

Josh:                  

Okay. Great. With the question on what devices we’re going to support I know we’re getting a lot of questions around which devices we’re going to support on day one. Maybe reiterate what models we’re going to cover and we’re going to be updating. Jason do you want to take that? Which models?

Jason:                         

We will support all models across the iOS iPhone 5.4s and 5’s 5c, 5s, and all iPads that supports iOS 8 through second generation, third generation, and fourth generation, the newer iPad Air plus the iPad minis. All devices will be supported on day one.

Josh:                  

Okay. And as far as maybe just talk a little bit about – great question on jailbreak and we discussed that - maybe reiterate.

Jason:                         

The devices are not jailbroken. We are controlling them via hardware. There is no software that Keynote installs onto the device to both stream the device screen to your computer or control the touchscreen accelerometer, any of the buttons on the device. It’s all being done via hardware controls. Because we’re doing those hardware controls we do not need to jailbreak iOS devices or root Android devices. You are actually interacting and testing against a device just like your end-users will have in their hand. You don’t need to worry that Keynote is installing something on the device that your users won’t have. You are getting the true user experience and true user representation.

Josh:                  

Great question here for Jason. Does Keynote allow testing on local devices. We showed the hardware integration but how does it work for local?

Jason:                         

Device also can be deployed to a local desktop. The device will be same as any device that you control over the cloud. There is no difference.

Chris:                          

Yeah. Your local device would appear in that same interface that you saw during the demonstration today. You would be using your local assets you already own.

Josh:                  

Another question here. How does Keynote help developers perform app testing and monitoring and we talked a little bit about monitoring but maybe you know discuss what we offer….  

Chris:                        

Application testing that functional testing is kind of what we walked you through during the demonstration. Of course test the functionality of your application then specifically to this webcast the new functionality that you can do with iOS 8. For monitoring once your application is released, it’s out in the public, downloadable, and starting to get adopted by your clients and your end-users Keynote provides a cloud service that allows you to monitor and measure the user experience and response time of your application. Now that the application is out, you finish your functional testing in QA to release to production and your operation team is tasked with making sure that the application is always available and that it is performing per your SLAs or your stated targets, Keynote provides a cloud service that allows you to monitor and make sure that you are meeting those targets.

Again it’s done on a cloud of real mobile devices just like we saw for functional testing.

Josh:                  

Good. Another question from Natalie. Do the devices you provide for testing include both carriers and Wi-Fi functionality past any interruption the user might experience between a cell phone carrier to a Wi-Fi network?

Chris:                          

That is a very good question. The devices all include both carrier and Wi-Fi connections. It’s just like a phone in your hand or sitting on your desk. Both tablets and phones can be on carrier and or Wi-Fi. And as part of your manual or automated tests a switch can be made on the device just as you would if that phone was in your hand by going to the phone or tablet settings and enabling or disabling Wi-Fi and or the carrier service.

Josh:                  

Another question here around does Keynote support legacy devices like iOS 6, 5, others? Great question too.

Chris:                         

Yes we do. Our cloud of mobile devices for testing does include not only iOS 8 – which of course is the focus for today – but iOS 7, 6, 5, all the way down to iOS 4. Because we all know that not every user updates their iOS version on day one or even day 365. You need to make sure that your application can continue to work on those older versions of iOS or Android and Keynote does provide devices with those legacy OS’s.

Josh:                  

Good. And when can we expect the beta release to Keynote customers? How does that happen and how do they get in touch with their –

Chris:                          

Yeah. If you are an existing Keynote customer reach out to and contact your account executive or solutions consultant and we’d be happy to work with you to get that iOS beta loaded on to your devices so you can begin testing before it’s released to the public.

Josh:                  

Okay. Last question. It is around the health app and third-party app and how we support that and how do we manage in general. Obviously there’s going to be a new health app and there’s going to be injection from other applications and…

Chris:                          

Yeah. As part of the new health app there is Apple has HealthKit which is going to allow your health application or other third-party health applications to share its data with the iOS health app or Apple health app. You can use these real mobile devices to not only do functional testing of your application itself and make sure that your application is functioning but also then test that the data is being shared properly and that your application is becoming a proper data source for the health application. That will insure that not only is your application working but that the HealthKit APIs that you are invoking in calling to share that data are working as implemented in your application.

Josh:                  

Excellent. Thank you all and thanks for your questions. We’ll go ahead and wrap things up. I know we’ve got a lot of your questions we weren’t able to get to today but we’ll get to them when we follow-up with you individually. Thank you for that. You can also contact us directly at sales@keynote.com. Let me go ahead and I know we had a lot of great questions around how to get started so I’ll cover that real quick. As Chris mentioned if you are a current customer of Keynote you can contact your rep or solutions consultant to have them upgrade your current devices with iOS 8 beta. If you are not a customer yet now is a great time to join.

Just click the free trial link in the link window and register. Just watch on day one we will have updated our device with iOS 8 enabled devices ready to test. We’re going to go ahead and bring you the link window so you can click on that link and there’s also some other great links in there. Lastly for those who don’t have time to test feel free to contact one of our iOS 8 enabled partners below. For more on iOS 8, feel free to click on the Learn More link in the window. You can read a great blog post that was posted last night. You can also watch our webcast on continuous integration on-demand. Also, please feel free to download the webcast slides. That’s it.

Thank you so much for everyone for attending today. We hope this webcast is both educational and informative. We’ll see you next time. You may now disconnect.

Duration: 45 minutes

Back to Top