u/FoShr

I've got a daily-reader app that uses a page-curl transition between articles, and it works great in light mode. The problem is dark mode: when a page curls, the underside / opposite face of the curling leaf still renders bright, so you get this glaring light triangle peeling across an otherwise dark screen. The front faces respect dark mode fine — it's specifically the back of the curl that doesn't.

Setup: SwiftUI app, the curl itself is [UIPageViewController with .pageCurl transitionStyle, bridged via UIViewControllerRepresentable / your actual setup]. Each page is a SwiftUI view hosted in a UIHostingController.

What I've tried so far:

• [e.g. setting the hosting controller's view.backgroundColor to a dark color]
• [e.g. forcing .overrideUserInterfaceStyle = .dark]
• [e.g. setting isDoubleSided / tinting the page view controller's view]

…but the curl's reverse face still comes out light. Short clip of the effect attached.

Is the underside something UIKit renders from the page's own backing, or is there a separate layer/material I can get at to tint it? Is .pageCurl even the right tool here, or do people drop down to a custom Metal/shader curl to get full control over both faces in dark mode? Open to either answer.

I run a companion website for a content app that's on testflight right now, and I want the web article to show only an opening teaser, then push readers into the app for the rest. The tension is ranking: a teaser-only page is thin and won't rank for the body.

Here's the actual page I'm testing it on: https://www.theuncdaily.com/articles/the-menacing-folklore-of-the-digital-log — the full article is in the HTML, but it's visually capped with a max-height and a fade overlay, so a reader only sees the first chunk before a "read the rest in the app" prompt.

What I can't get a straight answer on:

1. Since the full text is in the DOM, will Google index and rank it normally, or does it discount the visually-hidden portion? And is this a cloaking problem, given the user sees less than Googlebot does?
2. Would I be safer shipping only the teaser and accepting I rank for less?
3. Does the paywalled-content structured data (isAccessibleForFree: false + hasPart/cssSelector) apply here, even though it's an "app gate" rather than a paywall?

If you load the page, does anything look like it'd trip a cloaking or thin-content flag? Genuinely after a teardown.

I'm building a content app (a satirical daily newspaper), and content apps have an obvious discovery problem: Google can't crawl what's inside an app, so all of that daily content is invisible to search. Here's the setup I put together to fix that and turn web visitors into app users. Sharing in case it's useful, and I'd like to hear how others handle it.

The web layer

I built a companion website that mirrors each day's article at its own URL. The decisions that mattered for SEO:

• Keyword-rich slug URLs (/articles/why-everyone-says-rizz) instead of IDs or dates, so the URL itself carries search terms.
• Each article page ships the full text in the HTML for crawlers, plus NewsArticle structured data (JSON-LD), canonical tags, an auto-generated sitemap, and per-article Open Graph images so shared links look good.
• Pages regenerate on a schedule, so new editions get indexed without a rebuild.

The conversion hook

This is the part that does the redirecting. The full article is in the HTML so Google sees all of it, but on screen it's visually truncated into a teaser that fades out, with a "read the rest in the app" prompt and a download button underneath. Search and social bring people in, the teaser hooks them, and the CTA pushes the install.

Universal Links

This is what makes the hand-off seamless. With an Apple App Site Association file and the Associated Domains entitlement, any theuncdaily.com/articles/... link opens the app directly to that exact edition if the app is installed. If it isn't, the same link just loads the web page, which is already set up to convert. One link does both jobs depending on the user.

The loop

The app's share button shares the web link rather than a screenshot, so every time someone shares an article, the recipient gets a rich preview, lands on an indexable page, and either deep-links into the app or gets funneled to install it. User sharing feeds both traffic and SEO signals.

It's early, so I don't have real numbers to report yet. But the architecture is: web for discovery, Universal Links for a seamless hand-off, and a teaser-plus-CTA to convert.

How do the rest of you handle the "app content is invisible to search" problem? Do you mirror content to the web, or lean entirely on ASO and paid?