

padOS
2019 Proposal
Ty Booyzen
 Table of Contents

Mission Control App Windows Mouse & Trackpad

6 15 Support 25
25

Files Multiple Users Xcode for iPad

40 46 50

!2
padOS Philosophy
Why padOS should exist.
When looking across Apple’s products, most core
categories have their own operating system: Apple TV
has tvOS, Apple Watch has watchOS, and Mac has
macOS. Regardless of which device you use, the UI is
tailored to its unique interactive medium and scale.
The minimal distinction between iOS running on iPad
and iPhone and the single name shared between
platforms is an important indicator that these products
are more similar than different.
For iPad to push into larger markets, customers must
see it as more than just a “big iPhone.” They need to
see it as something distinct.
Moving to padOS would indicate to customers, the
press and developers that Apple believes iPad will
offer a strong, unique platform moving forward. A
platform that truly represents the future of personal
computing and one that is worth an important re-
evaluation.
!3
Very different.
Much the same.
While the distinction between iOS and padOS should be
made in out-bound marketing and internal teams, the
overall management of padOS and its development
should remain tightly linked with those of iOS to ensure
continued familiarity, harmonic progression and a flow of
innovation between the platforms. In fact, padOS should
continue to share the same fundamental building blocks
of iOS by maintaining use of UIKit for app developers to
build their apps.
Designing for iPad with UIKit would also become more
attractive as Apple brings UIKit frameworks to macOS.
Effectively, designing large-scale, powerful apps will open
developers to two of the most vibrant platforms in the
world. Mac users will get access to more apps, and iPad
users will get access to the most advanced features.
By maintaining parity of core frameworks used for iOS and
padOS, and further developing these for macOS,
developers would be able to easily bundle their iPad,
iPhone and even their Mac apps together on the App Store.
!4
Benefits
Customers and members of the press will take another look at iPad Pro when confronted with a new OS and

1 productivity-focused features. It would indicate Apple’s confidence in iPad as a long-term answer to personal
computing for the masses. One worth investment and differentiation.

Internal teams who work on padOS will be more easily held accountable for the pace of innovation of the

2 platform. Software innovations on iPad would become an annual event rather than the bi-annual progression as
was seen with iOS 9 and iOS 11.

Distinguishing iPhone and iPad software will liberate UX designers and developers to build experiences specific
3 to iPad without the concern of designing comparable experiences for smaller displays.

Developers will feel liberated to build groundbreaking experiences for padOS without feeling obligated to

4 designate resources to building smaller-screen versions. They’ll also have an added incentive to make their app
full-featured as their padOS app is easily ported over to macOS using common UIKit frameworks.

!5
Mission Control

Come in, mission control.

Mission Control in padOS would offer a bird's-eye
view of all full-screen windows, Split Views, and the
Slide Over app making it easy to switch between
them, rearrange them, close them or even open
new windows.
Philosophy _______________________________________7
Execution ________________________________________8
User Guide ______________________________________9

!6
Philosophy
iPad has always offered an incredible step forward in UX
design: full-screen working environments. However, to
enable more efficient workflows, Slide Over, Split View
and Drag and Drop were introduced. While many have
called for this to be extended into a window-based
desktop UI like on macOS, this would remove much of the
simplicity that makes iPad magical. Instead, the current
Multitasking experience should be made more easily
managed with Mission Control.

For this to be successful, Mission Control should be

practically undetectable when users compare it to the
simplicity of iOS 12 multitasking. It should be discoverable
by those users looking for a more powerful experience
rather than central to understanding how to use iPad.

!7
 Execution
When padOS is introduced, Mission Control should
work immediately without the need for developers to
update their apps.

The system would use the existing key

UIRequiresFullScreen in an app’s Info.plist file, and
protocol methods such as applicationWillResignActive,
applicationWillTerminate, applicationDidBecomeActive
to give users control over apps from Mission Control.

Mission Control should be able to instantiate the same

changes users expect from previous versions of iOS
including opening a new instance of Split View, opening
an app in Slide Over, closing app windows, etc.

!8
User Guide
Open Mission Control
To open Mission Control, swipe up and pause in the
middle of the screen to see and switch between
recent apps and app windows.

Close an App Window

To close a specific app window:

1. Open Mission Control.

2. Swipe up on the app window you want to close.

