Is Apple's Watch in jeopardy? Crisis at firm making sapphire screen for wearable deepens

• GT Advanced Technologies has been working with Apple on sapphire glass plant      
• Filed for bankruptcy last week     
• Apple says it will 'continue to evaluate the firm' but admits it is looking at other options to source screen  

The company that was due to make the scratchproof sapphire glass screen for the Apple Watch it still in crisis and may be forced to shut down, it has been revealed. 

GT Advanced Technologies, a former stock market darling and supplier to Apple, filed for bankruptcy on Oct 6 in a stunning turn of events for a company whose fortunes looked bright only a few months ago.

Apple said on Thursday that GT's 'ambitious' vision of sapphire manufacturing was ultimately not quite ready for primetime.

Few details have emerged since the bankruptcy filing, which wiped out most of GT's market value and triggered speculation over what may have soured its relationship with Apple.

But on Thursday, Apple, which had backed the development with GT of a sapphire-manufacturing plant in Arizona, said it will keep an eye on GT's advances, holding open the possibility of doing business with it in future.

'Apple put a lot of effort into an ambitious new sapphire manufacturing process with GTAT which is not ready for production. 

'We're going to continue evaluating GTAT's progress on larger sapphire boule development, as well as consider other options for the facility,' spokeswoman Kristin Huguet said, referring to raw cylinders of the material.

At the heart of GT's bankruptcy filing was a deal struck with Apple in November 2013. 

GT Advanced was to have used the Arizona plant to make scratch-resistant sapphire exclusively for Apple. 

That sapphire was to have eventually found its way into future mobile devices, such as iPhones - where it's already in use in their fingerprint sensors - or the upcoming Apple Watch.

iPad mini 3 release date, features, specs, UK price: Apple unveils iPad mini 3, kicks off orders

