Passa al contenuto principale

Open Manuscript Studio — Current Implementation Status

Microsoft Store distribution update — 10 November 2026: Microsoft notified the publisher that the Open Manuscript Studio submission was processed and available in the Store, with up to two hours for customer visibility. The IARC questionnaire ratings are also reported live. The specific Store product link, signed-package verification, actual Windows Store install/update and data preservation remain pending. Direct Windows EXE/MSI downloads are a separate unsigned channel; stable 1.0 has not been approved. See Code Signing Policy and RC status.

4 November 2026 — Web and Android RC available. Web Studio and the direct-install Android APK use 1.0.0-rc.1. Open Web Studio or download the Android RC package. Desktop downloads remain 0.3.0-beta.13; Linux native and macOS are Preview, iOS/iPadOS Experimental. See RC1 availability and changes.

Snapshot​

FieldValue
StatusWeb and Android RC; desktop beta/Preview
Snapshot date2026-11-04
Staged development source candidate1.0.0-rc.1 (Web and Android RC; desktop acceptance separate)
Last documented public beta0.3.0-beta.13
Reference implementationOpen Manuscript Studio
Source repositoryopen-manuscript-initiative/open-manuscript-studio
Web targetModern browsers
Desktop targetsWindows x64, Linux x64, macOS Intel, macOS Apple Silicon
Mobile targetsAndroid public universal APK; iOS/iPadOS validated native simulator target, with TestFlight/App Store distribution pending Apple Developer signing
Web deploymentstudio.openmanuscript.org

Web Studio and the Android APK are 1.0.0-rc.1. Desktop public downloads remain 0.3.0-beta.13. See RC availability and installation and desktop beta.13 notes. The portable manuscript format remains OMI-SPEC-320@0.3.0.

Recent source changes (1 November 2026; not a new release)​

Studio PRs #802, #804, #805 and #806 are merged. Together they add PDF asset preflight diagnostics, verified missing-media recovery, cloud-package upload/download integrity checks and a compact mobile multi-document tab strip. The last #805 and #806 development commits passed the required CI, CodeQL, iOS simulator and 1.0 readiness checks.

An author also successfully opened a cloud-saved manuscript on another device. This verifies manual cloud package portability, not transparent background synchronization of every local image. Automatic server-side binary asset storage remains under #803. The six Dependabot alerts visible during the November review require a fresh dependency-graph assessment; they have not been treated as closed.

Read the 1 November development update for evidence, limitations and next steps.

Recent changes in 0.3.0-beta.8–beta.12​

  • 0.3.0-beta.13 — native security and installers: packages TLS/Tokio security updates, opener/persisted-scope updates and bounded macOS DMG packaging retries into new builds. See the beta.13 release notes.

  • 0.3.0-beta.11 — long-document editing: reuses measurements for unchanged content and renders page guides only around the visible area while navigating. No server migration or OMI format change is required. See the beta.11 release notes.

  • 0.3.0-beta.10 — print pagination: measures manuscript blocks and footnotes in short, cancellable animation-frame batches to keep the live publication editor responsive. No server migration or OMI format change is required. See the beta.10 release notes.

  • 0.3.0-beta.9 — Linux and localization: improves Linux deep-link error handling and includes Dutch and Polish interface and research-module translations. No server migration or OMI format change is required. See the beta.9 release notes.

  • 0.3.0-beta.8 — DOCX import: prevents a document title from appearing twice when it is repeated as the first numbered heading, including in large-document imports. No server migration or OMI format change is required. See the beta.8 release notes.

Changes in 0.3.0-beta.7​

  • Android and EuroOffice: keeps the WebView and embedded editor controls above system navigation, with a persistent editor host and compact floating controls.
  • External editing and recognition: adds recoverable EuroOffice save snapshots, revision-bound final saves, and Transkribus page recognition with named model selection, explicit credit consent and reviewed source/rights-aware insertion. Unknown paid requests are not automatically resubmitted.
  • Interchange and localization: adds Preview ODT import/export with explicit loss diagnostics and fixes PO-backed interface/research-module translations in production bundles.
  • Interface and accounts: compact responsive settings, wrapping language choices, removal of the redundant simple text editor, and browser passkeys where configured. Native passkey handoff remains unsupported.
  • Version identities: Studio 0.3.0-beta.7; Windows MSI 0.3.0.7; iOS short version 0.3.0, build 19; Android versionCode floor 1206. The portable format stays at OMI-SPEC-320@0.3.0.
  • Deployment: pending application and identity migrations are required; deploy the API before the clients. See the release notes.