!9
User Guide
Place Two App Windows in Split View
To open a new app window in a Split View from
Mission Control:

1. Open Mission Control.

2. On the Dock, touch and hold the app of which you

want to open a new app window.

3. Drag the app icon over the sides of the existing

app window you want to create the new Split View
with.

4. Release the app icon on the side that you want the
new app window to be on in the Split View.

!10
User Guide
Place Two App Windows in Split View
To place two full-screen windows that are already
open into a Split View together:

1. Open Mission Control.

2. Touch and hold on the first app window that you

want to merge into a Split View.

3. Drag it over the sides of the second app window

that you want to merge it with.

4. Release the first app window on the side that you

want it to be on in the Split View.

!11
User Guide
Close a Split View and Make Both Windows Full-Screen
To close a Split View and make both windows in the Split
View full-screen:

1. Open Mission Control.

2. Touch and hold one finger on the first app app window
and another on the second app window in the Split View
you want to separate.

3. Pull the windows apart and release.

Alternatively:

1. Open Mission Control.

2. Touch and hold on one of the app windows in the Split

View that you want to split.

3. Drag this app window out of the Split View and over the
background of Mission Control and release.

!12
User Guide
Change the Slide Over App to a New App Window
The Slide Over app is an app window that can be
summoned over other windows at any time when you
swipe left from the right edge of the display.

To change the app that is currently designated as the

Slide Over app:

1. Open Mission Control.

2. Swipe left to see the current Slide Over app window.

3. On the Dock, touch and hold the app of which you

want to open a new app window in Slide Over.

4. Drag the app icon over the current Slide Over app
window and release.

!13
User Guide
Move an App Window from one Split View to
Another
To move an app window from one Split View into
another:

1. Open Mission Control.

2. Touch and hold on the app window that you want

to move into a different Split View.

3. Drag it over the side of the app window in the Split

View you wish to replace it with and release.

The app window that is moved will retain its size. The
app window that remains in the destination Split View
will resize to fit.

!14
App Windows

Seeing Double. Seeing Triple.

Seeing… Multiple.
App Windows in padOS would offer the ability to Philosophy______________________________________16
open multiple documents or projects of the same Execution _______________________________________17
app in separate windows or tabs. And with App Guide __________________________________________20
Exposé, you could get a birds-eye view of all of an
app’s windows too.

!15
Philosophy
With Split View, iPad is able to run two apps side-by-side.
Many apps, though, are containers for documents,
projects or web views. Sometimes two of the same types
of files or views need to be worked on at the same time.
Sometimes they even need to be placed side-by-side like
when you want to move content between documents.

Multiple windows of the same app and window tabs will

facilitate these workflows for padOS users. However, to
maintain the simplicity of using iPad, multiple instance of
a single app should not be central to the way iPad works.
Users who need to enhance their workflows will be able
to dig further into the UI but regular users may not
discover the features unless they search for them or
discover them through the Tips app.

!16
 Execution
Window Management
Windows and tabs of a specific app would be viewable by invoking its
own window manager with a long press on its icon on the Home
screen or Dock. The window manager would have options to open a
new window, merge all windows, or close all windows — effectively
quitting the app. An app that does not support windows or tabs would
simply not present a window manager.
If a window with multiple tabs is selected from the window manager, it
would be expanded and options to split the tabbed window into
separate windows and an option to close those tabs would be
available.
If the app icon is tapped on the Home screen or Dock, the most
recent window or tab of the app would open; helping ensure that the
simplicity currently found with iOS persists.
!17
Execution
App Exposé
Each app’s window manager would also
have the option to “Show More” which
would open an app-specific version of
Mission Control called App Exposé.

!18
 Execution
Developer Support
An app would not automatically allow multiple windows or tabs. If
developers wish to support multiple instances of their app, they
would designate this with new keys in the app’s Info.plist file:
UISupportsWindows and UISupportsTabs. A developer could
support either or both of these.

New methods for instantiating and managing multiple app windows

and tabs would be made available as part of UIKit’s
UIDocumentController and UIDocument subclasses instantiated
under the UIWindow class. This would include important controllers
like UIWindowController and UIWindowTabController.

Developers would effectively be able to choose to offer “Open in

New Tab,” “Open in New Window” or “Open in Split View” options
within their app, evoking methods under the UIDocument subclass.

The UIWindow class would not support opening multiple windows

