Mignori is getting very close to release.

In our May development update, we mentioned that we were waiting for WWDC before making final release decisions. After evaluating the current state of the app and the platform direction, the decision has been made: Mignori will target iOS 26 devices instead of waiting for iOS 27.

Even if iOS 27 were to be released before Mignori ships, iOS 26 may still remain supported. That is not a final promise yet, but it is the direction we are currently leaning toward. We do not want to hold the app back longer than necessary if the current iOS 26 foundation already supports the experience Mignori needs.

iCloud Sync Update

The other major update is about iCloud Sync.

Over the past several weeks, we have done a lot of testing around iCloud sync and the underlying CloudKit infrastructure. The conclusion is that CloudKit is too strict for the kind of library Mignori manages, especially when dealing with large local collections.

CloudKit can work very well when an app’s data model fits its expectations. Mignori’s library system is more complicated than that. It has local files, metadata, tags, albums, collection state, derived indexes, and potentially very large libraries. Getting all of that to sync reliably across devices introduces too many edge cases.

The biggest concern is quality. We are not willing to ship a sync feature that creates strange bugs, duplicate records, inconsistent libraries, or, in the worst cases, data loss. iCloud’s limitations are not a good fit for Mignori’s library model right now, and continuing to force the feature in that direction would put user data at risk.

Mignori Library Files

We know many people want to use their Mignori libraries across more than one device. That need is real, and we are not ignoring it.

Instead of relying on iCloud Sync, we are now considering portable Mignori library files.

The idea is that your library could live in a file you control. You could store it on your computer, back it up manually, move it between devices, and open it in Mignori from any of your devices.

If you want to keep your Mignori library in a folder managed by a cloud storage provider, you can. If you prefer keeping everything only on local storage, you can do that too. We consider Mignori a good fit for power users, and we want to give those users control over where their libraries live and how they are backed up.

This approach is more manual than automatic iCloud Sync, but it gives users clearer ownership over their data and avoids the hidden sync behavior that has made CloudKit so difficult for this app.

We understand this may be disappointing if you were hoping for automatic iCloud syncing at launch. It is disappointing for us too. But Mignori is a library app, and library integrity matters more than checking a feature box.

We would rather ship a reliable app with a more explicit library workflow than compromise quality trying to make iCloud behave in ways it was not designed for.

Core Functionality Is Complete

The important thing to understand is that Mignori’s core functionality is complete.

People can browse multiple booru websites, search across supported services, save posts, organize collections, manage tag libraries, export content, and rediscover their local libraries. Collections are working well, tag libraries exist, and the app is as complete as it reasonably can be for its first public release.

The iCloud Sync versus library files decision is one of the final major decisions we need to make before launch. It is not a sign that the rest of the app is still far away.

We are also aware of some iOS 27 issues reported by testers, and we are working through the final bugs and compatibility problems now.

What This Means for Release

This change does not mean Mignori is moving further away from launch. If anything, it makes the release path clearer.

By moving away from iCloud Sync as a launch requirement, we can focus on the parts of Mignori that are already working well: browsing, saving, organizing, searching, exporting, and rediscovering your local library.

Mignori is close. The remaining work is about making sure the first public release is stable, understandable, and respectful of the data users trust it with.