Manifest contract
The manifest defines the package identity, work, edition, assets, and navigation entry points.
Local-first reader app
BookField
BookField reads installable .wbpkg packages on your device. It is built for learning materials, reference content, annotations, schedules, and offline reading without turning the app into a cloud service.
.wbpkg import
Offline reading
Notes and highlights
Package format
A package that BookField can install and read
.wbpkg is the installable package format used by BookField. A package carries the manifest, ReaderDoc content, media assets, navigation tree, optional study plans, and locator indexes needed for local use.
ReaderDoc content
ReaderDoc-backed text is imported into local storage so the app does not parse EPUB, HTML, or CSS at runtime.
Offline references
Locator indexes and bindings let authored references resolve on the device when the matching packages are installed.
Reader experience
Built around installed packages, not cloud documents
BookField focuses on the reader experience after a package is installed: library management, reading position, local annotations, schedules, and search.
Library import
Import .wbpkg files from the app library or from Files and Open In flows.
Library-first access
Open recently used packages and keep the reading entry point close to the package itself.
Study plans
Use authored study plans on a calendar when the package includes schedule metadata.
Search and notes
Keep highlights, paragraph notes, bookmarks, and searchable local records on the device.
Package handoff
Keep the public workflow simple
The public page keeps the handoff at a product level. It describes how a prepared package moves into BookField without exposing internal production tooling.
-
1
Receive a .wbpkg
A publisher or internal workflow prepares an installable package for BookField.
-
2
Import into BookField
The user imports the package into BookField and the reader validates and stores it locally.
-
3
Read, schedule, search
The installed package appears in Library, and authored schedules and search data become available.
Platform status
Current implementation baseline
- iOS
- The current product baseline is the iOS implementation.
- Android
- Android follows the iOS behavior and is in parity hardening.
Technical notes
Boundaries that keep the reader predictable
- Imported package content is stored locally for reading and lookup.
- The initial product promise does not depend on cloud sync.
- Reader-side authoring is out of scope; BookField reads prepared packages.
- Navigation is controlled by the package navigation tree, not by runtime EPUB parsing.
Plan a BookField package flow
Use the package overview to decide whether BookField fits your content model, or discuss a custom distribution flow for your materials.