with the same UIDocument subclass object.

!19
Guide
Open the First or Most Recent App Window
To open the first or most recent app window:

1. Find the app icon on the Dock or the Home screen.

2. Tap the app icon.

Open the Window Manager

To open an app’s window manager to see all open
windows and tabs, and manage them:

1. Find the app icon on the Dock or the Home screen.

2. Touch and hold the app icon until the window manager
appears.

From the window manager, you can open a new window,

merge all windows, close all windows or manage a tabbed
view.

!20
Guide
Open a New App Window in Split View
To open a new app window in Split View:

1. Open an app.

2. Swipe up from the bottom of the screen to open

the Dock.

3. On the Dock, touch and hold the app of which you

want to open a new window.

4. Drag the app icon off the dock and over to the left
or right side of the window and release.

!21
Guide
Open an Existing App Window in Split View
To open an existing app window in Split View:

1. Open the first app from either Mission Control, the

Home screen or the Dock.

2. Swipe up from the bottom of the screen to open

the Dock.

3. On the Dock, touch and hold the app icon of the

desired app until the window manager appears.

4. In the window manager, touch and hold the app

window you wish to bring into the Split View.

5. Drag it over to the left or right of the main window

and release.

!22
Guide
Open a New Tab
To open a new tab in an existing app:

1. Open the app window to which you wish to add a tab.

2. Swipe up from the bottom of the screen to open the Dock.

3. On the Dock, touch and hold the app icon of the same app
that you already have open.

4. Drag the app icon over the app’s top title bar or tab bar
and release.

Note that document-based apps will require the user to

either create a new document or open an existing document
when a new tab is created.

Close a Tab
To close a specific app tab just tap the button on the tab
you wish to close.

!23
Guide
Merge Two App Windows Into a Tabbed Window
To merge two app windows into one window with tabs:

1. Open the app window to which you wish to add a tab.

2. Swipe up from the bottom of the screen to open the Dock.

3. On the Dock, touch and hold the app icon of the app that you
already have open until the window manager appears.

4. In the window manager, touch and hold the app window you wish
to make a tab.

5. Drag the app window over the current app window’s top title bar
or tab bar, and release.

Alternatively:

1. Open Mission Control or see all the app windows open.

2. Touch and hold the first window you wish to make a tab.

3. Drag it on top of the center of the second window you wish to

merge it with into tabs and release.

!24
Mouse & Trackpad Support

Give me your mouse, your

trackpad, your insertion points.
While touch would remain the primary mode of State of Affairs__________________________________26
interaction with iPad, padOS would offer support for Philosophy _____________________________________27
using a mouse or trackpad in select areas. So you Execution_______________________________________28
can move a text insertion point, select text, scroll, User Guide _____________________________________29
zoom, and even switch between apps and Mission
Control. All without lifting your hands from your desk.

!25
State of Affairs
Since the beginning, iPad has been a magical pane of glass that allows users to touch and
directly interact with their content offering the most versatile computing experience. As
iPad has evolved to handle more tasks for more people, its ability to be used in a vertical
position with the Smart Keyboard has become increasingly popular.

Working with a vertical touch display in this mode for prolonged periods when precision is
needed is ergonomically troublesome — requiring the user to move their hands up to the
display to engage with the content (usually text) that they’re working with.

While touch should never be replaced as the primary input method on iPad in any instance,
in some circumstances users might benefit from an additional, indirect input method that
allows them to interact with their content with precision without lifting their hands from
their desk and keyboard. The solution is a decades old one:

A pointer.

!26
 Philosophy
Implementing a pointing system — especially a point-
and-click system — that extends to every part of the iPad
user interface would go deeply against the very nature of
the iPad experience. So, while pointing devices may be
useful, the way they work should be fundamentally
altered for iPad, and their use should be limited to only a
handful instances.

Examples of these instances include when working with

active text fields, or views that allow for scrolling and
zooming, or with multitasking. The gestures that users
are already familiar with in iOS on iPad and even some
from macOS, should be extended to padOS both on-
display and through connected mice and trackpads.

!27
Execution
When a user interacts with a connected
mouse or trackpad, padOS will interpret
these inputs. If the input is recognized as a
system-wide gesture such as those for
switching between apps, going to the home
screen, or opening notification center,
padOS will enact the expected changes at a
system level.
If padOS detects any other type of input, it
will check for an object designated as a first
responder by the firstResponder() method.
If there is such an object and it supports
trackpad or mouse input, it will handle the
input appropriately for its view.