Changes in 0.3.0-beta.6​

  • Semantic source attribution: Links an imported visual object to the bibliographic record for its source using a portable prov:wasDerivedFrom relation. Assertion status distinguishes machine-inferred, author-declared and author-confirmed sources.
  • Portable format: Advances OMI-SPEC-320 to 0.3.0. Studio explicitly rejects unsupported older formats and does not migrate them silently.
  • Version identities: Studio is 0.3.0-beta.6; Windows MSI is 0.3.0.6; iOS beta build is 18; Android versionCode floor is 1205.

Changes in 0.3.0-beta.5​

  • Source review: Adds a review step before imported references are added to a reference library and before DOCX/PDF manuscript conversion is accepted.
  • Provenance: Retains the declared origin of each imported visual object, including author-declared own work, without exposing private local filenames. OJS/OMP source attribution stays visible in editable manuscript projections.
  • Research excerpts: Extends source-backed excerpts to additional safe module fields.
  • Reading notes: The bottom panel shows only notes anchored to text currently visible in the manuscript, follows scrolling, grows only as needed up to half the usable viewport, and scrolls overflow internally.
  • Android diagnostics: Help shows the Android versionCode alongside the shared application version.

This page describes implemented product capabilities, not OMI specification conformance. The OMI-SPEC-190 Collaboration and Permission Model Draft defines separate semantic obligations for grants, scoped access, invitations, live-session revocation, anonymity, audit and federation. Existing server-authorized Studio collaboration demonstrates part of this direction but no normative OMI-SPEC-190 conformance claim or independent fixture suite is available. The OMI-SPEC-180 Draft and the author validation guide document the merged experimental validation implementation and its RC progress/timing improvements, without making a normative conformance claim. Source-aligned manuscript translations now have a Studio author guide and a separate OMI-SPEC-170 Draft; the existing Studio translation extension is experimental, not normative conformance. Formal specification maturity and conformance evidence are tracked separately in the OMI Implementation Status Matrix. Publication-profile behaviour is mapped requirement by requirement in the Studio OMI-SPEC-240 Implementation Profile; that profile records implementation evidence and does not make a formal conformance claim.

Status vocabulary​

  • Operational — implemented in the current Studio development line and available when its normal runtime prerequisites are present.
  • Configuration-dependent — implemented, but requires installation-specific server credentials, OAuth/OIDC registration, mail delivery, an external service, database migration, or a publishing-system connection.
  • Validated native target — implementation and CI/native build validation exist, but public distribution still depends on platform signing/provisioning.
  • Foundation — architecture, registry, UI or configuration support exists, but the complete end-user service is not yet claimed as operational.

Current capabilities​

