Drafts get cleaned up between classes, on the train, in bed at 11pm. TextSight on a phone runs in three honest shapes: the responsive web app at app.textsight.ai works in iOS Safari, iOS Chrome, Android Chrome, and Samsung Internet today; the Android native app is live on Google Play (v1.0 on Internal testing, v1.0.2 polish build ready as a signed AAB) with scan, rewrite, and the system share sheet against the same backend the web uses; the iOS native app is on the 2026 roadmap and has not started development yet. No waitlist, no email gate. This page covers what works on a phone today and what is honestly not ready.
There is one Authenticity Score, one quota, and one account no matter which surface a user opens. The three mobile entry points are different shells around the same AI rewriter.
The web app at app.textsight.ai is the same React build that runs on desktop. The layout collapses cleanly under 768px, the editor takes the full width, the sidebar tucks into a slide-out, the result panel stacks under the input. iOS Safari, iOS Chrome, Android Chrome, Samsung Internet, and Firefox for Android all render the same UI. Paste from the standard iOS or Gboard keyboard works without permission prompts. This is the universal path and covers every phone in service today.
The Android app is live on Google Play under the Internal testing track. Version 1.0 (versionCode 1) shipped to invited testers, and the v1.0.2 polish build is ready as a signed AAB with onboarding redesign, the tool family, the result hero family, and the latest five QA fixes baked in. Scan, rewrite in three modes, sentence highlights, recent scans per account, and the system share sheet are all wired to the same backend the web app uses. Production roll-out is gated on screenshots, the feature graphic, and the remaining Play Console forms; the build itself is not the blocker.
There is no TextSight app on the App Store. The iOS native build is on the 2026 roadmap and has not started development. The honest framing matters because most search results on "ai rewriter iphone app" silently bury this. The web app on iOS Safari covers the full rewrite, detect, history sync, and copy workflow at parity with Android, and Apple supports Add-to-Home-Screen for a chrome-less full-screen window that behaves like a native app. No waitlist, no email collected, no gate. iOS development starts after the Android production listing settles.
The Android app is the most-shipped surface after the web. Both versions are the same backend; v1.0.2 is mostly UI polish and QA fixes rather than new flows.
Scan with a paste editor and a document picker, up to 5,000 characters per call on free and 50,000 per day on Pro. The score read-out with five colour-coded bands. Sentence highlights in a scrollable list. Rewrite in Light, Balanced, and Maximum modes. Recent scans saved per account. The system share sheet wired as both sender and receiver. Stub auth during the bridge phase; Google Sign-In and email sign-in come before the public listing.
Onboarding redesign that ports the four-step welcome flow from the web. A tool family screen that groups scan, rewrite, paraphrase, summarize, plagiarism risk, and grammar check into one launcher. A result hero family that reuses the same Authenticity Score header pattern across every output screen. Five QA fixes from the round-four review covering keyboard handling, score-band contrast, share-target preview, deep-link state, and remembered mode preference. No new endpoints, no new permissions.
Voice input through the standard Android speech intent. Offline scan cache for the last ten results. Share-to-image for the score card. Full Material You dynamic colour where the app picks up the user's wallpaper-derived palette. None of these are blockers for the production listing; they wait until D-U-N-S finishes and v1.0.2 ships.
No Play Billing during the developer-verification bridge, because the bridge does not satisfy Play Billing's verified-account requirement. Subscriptions are taken on the web at app.textsight.ai through Stripe and the entitlement carries to the Android build at sign-in. No on-device model; the AI rewriter compute stays server-side on every platform. No ad surfaces, no analytics SDK beyond Firebase Crashlytics for crash triage.
One account, one quota, one plan across mobile web, the Android app, and desktop. No platform surcharge, no app-store-only tier, no Pro-on-mobile-only feature.
Billed $89.88/year — Save $30
Billed $179.88/year — Save $60
Billed $359.88/year — Save $120
Yearly billing saves 25%. View full pricing →
The single best thing the Android app adds over the mobile web is integration with the system share sheet. Any app that exposes ACTION_SEND becomes an AI rewriter source.
Highlight a suspicious passage inside Chrome, Gmail, Docs, Slack, WhatsApp, Notion, or any app on the phone. Hit Share. TextSight appears in the target list. The selected text lands prefilled in the AI rewriter screen with the mode picker visible and the score from a quick scan rendered above it. Pick Light, Balanced, or Maximum, wait roughly fifteen seconds, copy or share the rewritten output back out without leaving the original conversation. Total time is around fifteen seconds for a paragraph.
From a result inside TextSight, tap the share icon and pick a target. The rewritten text gets passed to the receiving app through the standard intent, which means Gmail, WhatsApp, X, LinkedIn, Slack, Google Keep, Notion, or any LMS app on the phone all just work. No clipboard step, no app-switching, no formatting loss.
On a laptop, switching tabs to rewrite is annoying but cheap. On a phone, switching apps loses the keyboard, often loses the cursor position, and sometimes loses the draft. The share sheet collapses the whole loop into a single tap-tap-tap. Heavy users on the internal-test build report the share workflow is the main reason they use the Android app over the mobile web.
A phone is not a small laptop. Some AI rewriter workflows are actually faster on the phone than on a desk, and these are the four that come up most.
An essay drafted on a laptop the night before needs one AI rewriter pass before a 9am submission. On the bus ride in, open the Android app, paste the draft from the team chat, scan to see which paragraphs flag red, rewrite only those two in Balanced mode, share the cleaned version straight into Google Classroom or the LMS. The whole loop fits inside fifteen minutes.
A client email needs a softer tone before the 10am meeting. On the train, open the mobile web in iOS Safari or the Android app, paste the GPT draft from the team chat, pick Balanced, copy the cleaner version into a reply, send. No laptop, no Wi-Fi gymnastics. The result panel stacks under the input so reading on a phone screen is comfortable.
A blog draft outline sits in Notion mobile. Pull up the offending paragraph, share to TextSight, rewrite in Maximum mode, share the result back into Notion. Total interruption is under two minutes. The share sheet pattern means the writer never leaves the Notion context for more than two screens.
An investor update written in Apple Notes needs a less-corporate tone before the next call. Copy the text on iPhone, open app.textsight.ai in Safari (no install needed), paste, rewrite in Balanced, copy back, paste into the email. Add-to-Home-Screen makes the second pass faster the next time.
Most users do not need a native app. The web app on phone browsers covers rewrite, detect, history sync, paste, and copy at parity with native, and skips the install step entirely.
iOS Safari is the canonical iPhone path. The web app handles the editor cleanly, paste from the standard iOS keyboard works, copy uses the navigator.clipboard API with no permission prompt, and the result panel adapts to the safe-area inset on notched and dynamic-island devices. iOS Chrome is a WebKit shell under the hood, so behaviour is identical. Add to Home Screen gives a dedicated icon and a chrome-less full-screen window that behaves close to a native app.
Android browsers all work, and the web app installs as a Progressive Web App from the three-dot menu in Chrome and Edge with a home-screen icon. The Android native app is still the right pick if the share workflow matters, but the mobile web is the right pick if the user wants zero install friction and is fine with copy-paste between apps.
The compute happens on the server in every case. A rewrite call from iOS Safari hits the same endpoint, runs against the same model, and returns the same Authenticity Score as a rewrite call from the Android app or from a desktop laptop. The only thing native adds is OS integration (share sheet, deep links, system tray), not throughput or quality.
No system share-sheet integration; the user has to copy and paste between apps. No background processing if the screen sleeps mid-call; the call resumes on wake. No offline mode at all (this is true on every surface). File upload works on phone but the picker UI is rougher than on desktop. None of these block normal use; they are listed because most marketing pages quietly skip them.
Browser-based AI rewriter that runs on every phone, tablet, and laptop without install.
Open the online guide →Web, extension, and WordPress plugin coverage for Mac, Windows, Linux desktop workflows.
See the desktop story →Where the in-page extension stands today and the share-equivalent for desktop browsers.
Read the extension status →The main landing page covering every source model and all three rewrite modes.
Open the overview →Mobile web on iOS Safari and Android Chrome covers everyone today. The Android app is on Play Store for testers and the v1.0.2 polish build is ready. iOS is on the 2026 roadmap; no waitlist, no email collected.