Objects that could initially accept input from
a trackpad or mouse would include those of
the following classes:
UITextField
UITextField objects accept movement of the
text insertion point, selection and a
secondary click.
UITextView
UITextView objects accept movement of the
text insertion point, selection and a
secondary click. They also accepts scrolling
and zooming assuming the appropriate
UIScrollView delegates have been inherited.
 use within applications. This includes
UIScrollView
UIScrollView objects accept scrolling and
zooming assuming the appropriate
UIScrollView delegates, and maximum and
minimum zoom scales are set.
SFSafariViewController & WKWebView
SFSafariViewController and WKWebView
objects accept scrolling and zooming based
on associated UIScrollView delegates.
UIGestureRecognizer
UIGestureRecognizer class objects will
recognize some input from a trackpad for
swiping left and right for navigating a view
hierarchy.
!28
User Guide
Move Your Text Insertion Point

Magic Mouse Magic Trackpad

Move your mouse. Touch and slide one finger
along the trackpad.
!29
User Guide
Select Your Text

Magic Mouse Magic Trackpad

Click your mouse and Click and slide one finger along
move it around. the trackpad.
!30
User Guide
Edit Your Text with the Edit Menu

Cut Copy Look Up Share…

Magic Mouse Magic Trackpad

Right click your mouse. Tap with two fingers on
your trackpad.
!31
User Guide
Scroll

Magic Mouse Magic Trackpad

Slide one finger up or Slide two fingers up or
down on your mouse. down on your trackpad.
!32
User Guide
Zoom In or Out

Magic Trackpad
Pinch in or out on your
trackpad to zoom in or out.
!33
User Guide
Open Notification Center

Magic Trackpad
Slide two fingers from the
top edge of your trackpad.
!34
User Guide
View the Slide Over App

Magic Trackpad
While in another app window, slide two
fingers from the right edge of your trackpad.
!35
User Guide
Move Between Apps

Magic Mouse Magic Trackpad

Swipe two fingers left or Swipe left or right with four
right over your mouse. fingers on your trackpad.
!36
User Guide
Open Mission Control

Magic Mouse Magic Trackpad

Double tap two fingers on Swipe four fingers up on
your mouse. your trackpad.
!37
 User Guide
Open App Exposé

Magic Trackpad
To see all the windows of your current app,
swipe four fingers down on your trackpad.
!38
 User Guide
Return to Your Home Screen

Magic Trackpad
To go to your Home screen, pinch closed
four fingers on your trackpad.
!39
Files

File Management 2.0.

External file storage support in the Files App would External File Storage Support __________________________41

allow users to move large files easily from one Philosophy __________________________________41
Arguments _________________________________42
device to another, and even make local backups.
Execution___________________________________43
And with iCloud Drive Sharing, collaborating with
iCloud Drive Sharing___________________________________44
others on shared files and folders would be easy.
Philosophy _________________________________44
Execution ___________________________________45

!40
External File Storage Support
Philosophy
With the introduction of USB-C on iPad Pro in 2018,
many were left wondering why external file storage
support wasn’t included. This is an especially
important feature for professionals and creatives who
need to transfer large files over to their local or
iCloud storage.

Adding the ability to work with USB-C file storage

options through the Files app would not only add
value to the new USB-C port, but it would also help
iPad work better in environments with a mix of
devices with different wireless transfer protocols.
Examples include colleges and businesses with users
who need better cross-platform compatibility.

!41
External File Storage Support
Arguments
Two potential arguments that need to be considered include:

Opening iPad up to external storage options may expose users to additional security risk. However, through

1 sandboxing and a lack of support for running apps from an external disk, file transfers can be handled safely
and securely much the same as how online file storage locations are already managed by the Files app.

Customers may view this feature as a reason to forgo larger storage options which offer higher profit margins.
However, not adding this feature for the sake of up-selling would be user-hostile and antithetical to Apple’s

2 values. For most, it probably wouldn’t reduce the value of larger internal and iCloud storage either given the
additional convenience these offer. In fact, iPad may become more like a digital hub for some users which will
make larger internal storage even more attractive.

!42
External File Storage Support
Execution

