Indigo

Following people on both Bluesky and Mastodon carries a specific, low-grade tax. Many accounts worth following post the same thought to both networks, so anyone running two separate apps reads everything twice, checks two notification tabs and loses their place in two timelines. Indigo for Bluesky & Mastodon, from Aniline Applications Inc., exists to remove that tax. It pulls both networks into a single unified timeline, marks each post with a color cue for its source, and folds duplicate cross-posts into one.

The positioning is narrow and smart. A single-network client asks you to pick a side. Indigo’s pitch is that a social graph split across two decentralized services shouldn’t force that choice. That makes its target audience precise: people who live on both networks, often cross-post their own writing, and want one place to read, reply and check in.

Indigo runs on iPhone, iPad and Mac, and the App Store also lists Apple Vision compatibility. It requires iOS 26 or later. That hard floor frees the developer from legacy support, but it shuts out anyone on hardware that can’t update.

The business model is freemium with a firm line. Downloading and browsing cost nothing. Posting and interacting require the Ultraviolet tier, sold as a monthly subscription, an annual subscription or a one-time purchase, with a cheaper annual plan that covers a single service.

The App Store rating is 4.8 out of 5 from 185 ratings, a positive signal from a modest sample. The limits are covered below.

• Unified timeline: Bluesky and Mastodon posts in one feed, with color cues identifying which service each post comes from.
• Cross-post collapsing: When someone you follow posts the same content to both networks, Indigo shows it once.
• Dual-network composer: Publish to one or both services at once, with images, video, GIFs, alt text and mentions that work across networks.
• Cross-device sync: Accounts and scroll position sync between devices, so reading resumes at the last post.
• Thread-focused post view: Replies are grouped to make long conversations easier to follow.
• Unified notifications: Mentions, replies and quotes from both networks in a single view.
• Messaging: Bluesky direct messages are supported, and Mastodon private mentions get a conversation view.
• OAuth sign-in: Accounts connect through the networks’ standard authorization flow, not a password typed into the app.
• Ultraviolet tier: Monthly, annual or one-time purchase unlocks posting and interaction, plus a cheaper annual single-service plan.

The Merge and the Duplicate Problem

A merged timeline is easy to build badly. Interleave two feeds naively and the result is worse than two separate apps. Every cross-poster appears twice, and the timeline doubles in length without doubling in content. Indigo’s answer is duplicate collapsing: identical posts from the same person across both networks render as one. This is the feature that makes the concept viable.

The color cues do the other half of the work. In a feed drawn from two services with different cultures, reply etiquette and audiences, knowing where a post lives tells you who will see a reply and which norms apply. Encoding that in color, instead of stacking badges or labels on every post, keeps the signal ambient. It is legible at a glance and easy to ignore when it doesn’t matter.

Collapsing does create a tension that any merged client has to manage. Two copies of a post carry two reply threads, two sets of interactions and two audiences. Folding them into one is the right default for reading. How a client handles interaction with that merged post is where it earns or loses trust, and that is likely to be the area that sees the most refinement as Indigo matures.

Composing for Two Audiences

The composer publishes to one or both services in a single action. For anyone who already cross-posts by hand, that removes a copy-paste step from every post. Media support covers images, video and GIFs. Alt text is part of the package, which is non-negotiable for a client that serves Mastodon’s community, where described images carry real weight, and good practice on Bluesky too.

Cross-network mentions are the ambitious part. Bluesky and Mastodon identify people differently, so tagging someone on both from one draft means the client resolves identities the user would otherwise juggle manually. A unified client should absorb exactly this kind of drudgery.

Threads, Notifications and Messages

The thread-focused post view groups replies for easier reading. Conversation structure is the hardest thing for a social client to present well, because branching discussions tend to collapse into an undifferentiated list. Prioritizing grouping fits networks where long reply chains are often the main event.

Unified notifications gather mentions, replies and quotes from both networks. Like the timeline, this turns a two-place habit into one. For anyone who posts actively, it removes the most repetitive check in the two-app routine.

Messaging handles an asymmetry honestly. Bluesky direct messages are supported, while Mastodon private mentions get a dedicated conversation view. The two features are not the same thing on the underlying networks. Giving private mentions a chat-like shape makes them usable without pretending they are equivalent to DMs.

Continuity Across Devices

Accounts and scroll position sync across devices. For a reader who moves between iPhone and Mac through the day, landing on the last-read post separates actually catching up from skimming the top of the feed. That matters, because a sync feature that works most of the time is worse than none: it trains people to stop trusting it.

Where It Stops

Breadth across two networks costs depth on each. Power users of clients like Ivory may feel constrained by the breadth-first approach. That is a fair warning for anyone whose workflow depends on a specialist client’s full set of controls. The trade-off is structural: a merged client has more edge cases to manage than a single-network app, and Indigo’s direction is clearer than its finished depth.

The Ultraviolet Paywall

The free tier is read-only. You can browse, but posting and any interaction require Ultraviolet. For a social client, that makes the free version a demo in practice, and prospective users should treat it as one: a way to judge the merged timeline before paying.

The tier structure itself is fair. Offering a one-time purchase alongside monthly and annual plans respects people tired of stacking subscriptions. The cheaper single-service annual plan is an odd fit for an app whose premise is merging two networks. It does make sense as an on-ramp for someone active on one network today who expects to add the other later.

Indigo’s visual design rests on one strong idea: color as provenance. Assigning each network a visual identity lets a mixed feed stay readable without labeling every post. That information design is what keeps a two-source timeline from feeling chaotic.

The listing also promises a tailored design for each platform. Apple users notice quickly when an iPad app is a stretched phone layout or a Mac app is a thin port, so treating each device as its own design target is a sound priority for a client that leans this heavily on cross-device continuity.

On performance, a timeline of text and media is light work for current Apple hardware, and the iOS 26 floor rules out the oldest devices. Merging two feeds and matching duplicates does add client-side logic that a single-network app never runs. That kind of logic is where edge cases surface, so the app’s maturity matters.

Indigo is an Apple-only client, but it spans several form factors, and account and scroll-position sync ties them together.

• iPhone: Touch-first timeline reading and composing. This is the most likely primary device for a social client.
• iPad: A tailored layout on a larger canvas, which suits the thread-focused post view and long conversations.
• Mac: Pointer and keyboard input with its own tailored design. Position sync makes desk reading and phone reading one continuous session.
• Apple Vision: Compatibility is listed on the App Store. Treat it as a bonus, not a reason to buy.
• System requirement: iOS 26 or later, which excludes devices that can’t run it.
• Sign-in: OAuth for both networks.
• Pricing: The Ultraviolet tiers (monthly, annual, one-time, or single-service annual) gate posting and interaction on every platform.

Indigo solves a real, specific problem with focused design. Duplicate collapsing and position sync are the two features a merged client lives or dies on, and both are where Indigo puts its effort. The dual-network composer, unified notifications and honest handling of messaging asymmetry round out a coherent package. The App Store rating is 4.8 out of 5 from 185 ratings.

The limits are just as clear. Anything beyond reading sits behind Ultraviolet, depth trails dedicated single-network clients, and the merged-client model leaves edge cases to manage. We recommend Indigo to anyone already split between Bluesky and Mastodon on current Apple hardware, where the time saved on duplicate reading and double notification checks can justify the subscription or one-time purchase. Committed single-network users have little reason to switch.