microProject
microProject is a desktop project planning application for Windows, Linux,
and macOS. It brings the task outline, schedule, dependencies, resources,
progress, and Gantt chart together in one workspace, with an Office-style
ribbon and keyboard-driven editing.
microProject は、タスク階層・日程・依存関係・リソース・進捗をガント
チャートと同じ画面で扱うデスクトップ計画アプリです（日本語の概要）。
Download the latest release ·
Documentation and user guide ·
Compatibility roadmap
A commercial construction plan: the WBS task outline on the left, linked tasks,
milestones, and parallel work streams on the shared Gantt timeline on the right.
Features
- Task table and Gantt in one view — edit a WBS outline in the spreadsheet
and see durations, links, milestones, and progress on the timeline.
- Scheduling — dependencies, calendars, constraints, baselines, and
resource assignments with automatic rescheduling.
- Critical Chain (CCPM) — preview and apply resource-aware leveling, view
the critical-chain network, and track project and feeding buffer consumption.
- Office-style desktop UI — a ribbon modelled on current Microsoft 365
applications, Microsoft Project–style shortcut keys, Undo/Redo, printing, and
PDF output.
- Open file formats — the native
.mpo format, with import of Microsoft
Project .mpp and MPX files and exchange through Project XML and XLSX.
- Self-contained packages — the Java runtime is bundled; no separate Java
installation is needed.
Download
Windows is the reference platform. Linux and macOS packages are built from the
same source, and platform-specific behavior is verified separately. The
documentation site always points at
the newest stable package for each platform.
File formats
| Format | Role |
|---|
.mpo (MPO) | Native format and default save format. Newer releases keep reading files from earlier supported releases. |
.mpp | Microsoft Project files — import only. Writing MPP is out of scope; save as .mpo instead. |
| Project XML, XLSX | External interchange formats — open and save. |
| MPX | Older Microsoft Project exchange format — import only. |
.pod | ProjectLibre's standard format — opens and saves, but CCPM settings are not stored; use .mpo to keep them. |
Microsoft Project compatibility
microProject's goal is compatibility with the standalone Microsoft Project
desktop application: scheduling semantics, views, commands, keyboard and
mouse interaction, and project files. That goal is not yet achieved; the
milestones below are tracked publicly.
| Gate | Scope | Status |
|---|
| M0 | Target and complete coverage inventory | Open — #792 |
| M1 | Current Office-style ribbon visuals | Open — #793 |
| M2 | Offline desktop workflow parity | Open — #794 |
| M3 | MPP reading and other file interoperability (MPP writing out of scope) | Open — #796 |
| M4 | Microsoft Project-specific automation and extensions | Excluded by product scope — #797 |
| M5 | Release compatibility acceptance | Open — #795 |
Out of scope: Project Server, Project Web App, Project Online, Microsoft
Planner and other cloud sign-in or synchronization; VBA/macros, COM, VSTO, and
Microsoft Office add-ins. Local files, linked/master projects, shared
resources, offline collaboration, and microProject's own automation and
extensions remain in scope. See the compatibility goal,
the roadmap, and the
ribbon command inventory.
Build from source
Requirements:
- Windows, Linux, or macOS with a full JDK 25 or newer that includes
jpackage. Every module compiles with --release 25. If JAVA_HOME is not
set, the Windows release tasks fall back to C:\Program Files\Java\jdk-25.
- The checked-in Gradle Wrapper (no separate Gradle install).
- WiX Toolset on
PATH for the Windows MSI. A per-user WiX install under
%LOCALAPPDATA%\Programs\WiX Toolset v7.0\bin is picked up automatically.
.\gradlew.bat build # compile and test all modules
.\gradlew.bat stageAppDist # create the runnable desktop layout
.\scripts\run_microproject_clean.bat # clean build and launch on Windows
The runnable layout is modules\microproject_ui\build\install\microproject_ui.
For manual UI checks always use a freshly generated layout, never an older
build/install copy; see docs/build-and-run.md.
Packaging tasks (outputs go to build\releases\v<version>\):
This is the beginning of the README. Read the rest at the original. Read the full README ↗