The elements needed to execute this feature are already mostly present. The
iOS Files app provides the perfect environment for handling external storage.
The deeply-ingrained sandboxing principles of iOS and the inability to run
from an external disk without importing first, ensure the integrity of the
security of iPad and padOS.

The necessary drivers and support for file formats such as exFAT and FAT32
are already built into macOS, and read-only support for NTFS is also
available. These could be ported to padOS much the same as how drivers for
microphones, keyboards, etc. have already made their way to iOS.

Finally, to help enable better workflows, developers should be able to access

external storage through the Files Browser available through the
UIDocumentBrowserViewController. This would also incite many app
developers to employ this controller and bring greater uniformity across apps.

!43
 iCloud Drive Sharing
Philosophy
In a world where inter-personal computing has become as important as
personal computing, teams in education and enterprise have come to
collaborate on their projects almost entirely through online sharing.
Currently, Google’s GSuite is the primary way teams accomplish this
giving Google a stronghold in both segments — especially education.
This is particularly concerning given Google’s reluctance to extend a
good experience with these services to iPad and iOS.

For iPad to be considered more thoroughly by these markets, a native,

secure file and folder sharing option should become standard. Folder
support is an important addition to existing functionality as many
projects involve many files of different types. This, coupled with
improvements to web-based iCloud apps, would make iCloud a viable
collaboration platform for not just iWork documents but for entire
folders of any type of file for users of platforms even outside of Apple’s.

!44
iCloud Drive Sharing
Execution
Currently, users can share any file with an iCloud link. With padOS and updates to iOS and
macOS, users would also be able to select any iCloud folder, and share it and all of its contents
through a single link.

When a user receives a shared iCloud Drive link, their Apple device would add the folder or file
to a location of the user’s choosing in their iCloud Drive through either the Files or Finder app.
This shared file or folder will sit alongside their own content but be designated as shared.

The file or folder will be hosted by the original sharer who can control access to it, including
designating read or write privileges. If the original sharer deletes the file or folder, they will be
able to transfer control or remove it entirely.

Developers will have access to new methods in the UIDocument class that will allow them to
add additional features for documents that are shared with iCloud. This would include live-
updating.

Each user who has access to the file or folder will be visible to others under the name they
choose for their iCloud account. If a link is sent to someone not on one of Apple’s platforms,
they will be able to sign up for a free iCloud account. They can then access it through
iCloud.com or their iCloud folder managed using iCloud for Windows.

!45
Multiple Users
Sharing the magic of iPad.
With support for multiple users, padOS would
allow customers to share their iPad with work
colleagues, family members or members of their
household. padOS would make the incredible
experience of iPad shareable.
Philosophy _____________________________________47
Execution ______________________________________48
Account Types ________________________48
Account States _______________________48
Security ______________________________49
Memory Control ______________________49
!46
Philosophy
iOS already supports multiple users for education customers with
education profiles. However, offering this feature to everyone using
padOS would have far-reaching benefits.

With such a strong reliance on iCloud, sharing iOS devices has become
increasingly difficult for families when individuals want to protect their
own private data. Having the ability to create multiple user accounts
would facilitate this sharing more easily and securely. The same would
be true for businesses who have iPad that are shared with multiple
employees who need different apps or who have different business
accounts.

An important argument against offering this feature is the potential

reduction in unit sales of iPad. However, allowing multiple users would
increase the trial-ability of iPad. Given the high customer satisfaction
for iPad, if more users are able to try iPad as part of a shared
experience, it is likely that purchase intent will increase. Furthermore,
better experiences for those looking for a household iPad or an iPad to
share amongst employees may result in expanded market
opportunities. Multiple user support will also incite purchase of higher
storage capacities.