AreaStatusCurrent implementation
Structured manuscript editingOperationalSemantic sections, rich text, headings, inline formatting, lists, notes, references, tables and structured content handling.
Section ruler, tabs and columnsOperationalA ruler can apply paragraph/section tab stops and multi-column settings to the active section; selected text can also be converted into structured tables.
InDesign-compatible paragraph stylesOperationalReusable paragraph styles expose InDesign-oriented typography, spacing, indentation, rules, keep options and related publication controls with live rendering while remaining separate from manuscript semantics.
Adaptive form-field sizingOperationalShort numeric and fixed-length controls use compact content-oriented widths instead of automatically stretching across the available row.
Desktop and mobile multi-document workspaceOperational in merged development sourceBrowser-style document tabs keep several manuscripts open on desktop; Android/iOS now use compact horizontal, touch-sized tabs in a dedicated row. Tabs survive switching during the active session; persistence of all mobile tabs across application restart is not yet claimed.
One-step responsive navigationOperationalStudio navigation opens directly without an intermediate second-level menu. Desktop and mobile use the same responsive navigation model, including a same-position control for closing the navigation surface.
Session/workspace restorationOperationalNative and web workspace state can restore the previous working context, including open-document state, while explicit document-close controls allow the user to leave a manuscript without losing the surrounding application session.
Rich-text formatting controlsOperationalCompact inline formatting remains available near the selection; the expanded desktop menu is docked and viewport-safe, while inline language is selected from configured manuscript languages rather than free text. Automatic floating formatting can be disabled in editor settings. Mobile selection controls avoid collision with native text-selection UI.
Structured search and replaceOperationalSearch/replace overlay, scopes and result navigation with responsive access shared by desktop and mobile layouts.
Multilingual user interfaceOperational47 selectable UI languages with shared language selection. Interface, manuscript and metadata language preferences are managed in one compact responsive settings surface.
Time-zone preferencesOperationalStandard IANA time-zone selection with current UTC offsets and automatic system-zone defaulting.
Multilingual helpOperationalIntegrated localized help coverage across the supported Studio UI locales; Help surfaces report the current build version.
Accounts and authenticationOperationalServer-backed registration/login, logout and authenticated API access work in web and native clients. The same central account can be used across Windows, Android, iOS/iPadOS and browser clients. Native clients use bearer-session transport compatible with Tauri application origins.
Password recoveryConfiguration-dependentForgot-password/reset flow uses single-use expiring reset tokens stored only as hashes, generic account-existence responses and all-session revocation after successful password change. Requires working server mail delivery.
Federated sign-inConfiguration-dependentGoogle, Microsoft and configurable generic/institutional OIDC providers use Authorization Code + PKCE, state/nonce validation, discovery/JWKS validation and explicit account linking. Existing accounts are never auto-linked by e-mail alone.
Connected sign-in identitiesOperational / configuration-dependent providersAccount settings list password and connected ORCID/OIDC identities, allow configured providers to be linked/unlinked and prevent removal of the last usable sign-in method.
Account/profile interfaceOperationalShared server-backed personal profile editing is available across desktop/mobile layouts, with account identity separated from manuscript contributor metadata and organization-specific institutional membership.
Institutional profilesOperationalA Studio account can hold multiple institution memberships with one default affiliation. Shared institution name/ROR data is separated from membership-specific department, position, institutional e-mail, linked identity and role.
Institution administrator rolesConfiguration-dependentInstitution MEMBER, ADMIN and OWNER roles are server-authoritative. Institutional deployments expose dedicated administrator sign-in and role-protected member administration with last-owner protection.
Central OMI administrationConfiguration-dependentA separate ADMIN/OWNER central privilege plane can manage institutions, institution administrators, institution API credentials and administration audit events without obtaining manuscript/editorial-content access.
Institution Admin APIConfiguration-dependentInstitution-bound machine credentials use one-time raw token display, hashed storage, expiry/revocation and explicit scopes (institution:read, members:read, members:write, reserved integration scopes). Machine credentials cannot change owner roles.
Contributor identity modelOperationalContributors, roles, affiliations, identity assertions and author-profile workflows are represented separately from account identity.
ORCID authenticationConfiguration-dependentORCID OAuth/OIDC sign-in and linking infrastructure is implemented. Personal and institutional deployment credential sets are separated, and the active Sandbox/Production environment is visible in the Studio UI.
Portable ORCID-bound author signaturesConfiguration-dependentServer-committed immutable revision snapshots, ORCID author binding, WebAuthn signing, encrypted installation issuer keys and portable offline verification evidence are implemented.
Double-blind peer reviewOperationalAnonymous reviewer projection, review assignments, reviewer workspace, comments and review persistence. Reviewer launch permissions are role-scoped to preserve least privilege.
Editorial review dashboardOperationalEditor-facing overview and role-aware review portal for assigned peer-review work.
Studio-native editorial workflowOperational / configuration-dependentDNS-verified journals and presses without an authoritative OJS/OMP binding can run submission, reviewer assignment, double-anonymous peer review, author revision, editorial acceptance and revision-bound publication in Studio. OJS/OMP remain authoritative when configured.
Live manuscript collaborationOperationalYjs synchronization supports live co-editing after an invited author accepts in Studio. The invitation inbox supports acceptance without an e-mail message, and live cursors show collaborator names and distinct colors. Peer-review change tracking remains separate.
Personal reference libraryOperationalAccount-level bibliographic records can be reused across manuscripts. Each document keeps portable record snapshots and independently selects uncited works for its bibliography; cited works are included automatically.
Bidirectional OJS review writebackConfiguration-dependent / validatedSigned review writeback returns submitted review data to OJS. Reviewer launch scopes are least-privilege, and the two-round OJS review protocol is documented and exercised against the OJS 3.5 integration line.
Native OJS review formsConfiguration-dependent / validatedOJS review-form definitions can be imported into the reviewer workspace, rendered as Studio controls, localized safely and written back to OJS with the submitted review. Server handling keeps provider markup opaque and client rendering extracts text safely.
External/OJS review assignmentsConfiguration-dependentOJS-connected author, editor and reviewer workflows and external assignment context are implemented when the OJS integration is configured.
OJS manuscript launch/importConfiguration-dependentSigned launch assertions, manuscript/file retrieval and structured import of metadata and manuscript content from OJS.
OJS 3.5 interoperabilityValidated integration linePKP/OJS 3.5 compatibility is documented and exercised in native end-to-end author, editor and double-anonymous reviewer workflows, including assigned files, review forms, corrections, separated feedback and signed writeback. Cross-version regression remains ongoing release work.
OMP manuscript/study launch and reviewConfiguration-dependent / validatedSigned launch assertions map monographs and publications into Studio while reviewer access is restricted to the assigned study. Author, editor and double-anonymous reviewer flows cover assigned files, review forms, corrections, separated feedback and signed writeback.
OMP 3.5 interoperabilityValidated integration lineThe deployable OMP plugin and Studio integration are exercised end to end against OMP 3.5. Wider cross-version regression and production hardening remain ongoing release work.
DOCX structural importOperationalHeadings, inline semantics, list inheritance, footnotes/endnotes, references, structured tables and semantic index fields are handled. Large imports use deferred editor mounting and imported DOCX files open directly as OMI manuscripts.
Dynamic indexes and listsOperationalImported Word index fields are represented semantically rather than as stale page-number text. Index occurrences navigate to document locations; unresolved occurrence controls are suppressed. Name-index import normalizes letter/number boundaries and filters Arabic-number page-reference noise while retaining name-relevant Roman numerals.
Local spellingOperationalPersisted local spellcheck follows manuscript language through the platform/browser spellchecking layer.
Grammar and style proofreadingConfiguration-dependentOpt-in advanced checking can use LanguageTool-compatible and configured AI language services. Issues are shown in the manuscript and suggestions are explicitly applied by the user.
Translation executionConfiguration-dependentStructured DeepL translation operates on selection/block/section/manuscript scopes while preserving inline semantics and excluding citations, code, equations and bibliography records from unsafe flattening. Language variants can be stored separately.
Unified manuscript validation (OMI-SPEC-180 experimental profile)Proposed in Studio PR #783; not yet verified in current releaseManuscript → Validation adds non-mutating authoring, OMI-exchange and publication-preflight checks; source-bound reports, JSON download, distinct document errors and incomplete coverage, localized diagnostic navigation and mobile/desktop UI. Guide · Draft specification · Studio PR #783. Existing JATS/PDF/signature gates remain separate.
Source-aligned manuscript translations (OMI-SPEC-170 experimental Studio profile)Operational in current sourceManuscript → Translations manages portable source/target language variants, fingerprints and freshness, explicit equivalence and review, retained targets after source edits, alignment synchronization/archival, DeepL-preview adoption and guarded parallel/target HTML text proofs. Author guide · OMI-SPEC-170 Draft · Studio technical profile. This is not a conformant publication-edition pipeline.
AI integration agentsConfiguration-dependentProvider-neutral language editor, metadata assistant, summarizer and citation-checker agents return suggestions through scoped server-side execution. External transmission of review-confidential content requires explicit permission.
Integration audit and extension registryOperational foundation / configuration-dependent executionIntegration execution records operation metadata/digests without storing manuscript text or secrets. Extension manifests support version compatibility, permissions, capabilities and HTTPS-only external endpoints.
Per-document bibliography selectionOperationalEach manuscript can explicitly include selected uncited works in its bibliography, while actually cited records remain automatically included. The same selection is respected by HTML, JATS, custom export and Studio-native review snapshots.
Portable OMI exportOperationalPortable .omi.zip and OMI JSON outputs are available as first-class interchange forms.
Scholarly/publishing exportsOperationalJATS XML, semantic offline HTML package, DOCX, EPUB, PDF, IDML, XPress Tags, FrameMaker MIF, Scribus SLA and LaTeX are represented in the current export layer. JATS, HTML and PDF publication outputs participate in the validated publication-build pipeline, and semantic index fields can be exported back to DOCX.
JATS 1.4 validated exportOperationalStudio targets NISO JATS 1.4 Article Authoring with the MathML 3 DTD. The server performs full offline validation with a pinned local schema package and rejects untrusted entity/DTD substitution.
JATS semantic conformance and release gatesOperationalA machine-readable OMI→JATS capability matrix distinguishes stable, conditional and fallback mappings. Error-level renderer diagnostics and known fidelity fallbacks can block release even when XML is DTD-valid.
Publication build provenanceOperationalJATS, semantic HTML and PDF publication artifacts receive portable .omi-build.json sidecars containing the committed revision, state/profile digests, artifact SHA-256, Studio build identity and renderer information.
Printed and interactive PDF exportOperational / server renderer requiredPDF export distinguishes print/archive output from interactive output. Final artifacts are rendered with pinned Vivliostyle CLI rather than the browser print dialog; print/archive mode removes active hyperlinks while interactive mode preserves usable scholarly and external links. Merged preflight checks reject missing, corrupted or unresolved referenced images instead of silently producing incomplete output.
Cross-platform export deliveryOperationalHosted Studio uses browser downloads; installed Tauri clients use native save/document-provider dialogs and binary writes for supported export targets. Publication sidecars are delivered alongside the artifact where the platform exposes a sibling path, or through a second save action on mobile document providers.
Publisher profilesOperationalPublisher profile, export stylesheet and print stylesheet handling are separated from manuscript semantics and included in publication-build provenance. The implementation is mapped to OMI-SPEC-240@0.1.0 in the dedicated Studio implementation profile, with remaining gaps recorded explicitly and no formal conformance claim.
Device-aware storage modeOperational on installed clientsStudio keeps a per-user, per-device “own device” trust preference. Own devices can retain normal native working paths; newly seen/shared devices default to a restricted mode that does not retain local working paths.
Profile cloud connectionsOperational / provider-dependentDirect WebDAV/Nextcloud credentials are encrypted server-side and scoped to the signed-in user, so profile cloud connections can follow the account across devices. Future OAuth cloud connections use the same profile-scoped model.
Portable storage on shared devicesOperational on installed clientsShared-device mode still permits explicit one-off open/save to removable or portable locations without keeping the selected path as the current working file.
Locally synchronized foldersOperational on desktopOneDrive, SharePoint, Google Drive, Dropbox, Nextcloud, iCloud Drive and other desktop-synchronized folders are treated as connection methods of their actual provider. Studio writes portable OMI files locally while the provider client performs authentication/synchronization.
Android native document workflowOperational betaAndroid uses the system Documents / Storage Access Framework picker for opening, Save, Save As, portable .omi.zip backup and supported export destinations instead of broad shared-storage permissions. Document lifecycle and close/reopen behavior remain part of focused beta regression testing.
iOS/iPadOS native Files workflowValidated native targetiPhone/iPad uses the Apple Files / UIDocumentPicker workflow with security-scoped document access for opening/saving OMI files and mobile-relevant export destinations. Public distribution still requires Apple signing/provisioning and device validation.
WebDAV / Nextcloud direct storageConfiguration-dependentDirect WebDAV/Nextcloud connections support encrypted server-side credentials, connection testing, portable backup upload, restore and deletion. Cloud-package upload/download integrity now uses SHA-256 and validates the package identity and restored referenced media; a reported successful save does not silently omit missing images.
Missing-media recoveryOperational in merged development sourceReferenced assets can be audited and verified bytes restored from a valid OMI container belonging to the same manuscript without replacing its text or revision history. This is user-initiated, not background synchronization.
Integrations catalogueOperationalProvider registry, catalogue UI, status client, declared authentication modes and execution surfaces are present.
Windows desktop applicationOperational betaTauri 2 Windows application, EXE/MSI packaging, native authentication, local-file access and native save flows are implemented.
Linux and macOS packagingOperational build targetsRelease automation defines Linux AppImage/DEB and macOS Intel/Apple Silicon DMG targets. Platform signing/notarization remains separate release-hardening work.
Android applicationOperational betaA universal Android APK is produced by the shared Tauri 2 release workflow. Server-backed auth, OIDC/ORCID native return handling, responsive navigation, native Documents/SAF file handling, export delivery and OMI branding are part of the shared client line.
iOS / iPadOS applicationValidated native targetTauri iOS project generation and the Apple Silicon iPhone/iPad simulator build succeed in CI, including native Files integration and shared mobile authentication/export code. Public TestFlight/App Store distribution still requires Apple Developer signing, provisioning, Universal Link association and physical-device validation.
Cross-platform update notificationsOperationalLogin, workspace, review and native/mobile surfaces check for newer public releases on startup, periodically and when the app becomes visible. Signed Tauri updater metadata is preferred where available, with current-release fallback for platform installers and Android APK delivery.
Desktop update flowOperationalUpdate notification and installer flow is implemented in the desktop application. Signed updater metadata is preferred; the public-release fallback prevents supported clients from being stranded when signed updater metadata is unavailable.
Cross-platform release automationOperationalGitHub Actions produces Windows, Linux, macOS and Android artifacts from the shared source tree and runs an iOS/iPadOS simulator smoke build. The current release pipeline binds each public release tag to the exact source commit, uploads assets only once, never retargets an existing release and never replaces existing release assets. A manual signed Apple release workflow is prepared for App Store Connect once Apple credentials are configured.
Release dependency reproducibilityOperationalJavaScript and Rust dependency graphs are lockfile-controlled; CI uses reproducible install paths including npm ci for the server.
Application brandingOperationalOMI Studio branding and generated native icon assets are used across the application shell and release packaging, including Android and the generated iOS/iPadOS target.
Security hardeningOperational baselineServer-side rate limiting, SSRF restrictions, OIDC state/nonce/PKCE and issuer validation, restricted secret persistence, hashed reset/Admin-API tokens, integration/admin auditing, safer import/export escaping and automated security scanning are incorporated into the current development line. OJS review-form rendering has additional markup/text isolation hardening. The remaining transitive glib 0.18.x advisory is tracked in one canonical upstream-blocked issue until the supported Tauri/GTK stack can move to glib >= 0.20.
Windows code signingNot yet enabledThe SignPath Foundation application was not accepted at the current public-adoption level. Windows installers remain unsigned; a paid signing route or a later Foundation reapplication remains possible as project visibility grows.