Apple unveiled the iPad mini 3 on 16 October (if you blinked you'd probably have missed it), alongside the new iPad Air 2, introducing a new gold colour option, the Touch ID fingerprint sensor beneath the Home button. Here, we bring you the latest iPad mini 3 release date information, as well as the iPad mini 3 price so you'll know how much the iPad mini 3 will cost.

iPad mini 3 vs iPad mini 2: What's the difference?  The big question for potential iPad mini customers is going to be: What's the difference between the iPad mini 3 and iPad mini 2? Disappointingly, it's largely similar, with the same screen, the same camera, the same design apart from the new gold colour and even the same specs.  Yep, that's right, the iPad mini 3 doesn't even have the new A8 processor found in the in the iPhone 6 and iPhone 6 Plus, or the A8x processor found in the iPad Air.

iPad mini 3: Release date

Apple has kicked off pre-orders for the iPad mini 3, ahead of its release alongside the new iPad Air 2 next week. Strangely, there's no actual release date yet for the iPad mini 3, with Apple simply saying that it will be available "Starting later next week."
At time of writing, you can order the iPad mini 3 from the Apple Online Store, and it'll be dispatched within 2-4 days, so you could get it delivered to you as soon as 22 October. There's no word yet about whenthe iPad mini 3 will be available in store, but it looks like there'll be no early opening and giant queue outside Apple Stores like there usually is, which is a bit of a departure for the company.

iPad mini 3: Price

As expected, the iPad mini 3 starts at £319, like the iPad mini 2 did before it. There are three configurations available: 16GB, 64GB and 128GB.
Apple is continuing to sell the iPad mini 2 with a new price tag of £239, and two configurations: 16GB or 32GB. The original iPad is now Apple's cheapest iPad ever at £199.

Understand How an App Extension Works

An app extension is not an app. It implements a specific, well scoped task that adheres to the policies defined by a particular extension point.

An App Extension’s Life Cycle

Because an app extension is not an app, its life cycle and environment are different. In most cases, an extension launches when a user chooses it from an app’s UI or from a presented activity view controller. An app that a user employs to choose an app extension is called a host app. A host app defines the context provided to the extension and kicks off the extension life cycle when it sends a request in response to a user action. An extension typically terminates soon after it completes the request it received from the host app.

For example, imagine that a user selects some text in an OS X host app, activates the Share button, and chooses an app extension from the sharing list to help them post the text to a social sharing website. The host app responds to the user’s choice by issuing to the extension a request that contains the selected text. A generalized version of this situation is pictured in step 1 of Figure 2-1.

In step 2 of Figure 2-1, the system instantiates the app extension identified in the host app’s request and sets up a communication channel between them. The extension displays its view within the context of the host app and then uses the items it received in the host app’s request to perform its task (in this example, the extension receives the selected text).

In step 3 of Figure 2-1, the user performs or cancels the task in the app extension and dismisses it. In response to this action, the extension completes the host app’s request by immediately performing the user’s task or, if necessary, initiating a background process to perform it. The host app tears down the extension’s view and the user returns to their previous context within the host app. When the extension’s task is finished, whether immediately or later, a result may be returned to the host app.

Shortly after the app extension performs its task (or starts a background session to perform it), the system terminates the extension, as shown in step 4.

How an App Extension Communicates

An app extension communicates primarily with its host app, and does so in terms reminiscent of transaction processing: There is a request from the host and a response from the extension. Figure 2-2 shows a simplified view of the relationship between a running extension, the host app that launched it, and the containing app.

App Extensions Increase Your Impact

Starting in iOS 8.0 and OS X v10.10, an app extension lets you extend custom functionality and content beyond your app and make it available to users while they’re using other apps or the system. You create an app extension to enable a specific task; after users get your extension, they can use it to perform that task in a variety of contexts. For example, if you provide an extension that enables sharing to your social sharing website, users can use it to post a remark while surfing the web. Or if you provide an extension that displays current sports scores, users can put it in Notification Center so that they can get the latest scores when they open the Today view. You can even create an extension that provides a custom keyboard that users can use in place of the iOS system keyboard.

There Are Several Types of App Extensions

iOS and OS X define several types of app extensions, each of which is tied to an area of the system, such as sharing, Notification Center, and the iOS keyboard. A system area that supports extensions is called an extension point. Each extension point defines usage policies and provides APIs that you use when you create an extension for that area. You choose an extension point to use based on the functionality you want to provide.

Table 1-1 lists the extension points in iOS and OS X and gives an example of tasks you might enable in an app extension for each extension point.

Table 1-1Extension points in iOS and OS X
Extension point
Typical app extension functionality
Today (iOS and OS X)
Get a quick update or perform a quick task in the Today view of Notification Center
(A Today extension is called a widget)
Share (iOS and OS X)
Post to a sharing website or share content with others
Action (iOS and OS X; UI and non-UI variants)
Manipulate or view content originating in a host app
Photo Editing (iOS)
Edit a photo or video within the Photos app
Finder Sync (OS X)
Present information about file sync state directly in Finder.
Document Provider (iOS; UI and non-UI variants)
Provide access to and manage a repository of files.
Custom Keyboard (iOS)
Replace the iOS system keyboard with a custom keyboard for use in all apps
Because the system defines specific areas for app extensions, it’s important to choose the area that best matches the functionality you want to deliver. For example, if you want to create an extension that enables a sharing experience, use the Share extension point, starting with the Share Extension Xcode template.

IMPORTANT

Each app extension you create matches exactly one of the extension points listed in Table 1-1. You don’t create a generic extension that matches more than one extension point.

Xcode and the App Store Help You Create and Deliver App Extensions

An app extension is different from an app. Although you must use an app to contain and deliver your extensions, each extension is a separate binary that runs independent of the app used to deliver it.

You create an app extension by adding a new target to an app. As with any target, an extension target specifies settings and files that combine to build a product within your app project. You can add multiple extension targets to a single app (an app that contains one or more extensions is called a containing app).

The best way to start developing an app extension is to use one of the templates that Xcode provides for each extension point on both platforms. Each template includes extension point–specific implementation files and settings, and produces a separate binary that gets added to your containing app’s bundle.

To distribute app extensions to users, you submit a containing app to the App Store. When a user installs your containing app, the extensions it contains are also installed.

After installing an app extension, a user must take action to enable it. Often, users can enable an extension within the context of their current task. If your extension is a Today widget, for example, users can edit the Today view in Notification Center to enable your extension. In other cases, users can use Settings (in iOS) or System Preferences (in OS X) to enable and manage the extensions they install.

Users Experience App Extensions in Different Contexts

Although each type of app extension enables a different type of task, there are some parts of the user experience that are common to most extensions. As you think about designing an extension, it’s important to understand the user experience that’s intended by the extension point you choose. At a high level, the best user experience for all extensions is quick, streamlined, and focused on a single task.

Users open your app extension by interacting with some system-provided user interface (UI). For example, a user accesses a Share extension by activating the system-provided Share button in an app and choosing the extension from the list that’s displayed.

Although most app extensions provide at least some custom UI elements, users don’t see your custom UI until they enter your extension. When users enter your extension, your custom UI can help to show them that they’re shifting into a new context. Because users can distinguish your extension from the current app, they can appreciate the unique functionality that you provide. Users’ awareness of extensions as separate entities also means that they can identify and remove extensions that misbehave or don’t perform well.

To give users a smooth transition into your app extension, you generally want to balance your custom design with the UI that’s associated with the extension point. For example, it’s a good idea to make your widget look like it belongs in the Today view. Similarly, in your Photo Editing extension, it works well to create a UI that harmonizes with Photos in iOS.

NOTE

Even if your app extension doesn’t display any custom UI (other than an icon), users still understand that your extension is different from the current app because they took a specific action to activate it.

Source:  https://developer.apple.com/library/ios/documentation/General/Conceptual/ExtensibilityPG/index.html