Apple Rejected My iPhone Duo App. Here’s What I Built.
Handing someone your phone should be a small thing. You want to show them the screen, let them try the camera, or give them a turn with something new. You probably don’t want that invitation to include your personal photos, messages, and accounts.
That gap is why I started building Duo Demo.
The idea was a space where friends and family could try things using sample content instead of opening my everyday apps. I wanted the experience to feel familiar and make good use of the Duo’s changing screen layouts.
We built it, tested it through TestFlight, and submitted it to Apple. The original version didn’t get approved.
This is the story of what it did, why Apple rejected it, and the useful idea I’m trying to preserve.
Screenshots in this post show the original Duo Demo build 6 in the iOS simulator on October 10, 2026. They show screens inside our app, not the iOS Home Screen or photos of a physical Duo.
Watch Duo Demo in action
I recorded these short walkthroughs on October 17, 2026, using the preserved original Duo Demo build 6 in the Device Hub iPhone Duo simulator. These silent clips show the original app running in the simulator. Press play to watch.
Explore the unfolded photo library
From Duo Demo’s home screen, I open the included landscape photo library, view a picture, and return home. The photos are sample content inside the app, separate from the owner’s personal library.
Put Arcade and Notes side by side
I turn cards in the memory game, open the companion activity menu, and bring up Notes alongside Arcade. The two activities share the larger layout, with a fictional “Rooftop game night” note on one side.
Prepare a handoff on the outer display
On the smaller outer layout, I open the handoff guide from Duo Demo’s home screen, show its preparation instructions, and return home. This clip shows the guide, not actual iOS Guided Access activation.
A phone to explore, without opening my personal apps
Think about what happens when somebody asks to try your phone. They might want to see how the larger layout works, take a picture, or browse around. Showing one feature is easy enough. Letting them explore freely is a different proposition.
Duo Demo was my attempt to give that curiosity somewhere to go.
It included fictional contacts, conversations, calendars, reminders, and other sample experiences. Those weren’t windows into the owner’s real records. The message replies were local simulations; they weren’t texts being sent to actual people.
There were also things to do: write a note, play a memory game, listen to original instrumental music, browse included landscape photos, or use the real camera. Web browsing used a temporary session separate from Safari and could be switched off for an offline handoff.
I wanted enough interaction to make repeat handoffs useful: a place to try the device, do something, and reset it for the next person.
What the privacy idea actually meant
There’s an important limit here: Duo Demo was not an iOS guest account. Installing it didn’t lock the rest of the phone or create a separate operating system profile.
The owner needed to set up and start iOS Guided Access, Apple’s feature for keeping a device in one app. Duo Demo’s handoff page explained that step and showed whether Guided Access was active. iOS controlled the restrictions and passcode.
Inside the app, the separation came from using fictional content and keeping guest activity apart from the owner’s ordinary apps. The camera could take real photos and videos, but it didn’t browse the owner’s existing photo library. Captures were stored inside the app. With Add Photos permission, real photos and videos were also saved to the iPhone photo library; Reset removed only the app’s copies.
Resetting the demo session cleared app-local captures and temporary browsing sessions and restored sample content. It couldn’t pull back a photo already saved elsewhere, or erase information somebody had submitted to a website. An offline handoff also required turning live browsing off after Reset, which re-enabled it in this original version. Ending Guided Access was also a separate action controlled by the owner.
Those boundaries matter. The promise I wanted to make was a more controlled handoff, with clear instructions about how it worked.
TestFlight made the rough edges obvious
Getting the app onto a real phone was a turning point. I was able to install it through TestFlight and start trying the things a guest would try.
The camera quickly exposed a problem: the experience leaned on the front camera when it needed a proper choice of cameras. We revised it to start with the rear camera and added front/back switching, available rear lens choices, zoom, tap-to-focus, flash controls, and a clearer video recording flow.
There was less visible work, too: checking what Reset actually removed, keeping old camera results from returning after a reset, and clearing browsing across open panes. A handoff app needs to finish cleaning up, not merely make the screen look fresh.
We also replaced bundled Apple-sourced media and downloaded icons with original work or material with documented licensing. That included original music and short films, plus landscape images with recorded sources. Preparing for review meant taking responsibility for the content as well as the code.
What Apple actually said
The first review response, on October 8, asked for more information under Guideline 2.1. Apple wanted a recording from a physical device, an explanation of the app’s purpose and main flows, and information about services and content rights. That message was an information request, not a reported crash.
We supplied recordings and explanations. After reviewing the resubmission, Apple rejected version 1.0, build 6 on October 15 for two specific reasons.
Under Guideline 2.2, Apple classified it as “a demonstration app for iPhone Duo.” The reviewer asked for an app and listing that delivered a complete experience appropriate for public distribution, pointing to TestFlight for demonstrations and unfinished concepts.
Under Guideline 5.2.5, the reviewer objected to “Terms for Duo in the app name in an inappropriate manner.” Apple asked us to remove metadata that could cause confusion with its products or services.
That is what the rejection said. It wasn’t a statement that privacy tools or guest-sharing utilities could never belong on the App Store.
The gap between my intention and the presentation
I still think the handoff problem is real. But my intention and the app’s presentation weren’t quite aligned.
The original home screen, fictional system-style experiences, device-specific name, and listing all leaned toward showing off a phone. From that angle, Apple’s description of it as a demonstration app is understandable, even though I wanted people to use it repeatedly as a utility.
Calling it “Demo” didn’t help explain that distinction.
The planned price was $2.99 upfront, without subscriptions or in-app purchases. That was the intended model, not a product that had launched or generated App Store sales. This version has not been released on the App Store.
What could have been—and what comes next
Had Duo Demo been approved, I hoped it would become the app you opened before saying, “Here, try it.” A camera, some notes, a game, and content to explore could give someone a useful turn with your device while your regular apps stayed outside the experience.
That possibility is still what interests me.
We’ve preserved the original project and are rebuilding around the practical guest activities under a different name: Guest Session. The direction is a clearer dashboard, real tools, an obvious way to clear guest content, and honest guidance about Guided Access. It’s a product change as well as a name change.
That work is ongoing. Guest Session has not been approved, and I can’t promise that it will be. I can show what we built, explain what the review taught us, and make the next version better focused on the job I wanted it to do in the first place.
If you could give someone a temporary guest space on your phone, what would you want them to be able to do?