!47
Execution
Account Types
User accounts would be managed through a new section in
Settings. Accounts can be designated as:
Administrator — able to make changes across the entire system
including to other user accounts, administrators can force users
to log out, can update the device, can share a data plan with other
users, and add or delete users. Administrators can also adjust
Screen Time and parental control settings for standard users.
Standard User — able to make changes to only their own
account, standard users cannot update padOS, change data plan
settings or edit other users.
Guest Account — an ephemeral account, guest accounts will lose
all data upon logging out. Administrators can choose which apps
to make available on the guest account based on what they have
already downloaded. Guest accounts cannot access Settings.
Account States
User accounts can exist in 4 states:
Logged Out — the user has not logged in, and their account has
not been loaded. This is equivalent to a single user having their
iPad turned off.
Logged In — once logged in, a user’s apps and services load
much like when a single user turns on their iPad.
Locked — when an account is locked but still logged into, apps
and notifications will continue to refresh in the background.
Depending on the user’s settings, notifications will be available on
their lock screen.
Unlocked — An unlocked account is an account that is logged in
and currently active.
!48
Execution
Security
Each user account is assigned a
unique key for the highest class of
Data Protection. These keys, held
in the Secure Enclave, are used to
unlock files and Keychain items for
each individual user. They are only
available to the system until the
user inputs their password. When a
device with Touch ID or Face ID
enabled locks, these keys are not
discarded but are wrapped with a
key that’s given to the Touch ID or
Face ID subsystem inside the
Secure Enclave. When these
systems detect a successful match,
they provide the key for
unwrapping the Data Protection
keys and the account is unlocked.
When a standard user account is
created, it is assigned a unique Data
Protection key in the Secure
Enclave. This key is then wrapped
with the keys that are assigned to
administrators’ accounts and
encrypted using their own Data
Protection key. These keys are not
lost at any time giving
administrators access to and control
over standard users’ accounts.
When a user logs in for the first time
with their password, the Secure
Enclave provides the Data
Protection Key. When the device
sleeps or the user locks their
account, this key is not lost but
wrapped with a key given to the
biometric authentication system.
This remains true if another user
logs in to their account. The
authentication subsystems can wrap
multiple keys.
If a user logs out, the Touch ID and
Face ID subsystems discard their
keys, requiring the user to log back
in with their password.
A passcode will be required for a
specific user if iPad is in any of the
following states:
• The user account hasn’t been
unlocked for more than 48
hours.
• The passcode hasn’t been used
to unlock the account in the last
156 hours and the account
hasn’t been unlocked by
biometric authentication in the
last four hours.
• After five unsuccessful biometric
match attempts.

A passcode will be required for all
users if iPad is in any of the
following states:
• The iPad has just been turned on
or restarted.
• The iPad has received a remote
lock command.
• After initiating power off/
Emergency SOS.
Memory Control
When an account is locked but still
logged in, and another user account
is logged into and unlocked, the
second user account will be loaded
into memory and the first account’s
state will be relegated to storage.
During times of low memory and
CPU use, the system will pull the
locked but logged in accounts’
states from storage and refresh for
notifications.
!49
Xcode for iPad Beta
Build the future. Anywhere.
The vitality of Apple’s app stores is made possible in
no small way by the incredibly user-friendly IDE:
Xcode. Enabling developers to build, test and deploy
remarkably powerful apps from their Mac, Xcode
has been an important part of the Mac story for over
a decade.
Now, it’s time for the same amazing capabilities of
Xcode to come to iPad. Effectively, this would make
software development for Apple’s platforms easier,
and more accessible to more people in more places.
The future is ready to be built. And with Xcode for
iPad and padOS, it would be built on iPad.
!50
Philosophy
For iPad to truly represent the future of personal computing, apps
used in this future on iPad and iPhone need to be buildable on iPad.
Xcode for iPad would enable existing developers to do this but it
would also spur millions more users (especially younger users) to
learn to code, build an app, and share it with the world.

Since 2016 when Swift Playgrounds was introduced, Apple has

slowly been developing a deeper understanding of how an IDE can
be reinvented for a touch display. UI innovations like QuickType for
code and Snippets show that there is a lot of potential for an IDE on
iPad to be even better than on Mac.

However, for Xcode for iPad to be truly powerful, developers should

be able to build, test, deploy and manage apps right from iPad
without needing to use Xcode on Mac.

!51
 Conclusion

The future of iPad.

In 2010, iPad was introduced as a magical pane of glass that could
become anything you needed it to be. Over the years, it has proven
to be more of a mirror reflecting the legacy of iPhone and iOS. With
padOS, iPad will redefine what we thought was possible with a
device that can go almost anywhere and be used by almost anyone.
Features like Mission Control, multiple app windows, additional file
management options and mouse & trackpad support will make it
possible to do more and do it more quickly than ever before. Multiple
user support will make iPad more accessible to more people. And
Xcode for iPad will liberate software development and signal a new
era for app developers.
padOS will not just be the future of iPad, it will redefine what we
expect from our computers.
!52