Cross-platform architecture​

Studio has a concrete shared-client architecture rather than separate web and native product lines. React/TypeScript, the OMI manuscript model, editor behavior, authentication flows, peer review, integrations and import/export logic are shared. Tauri 2 supplies native packaging and platform capabilities for desktop and mobile clients.

The responsive UI intentionally differs by form factor: desktop can expose multi-document tabs, a persistent document outline and multi-panel editing, while mobile uses compact navigation, drawers, touch-oriented controls and platform-native file pickers. This is a presentation difference, not a separate manuscript model.

The iOS/iPadOS target uses the same shared mobile client. Apple-specific work is confined to native packaging, Files/UIDocumentPicker document access, application metadata, signing/provisioning and Universal Link association.

Architecture boundaries​

Local-first manuscript ownership​

The native application can keep manuscripts in storage chosen by the author. A manuscript does not need to become proprietary server state merely because server-backed identity, collaboration or integrations are enabled.

Installed Studio clients distinguish a trusted personal device from a shared/foreign device. On an own device, normal local/system-storage working paths can be retained. On a shared device, Studio prefers profile-scoped cloud connections and does not retain the selected local path; one-off portable/removable storage remains available.

Server-backed identity and services​

Accounts, password recovery, connected identities, federated sign-in, collaboration, peer review, direct cloud connectors, institution administration and publishing-system integrations use the Studio API and PostgreSQL-backed services. Authentication identity is kept distinct from scholarly contributor identity and from institution membership. These features depend on the deployment being correctly configured and migrated.

