Version 0.3.0-beta.3 adds linked Word footnotes and endnotes, complete non-printing marks, persistent collaborator chat, clearer export formats, and improved JATS, IDML and OMI package workflows. It builds on live manuscript collaboration, Studio-native editorial workflows, publication layout and reusable reference libraries.
Live collaboration and accepted invitations
Invite a Studio author to a manuscript. The invitation appears in their Studio inbox, and access starts only after they accept. Collaborators edit together in real time and see names and distinct colors beside live cursors and selections.
InDesign-compatible paragraph and publication styling
The live publication editor now exposes an InDesign-inspired paragraph-style system with inheritance-aware controls and live rendering, while keeping manuscript semantics separate from reusable publication presentation.
Section ruler, tab stops and columns
Authors can apply ruler-driven tabs and multi-column layout to a selected manuscript section, together with text-to-table conversion and compact value controls suited to publishing work.
Studio-native editorial workflow
DNS-verified journals and presses that do not use OJS or OMP can run submission, double-anonymous review, author revision, editorial acceptance and publication in Studio. Acceptance is bound to the exact committed revision and remains separate from publication.
Personal reference library and document bibliography
Authors can save curated bibliographic records to an account-level personal library, reuse them across manuscripts and choose which uncited works appear in each document bibliography. Cited works remain included automatically.
HTML5 and print-layout zoom
The Word-style document zoom now works consistently in the HTML5 visual publication editor and the paged print-layout view.
Direct OJS/OMP author submission
From Publication, an eligible standalone study can be prepared and submitted directly to a configured OJS or OMP installation. Studio transfers manuscript metadata and files, preserves draft/retry state, validates the target workflow, and uses the author’s publishing-system API credentials.
PKP-compatible scholarly metadata
Submission metadata now covers structured contributor identity, separate given/family names, affiliations, ORCID-compatible fields and conflict-of-interest declarations for OJS/OMP exchange without collapsing publication-specific name formatting.
Reference-manager interoperability
RIS, BibTeX and CSL JSON interchange, bulk import, deduplication and linked-record refresh are available through the reference-management layer, with Mendeley OAuth integration for connected libraries.
Reusable personal reference library
Authors can save curated bibliographic records to an account-level library, reuse them across manuscripts, and choose which uncited works appear in each document bibliography. Cited works remain included automatically, and copied records remain portable inside the manuscript.
Studio-native editorial workflow
DNS-verified journals and presses without OJS/OMP can run submission, reviewer assignment, peer review, author revision, editorial acceptance and verified publication directly in Studio. OJS/OMP remain authoritative when configured.
InDesign-compatible layout controls
The live publication editor now includes InDesign-compatible paragraph styles, section-level rulers, tab stops, columns, text-to-table conversion and live rendering, while manuscript semantics remain separate from presentation.
Adaptive form layout
Short numeric and fixed-length fields size to their expected content instead of stretching across the full form, improving responsive density on desktop and mobile.
Native OMP 3.5 client
Studio discovers OMP capabilities, imports authorized source content and can return author revisions, assignment-scoped reviewer attachments, review-form responses and supported native review results while OMP remains authoritative for review completion and editorial decisions.
Release integrity and update flow
Desktop, mobile and review surfaces can notify users about newer Studio releases. The release pipeline binds a release tag to the exact build commit and never replaces assets of an already published release.
One-step responsive navigation
Studio navigation opens directly without an intermediate second-level menu. Desktop and mobile use the same responsive navigation model with a same-position close control.
Printed and interactive PDF export
Publication export distinguishes print/archive PDF from interactive PDF. Print output removes active links, while interactive output preserves usable internal and external links; typeset publication and neutral editorial content modes remain separate.
Desktop manuscript workspace
Browser-style document tabs, full-window Studio/Account surfaces and a toggleable Word-like document outline support long-form desktop work without changing the mobile structure workflow.
Large DOCX and rich-text usability
Large Word imports use deferred editor mounting and open directly as OMI manuscripts. Imported standalone DOCX studies are explicitly recognized as studies for direct publishing rather than being mistaken for volumes.
Dynamic indexes
Word XE markers are imported as semantic index targets instead of page-number text. Studio can present each name once with clickable links to real occurrences, while DOCX export writes XE and INDEX fields so final page numbers are generated from the exported layout.
Search, replace and block structure
Document search exposes search-and-replace directly and highlights matches. The current paragraph or selected blocks can be transformed between normal paragraphs, headings, block quotes, bullet lists, numbered lists and code blocks.
Proofreading, translation and agents
Local spellcheck follows manuscript language. Optional grammar/style services, DeepL execution, provider-neutral AI agents and integration audit records operate through explicit, scoped external-service flows.
Cross-device account security
Password recovery uses single-use expiring reset tokens and revokes prior sessions after password change. Connected sign-in methods can be managed from the account panel without conflating account identity with manuscript permissions.
Federated sign-in
Google, Microsoft and configurable institutional OpenID Connect providers use Authorization Code + PKCE, state/nonce checks and issuer/audience validation. Existing accounts require explicit identity linking rather than e-mail auto-linking.
Device-aware storage
Installed clients distinguish trusted personal devices from shared/foreign devices. Own devices can use native local/system storage; shared devices prefer profile cloud connections and do not retain local working paths.
Android-native file workflow
Android uses the system Documents / Storage Access Framework picker for opening, saving, Save As and portable OMI backup/export destinations instead of broad shared-storage permissions.
Android and Google Play beta distribution
Signed Android AAB/APK builds are operational. Google Play closed testing is available for eligible testers, while the universal APK remains available as a direct beta download from the current GitHub release.
iOS and iPadOS native target
The shared Tauri client generates and compiles as an Apple Silicon iPhone/iPad simulator app. Files/UIDocumentPicker storage, mobile export delivery and native authentication handoff are implemented; TestFlight/App Store distribution still requires Apple Developer signing, provisioning and Universal Link association.
Institutional and central administration
Personal and institutional profiles are separated. Institution MEMBER/ADMIN/OWNER roles, administrator sign-in, OMI central administration, scoped institution Admin API credentials and append-only admin audit events are implemented without granting manuscript access.
Verified scholarly identity
ORCID linking is integrated with cryptographic author signing: immutable committed revisions can be bound to verified ORCID identity and portable WebAuthn/issuer verification evidence.
Publishing-system workflows
OJS and OMP 3.5 author, editor and double-anonymous reviewer workflows are operational when configured. Native end-to-end tests verify assignment-scoped files, review forms, corrections, separated feedback and signed writeback, while the standalone author flow now also supports direct submission from Studio.
The project is in public beta. Beta development prioritizes regression testing, large-document performance, error recovery, interoperability, migration discipline and trustworthy immutable releases on the path to the first release candidate.