Readable in one screen · decide continue or stop first
ConceptBrim – Use the iPhone Duo's whole outer display in Safari
When you unfold your iPhone Duo, why does Safari still act l
Author · MicroValidatorLast updatedWho this is for Early adopters who own or expect to own a dual-display/foldable iPhone and use S
Core takeaway / TL;DR
Run the one-week landing page + interview experiment first; do not build the ful
Suggested next step Publish a minimal landing page with a screencast and a $4 be
Run the one-week landing page + interview experiment first; do not build the ful
Next experiment
Publish a minimal landing page with a screencast and a $4 be
Best thing to validate
If the outer-display Safari problem is real, a tiny extension can become a defau
Biggest risk
The iPhone Duo may not exist as a shipping device, or Apple's extension APIs may
Critical assumption (summary)
There is a real, recurring Safari outer-display problem on a device that enough people own or will own.
Show objections and continue/stop
Strongest objection
The iPhone Duo may not be a real shipping device, and 'nothing exists' for it may simply mean no one has the problem.
Continue if
If at least 3 of 10 interviews show a concrete workaround and a willingness to pay $4–$6, build the minimal extension an
Pivot if
If interviews show no one can demonstrate the problem or everyone says they would use a free alternative, stop and pivot
Show score rationale
The phrase suggests a desire to use the full outer display for Safari, which may indicate a pain point around wasted screen space.,The product name 'Brim' implies a border/fill metaphor, but no functional details are known.
Fill the critical gaps (max 2)
“I don’t know” is fine — we give how to get evidence; we never invent interviews or payments.
02 Where the signal came from
Raw keyword
Brim – Use the iPhone Duo's whole outer display in Safari
Is anyone searching? Relative interest — not monthly volume.
Trends 0–100 is relative interest, not monthly volume; 0 ≠ no demand.
Trends unchecked
Live search interest not checked yet. Conclusions below are hypotheses pending validation.
04 Business breakdown
Who needs this
Early adopters who own or expect to own a dual-display/foldable iPhone and use Safari as their primary mobile browser.
Job to be done
When the phone is unfolded, make Safari render across the entire outer display so reading and web apps do not require zooming or scrolling inside a narrow column.
Why they might pay
They save a few seconds every time they open Safari and avoid the mental overhead of switching to a different browser or using a bookmarklet.
Alternatives
Switch to a third-party browser, use Reader Mode, request desktop site, rotate the device, or manually zoom.
Differentiation wedge
A Safari extension that injects a viewport meta tag and CSS to force full-bleed rendering on the outer display; no account, no cloud sync, no settings.
OPC scope
Safari extension that injects a viewport meta and CSS; no backend, no accounts, no cloud.
Open questions
Does the iPhone Duo's outer display have a Safari viewport bug that is actually fixable by an extension?
Will Apple allow an extension to override the viewport on the outer display?
Is the pain frequent enough to justify a paid extension?
Valid signal = real task completion, reuse, or pay intent — with observe + continue/stop.
01
Create a one-page landing site with a 90-second screencast showing the Brim extension on a simulated iPhone Duo outer display, plus a signup form and a $4 'pay for beta' button.
Observe
Number of visitors, signups, and clicks on the paid button.
Continue
At least 20 visitors and at least 5 signups, with at least 1 paid click.
Stop
Fewer than 10 visitors or 0 signups after the week.
02
Post the landing page to Hacker News and two relevant communities (r/iPhone, r/foldables) with a title focused on the problem, not the product.
Observe
Comments, upvotes, and whether people describe the same Safari outer-display pain.
Continue
At least 5 commenters describe the same problem or ask for a beta.
Stop
Comments are mostly 'this device doesn't exist' or 'just use another browser'.
03
Run 5 short interviews with people who sign up, asking them to screen-record how they currently use Safari on a foldable/dual-display phone.
Observe
Whether they can show a concrete workaround and whether they mention the pain unprompted.
Continue
At least 3 of 5 show a recurring workaround and say they would pay $4.
Stop
None can show the problem or all say they would not pay.
04
Build a minimal Safari extension that only injects a viewport meta and CSS on the outer display; install it on your own device/simulator and record before/after.
Observe
Whether the extension actually changes the rendering and how much friction it takes to install.
Continue
The extension works on the target device and install takes under 5 minutes.
Stop
The extension cannot override Safari's viewport or requires private API access.
05
Send a follow-up to signups with a 'pay $4 for the beta' link and ask for a one-line reason if they decline.
Observe
Conversion from signup to paid and the stated reason for declining.
Continue
At least 2 people pay or 5 say they would pay after the beta works.
Stop
No one pays and no one gives a specific pain statement.
FAQ
Should I keep building this idea?
Run the one-week landing page + interview experiment first; do not build the ful
What is the smallest next experiment?
Publish a minimal landing page with a screencast and a $4 be
What is the biggest risk right now?
The iPhone Duo may not exist as a shipping device, or Apple's extension APIs may
Who is this validation for?
Early adopters who own or expect to own a dual-display/foldable iPhone and use Safari as their primary mobile browser.
How should I read the score?
Current OPC feasibility score is 35/100. It is an AI-assisted executability check, not a market guarantee. Low scores mean “prove demand first,” not “never build.”
07 Evidence & boundaries
Demand evidence summary
No traceable demand evidence beyond the HN submission title. The next step is to test whether the specific Safari outer-display problem exists on a real device
External record
A Hacker News submission title mentions Brim as a way to use the iPhone Duo's whole outer display in Safari. · Source: User-provided Hacker News submission title · not provided · Supports: interest
User-stated
The user provided only the keyword: 'Brim – Use the iPhone Duo's whole outer display in Safari'.
Model hypothesis
If a Safari extension can make Safari render across the full outer display, early adopters with dual-display iPhones may use it daily and pay a small one-time fee.
The pain may be strongest for people who read long articles or use web apps on a foldable device.
Known facts
The user provided only the keyword 'Brim – Use the iPhone Duo's whole outer display in Safari'.
The user-provided keyword is presented as a Hacker News submission title.
No live Trends, interview, or payment data was supplied for this run.
Unverified assumptions
The 'iPhone Duo' refers to a dual-display/foldable iPhone concept with an outer display.
Safari on that device may currently render a narrow or letterboxed viewport.
A Safari extension can inject CSS/viewport changes on the outer display.
AI inference: The phrase suggests a desire to use the full outer display for Safari, which may indicate a pain point around wasted screen space.,The product name 'Brim' implies a border/fill metaphor, but no functional details are known.
Share the judgment08 Share
Tap an icon for poster, caption, and link.
Tap a platform: poster + caption + report link.
Share to
microvalidatorIdea validation card
Feasibility draft
Opportunity
Risk
Next
Would you pay for this?
Advanced: one-click frontend skeleton
Turn this idea into a single-file HTML MVP (Tailwind CDN + core interaction mock).