Institutional administration boundary​

Institution membership (MEMBER / ADMIN / OWNER) and OMI central administration (ADMIN / OWNER) are separate authorization planes. Neither grants manuscript/review/editorial-content access by itself. Institution machine API credentials are bound to one institution and explicit scopes, and cannot alter owner roles.

See Institutional and Central Administration.

External integrations​

OMI separates manuscript semantics from provider-specific authentication and transport. OJS, OMP, cloud storage, ORCID, OIDC identity providers, translation services and AI agents therefore connect through integration layers rather than becoming part of the core document model.

Publishing-system authority​

For connected OJS and OMP workflows, the publishing system remains authoritative for submission workflow state, assignments, rounds and editorial decisions. Studio acts as the structured authoring and review workspace and exchanges information through defined application endpoints rather than direct database coupling.

The current OJS and OMP integrations are bidirectional for review work: Studio can consume role-scoped launch context, assigned files and native review-form definitions, and can return signed review submissions, corrections and separated author/editor feedback through the integration endpoint. OMP additionally preserves monograph/publication/study mapping and restricts reviewers to their assigned study. This does not transfer workflow authority from OJS or OMP to Studio.

Release and distribution​

1.0.0-rc.1 is available for Web and the direct Android APK. Desktop packages remain on 0.3.0-beta.13. GitHub Actions produces release artifacts from the shared source tree for Windows, Linux, macOS and Android. Desktop downloads are pinned to their published tag; the Android RC link selects its exact build artifact, while published release assets remain immutable. The application version is independent of the portable OMI manuscript format, which remains OMI-SPEC-320@0.3.0.

