WWDC 2018: the announcements
and their lasting impact

Apple’s Worldwide Developers Conference in 2018 brought together several ideas that still make useful starting points for product design: make everyday tasks faster, give people control over interruptions and let an app’s useful actions extend beyond its own screens.

The conference ran from 4 to 8 June 2018 in San Jose. Its opening announcements included iOS 12, macOS Mojave, watchOS 5 and tvOS 12, alongside capabilities such as Siri Shortcuts and ARKit 2.

This retrospective looks at the main announcements, distinguishes previews from later releases and considers their practical significance for businesses developing applications. It is a historical account with product analysis, not implementation guidance for current Apple APIs.

What did Apple announce at WWDC 2018?

Apple’s WWDC 2018 highlights provide a contemporary record of the presentations. The announcements were a roadmap for the platforms, not a statement that every feature was publicly available that day.

iOS 12 put everyday performance in the foreground

In its iOS 12 preview, Apple emphasised faster and more responsive everyday interactions, including on older supported devices.

That was a meaningful product message. Improvements to familiar tasks can be valuable even when they do not create a new screen or a dramatic demonstration.

For an app team, the corresponding work might involve reducing startup delays, keeping typing responsive or showing a useful result before every background operation has finished. Those improvements should be measured on devices representative of the audience.

A product that feels quick on a developer’s phone may behave differently on an older device with a weaker connection. Test the actual journeys people repeat, including sign-in, search and completing a transaction.

The lasting lesson is to give performance its own place in the roadmap. Feature delivery and usability are connected: an important feature that is slow or unreliable may not deliver its intended benefit.

Siri Shortcuts made individual app actions more important

Apple’s June 2018 developer announcement for Siri Shortcuts described ways for people to complete app-related tasks through surfaces including the lock screen, Spotlight and the Siri watch face.

For product teams, the interesting shift was from thinking only about an app’s navigation to identifying the actions someone wants to complete.

Consider checking a booking, starting a familiar activity or retrieving a particular piece of information. Each is a task that can be designed independently of the sequence of screens usually used to reach it.

That requires clear behaviour. What information is needed? What happens if the user is signed out? Does the action merely display information, or does it make a change that needs confirmation?

This remains a useful design exercise even when implementing a different integration. Well-defined actions are easier to expose through alternate interfaces than behaviour tightly coupled to one screen. The historical Shortcuts announcement illustrates that principle; it should not be used as documentation for the APIs a project should adopt today.

Screen Time challenged a simple view of engagement

Apple introduced Screen Time and interruption controls as part of iOS 12. These included activity reporting, app limits and changes to notifications and Do Not Disturb.

The product implication was that time spent in an application is not always the best measure of value. For many services, the user wants to complete something and move on.

A booking app can succeed by making a reservation quick. An internal tool can succeed by reducing the time an administrator spends assembling information. In those cases, longer sessions may indicate difficulty rather than engagement.

Apply the same judgement to notifications. Ask whether an alert needs immediate attention, whether it can wait and whether the user has a clear choice about receiving it.

Useful metrics include successful completion, repeat use when the need returns and requests for assistance. They give more context than the number of times a notification was opened.

ARKit 2 expanded shared and persistent AR

ARKit 2 introduced support for shared experiences and persistent augmented reality, along with improvements including 3D object detection and image tracking. Apple also presented its Measure app and the USDZ format, developed in collaboration with Pixar, for sharing 3D content.

These were distinct parts of a broader opportunity: experiences could be shared between people, revisited and distributed through familiar ways of handling content.

For a business application, the first question is what spatial interaction adds. A product preview may help someone understand an object’s appearance in a room. A collaborative experience may help several people examine the same arrangement.

Neither use becomes valuable simply because it uses AR. Test whether it improves the customer’s decision, and account for the work needed to create suitable 3D assets. Lighting, environment and device support also belong in the evaluation.

The lasting lesson is to scope the content and the interaction together. An impressive technical capability still needs an accessible, useful experience around it.

macOS Mojave combined visual change with workflow improvements

Apple’s macOS Mojave preview introduced Dark Mode, desktop Stacks and improvements to Finder and Quick Look. It also described privacy changes, including permissions for camera and microphone access.

The same announcement previewed work to bring iOS frameworks to the Mac, with wider developer availability planned for 2019. That was a preview, not a general release of Mac Catalyst at WWDC 2018. Apple later included Mac Catalyst in its October 2019 macOS Catalina release announcement.

For product teams, this provides two useful lessons. First, small workflow improvements can reduce effort across frequently repeated tasks. Second, sharing code across platforms does not remove the need to design for their different interaction patterns.

A desktop user may expect keyboard shortcuts, multiple windows and dense information. A phone user may need a focused task that works comfortably with touch. Reuse should support those experiences rather than forcing them into identical layouts.

watchOS 5 focused on activity and brief interactions

The watchOS 5 announcement included activity competitions, automatic workout detection, new workout types, Walkie-Talkie and podcasts.

Those features illustrate the need to design around the device’s context. A wrist interface is well suited to a glance, a short interaction or information relevant to an activity already underway.

For an app project, start by identifying what belongs on the watch. A quick status check might make sense there; a complex setup flow may belong elsewhere.

Test whether the interaction can be understood without prolonged attention. Decide what happens when a connected phone or network is unavailable. Moving a phone screen onto a watch is a layout exercise; designing a useful watch experience requires choosing the right task.

tvOS 12 showed the importance of the complete experience

Apple’s tvOS 12 preview included Dolby Atmos support for Apple TV 4K. The announcement concerned the quality and convenience of entertainment in a living-room setting.

For software teams, it is a reminder that a feature depends on the surrounding experience. The device, available content and the user’s equipment can all affect what is delivered.

Design for supported combinations and communicate limitations clearly. A capability on a specification sheet is only useful when the customer can access it in practice.

Group FaceTime: announcement and release were separate events

Group FaceTime was previewed at WWDC as part of iOS 12. However, the initial public iOS 12 release arrived on 17 September 2018, while Group FaceTime followed with iOS 12.1 on 30 October.

That distinction matters in a historical account and in product planning. Teams building against a platform preview need to follow release notes, test supported configurations and avoid treating keynote demonstrations as delivery guarantees.

Where a planned feature depends on an unreleased capability, identify the fallback and the impact of a delay before making commitments to customers.

What should app teams take from WWDC 2018?

The event’s useful legacy extends beyond its individual feature names. It brought together several recurring product questions:

• Can people complete everyday tasks quickly on the devices they own?
• Which actions should be accessible beyond the app’s main screens?
• Does an interruption help the user, and can they control it?
• Does a new interaction offer enough benefit to justify its complexity?
• What must change when an experience moves to another device?
• Which dependencies are available now, and which are still previews?

Use those questions to evaluate a roadmap. A platform announcement can reveal an opportunity, but it is the user’s task that gives the development work a purpose.