Why Inkwell’s iOS Review Is Stalled: A Deep Dive into Apple’s Guideline Battles

![Featured image]()

Inkwell, the iOS client for the Micro.blog publishing platform, has been caught in a protracted App Store review loop since its first submission on April 21, 2026. The developer, Manton Reece, has iterated through multiple re‑submissions, phone calls, and even an appeal to the Review Board, yet the app is still marked Waiting for Review. Below is a systematic breakdown of the guideline sections that have triggered rejections, the concrete changes made to address them, and why one particular issue – a trademark conflict – continues to block progress.

---

1. Guideline 1.2 – Objectionable Content Controls

Problem: Apple flagged the app for lacking a way to report objectionable content or block users, even though Inkwell is fundamentally an RSS reader where users only follow public Micro.blog accounts.

Fix: Added a Report and Block option to the reply view, mirroring the functionality available on the web version. The welcome screen was also expanded with explicit Terms of Service and Privacy Policy links to satisfy Apple’s request for clearer legal disclosures.

Impact: The app now meets the minimum safety requirements for user‑generated content, but the change added visual clutter to the onboarding flow, a trade‑off the developer accepted to keep the review moving.

---

2. Guideline 2.1 – Sign‑in with Apple

a) 2.1(a) – Non‑functional Sign‑in Button

Problem: The Sign‑in with Apple button failed when the user attempted to authenticate from within Inkwell.

Fix: Identified a mis‑configured redirect URL and corrected it. To avoid future confusion, the button is now hidden when the user is already signed in through Inkwell or when syncing with third‑party clients such as Unread.

b) 2.1(b) – Revenue‑related Questions

Problem: Apple asked a series of questions about how the app generates revenue.

Fix: Provided detailed answers outlining that Inkwell does not host any in‑app purchases; it simply consumes the Micro.blog subscription that users pay for on the web. The response clarified that the app is a reader‑type client and does not take a cut of the service’s revenue.

---

3. Guideline 3.1 – In‑App Purchase Requirements

Problem: Apple argued that the app should use In‑App Purchase (IAP) to take a percentage of Micro.blog’s revenue.

Fix: Stripped all content‑creation features (posting, highlighting) and removed the sign‑up flow. The app now functions purely as a stand‑alone companion that displays content for existing Micro.blog accounts. It is also limited to the U.S. storefront temporarily to simplify compliance with the Epic vs Apple settlement rules.

Result: The app now falls under either 3.1.3(a) – Reader apps or 3.1.3(f) – Stand‑alone companion apps, both of which are exempt from IAP.

---

4. Guideline 4 – Design and Sign‑in with Apple UI

Problem: Reviewers noted that the Sign‑in with Apple flow still prompted for a user’s name, which contradicts Apple’s UI guidelines.

Fix: Updated the authentication UI to suppress the name request when the user’s Apple ID already supplies it. Eventually, the entire Sign‑in with Apple option was disabled in the app to avoid further design complaints.

---

5. Guideline 5 – Account Management

5.1.1(v) – No Delete Account Option

Problem: Apple required a way for users to delete their Micro.blog account from within the app.

Fix: Added a Delete Account button in the Settings screen that triggers the same API call used on the web. The button includes a confirmation dialog to prevent accidental deletions.

5.2.5 – Trademark Conflict

Problem: The name Inkwell appears on Apple’s own trademark database, originally used for a handwriting‑recognition feature in Mac OS X 10.2. Although the trademark is listed as “dead” by the USPTO, Apple’s internal list still flags it, leading to repeated rejections.

Attempts to Resolve:

• Renamed the app in the App Store metadata to de‑emphasize the word “Inkwell.”
• Submitted an appeal to the Review Board, arguing that the trademark is inactive and that dozens of unrelated apps already use the same name.
• Highlighted that the Android version, already approved by Google, uses the identical branding without issue.

Current Status: The appeal is pending. Apple has not provided a definitive timeline, and the reviewer continues to reject the submission on this point alone.

---

6. The Bigger Picture: Why This Matters

The Inkwell saga illustrates how incremental compliance can still be derailed by a single, arguably outdated, policy enforcement. While the developer has addressed every technical and design concern raised by Apple, the trademark flag remains a non‑technical roadblock that cannot be solved with code changes alone.

For other indie developers, the takeaways are clear:

1. Document every change and keep a detailed changelog for reviewers. Apple’s feedback often references specific UI elements; a precise response can shorten the loop.
2. Prepare a fallback branding strategy early. If a name is on Apple’s internal watchlist, having an alternative ready can prevent months of delay.
3. Leverage the appeal process but be realistic about timelines. Apple’s Review Board can take weeks to respond, and the outcome is not guaranteed.

---

7. What’s Next for Inkwell?

Manton plans to keep the app US‑only for now, a tactical move to satisfy the reviewer while the trademark dispute is resolved. Once cleared, the app can be expanded globally without further changes, as the underlying compliance work is already in place.

In the meantime, the developer continues to gather user feedback via TestFlight and will monitor any updates from Apple’s Review Board. The community can help by:

• Sharing any similar experiences with trademark rejections.
• Offering suggestions for a quick re‑branding path that preserves the app’s identity.
• Reporting any new Apple guideline updates that might affect reader‑type apps.

---

Bottom line: Inkwell is technically ready for the App Store; the lingering trademark issue is the sole obstacle. Until Apple either clears the name or the developer opts for a new brand, the app will remain in review limbo.