iOS/iPadOS currently has a successful CI simulator build rather than a public IPA. The Apple distribution path is prepared but deliberately separated from simulator validation: public/device builds require the real Apple Development Team ID, distribution certificate, provisioning profile and final apple-app-site-association configuration before TestFlight/App Store publication can be claimed.

See Open Manuscript Studio on iOS and iPadOS.

Beta validation focus​

The beta line shifts the release gate from “is the primary workflow implemented?” to “does it remain reliable across realistic documents, platforms, roles and failure conditions?”. Current validation priorities are:

  1. manuscript creation, opening, editing, saving, explicit closing, session restoration and reopening without data loss;
  2. large and structurally complex DOCX imports, including notes, tables, lists, fields and dynamic indexes;
  3. representative structured export paths on web and native clients, including printed versus interactive PDF behavior;
  4. OJS and OMP manuscript round-trip and role-aware author/editor/reviewer workflows, including assigned-file scoping, multi-round review, native review forms and signed writeback;
  5. Studio-native submission → review → revision → editorial acceptance → publication, including migration, authorization and revision-binding regression tests;
  6. reusable personal-reference-library behavior across multiple manuscripts and bibliography-selection fidelity across export formats;
  7. double-blind peer review without identity leakage and with least-privilege integration scopes;
  8. Android Documents/SAF lifecycle behavior and responsive mobile navigation;
  9. iOS/iPadOS Files/UIDocumentPicker behavior once signed physical-device testing is available;
  10. institution/central administration without privilege leakage into manuscript content;
  11. understandable user-facing recovery for network, authentication, migration, import/export and integration failures;
  12. release provenance, updater fallback behavior and immutable downloadable assets across successive beta releases;
  13. invitation expiry, explicit acceptance, authorization, reconnect and shared-document recovery in multi-author collaboration.

Configuration-dependent integrations do not need to be universally available for the beta line, provided their maturity is clearly identified and they do not compromise the stable core workflows.

Remaining beta hardening work​

  • complete focused Windows and Android regression passes, especially native document open/close/save/session-restoration behavior;
  • continue stress-testing large and structurally unusual DOCX manuscripts and improve graceful recovery for unsupported Word constructs;
  • exercise password reset, OIDC linking/unlinking and cross-device session behavior against production-like mail/provider configuration;
  • run migration and authorization regression tests for institution membership, central administration and institution Admin API credentials;
  • continue OJS 3.5 round-trip, multi-round review and cross-version interoperability testing;
  • continue OMP 3.5 cross-version interoperability, deployment and recovery hardening;
  • harden Studio-native editorial workflow migrations, editor/reviewer authorization and multi-round recovery;
  • stress-test large personal reference libraries, cross-document reuse and bibliography-selection export fidelity;
  • strengthen recovery behavior for interrupted network, cloud and synchronization operations;
  • replace remaining technical/raw error surfaces with actionable user-facing messages;
  • continue tracking the upstream Tauri/GTK migration until the transitive glib 0.18.x advisory can be removed by a supported dependency update;
  • integrate Windows production code signing if/when the SignPath Foundation application is accepted;
  • continue macOS signing/notarization work;
  • configure Apple Developer signing/provisioning, production Universal Link association and TestFlight/device validation before claiming public iOS/iPadOS distribution;
  • continue store-oriented Android distribution work;
  • develop conformance suites mapping implementation behaviour directly to normative OMI requirements;
  • establish release-level compatibility guarantees for supported import/export targets.

The presence of a feature in this implementation snapshot must not be interpreted as formal conformance with an OMI specification unless a corresponding conformance class and evidence are published separately.