PixivFE Development Status and Roadmap

PixivFE is an open-source, self-hostable alternative front-end for pixiv, and its documentation treats development as an ongoing, publicly tracked effort rather than a finished product. The docs include dedicated pages for Development, Roadmap, Scope, and a Feature tracker, alongside supporting material on Testing, Tools, Coding tips, and Design flaws. If you want to know where the project stands or how to get involved, those documentation sections are the place to start.

What the documentation says about development

The PixivFE documentation lists a Development section that groups the project's contributor-facing material. Based on the documentation structure, this section covers:

• Roadmap – the planned direction of the project.
• Scope – what the project intends to cover (and, by implication, what falls outside it).
• Feature tracker – a running record of features.
• Guidelines – expectations for contributors.
• Testing – how the project is tested.
• Tools – utilities relevant to development.
• Coding tips – practical notes for working on the codebase.
• Design flaws – acknowledged shortcomings in the current design.

The presence of a "Design flaws" page is notable: it signals that the project documents its own weaknesses openly rather than presenting only polished features. For anyone evaluating whether to contribute or self-host, that transparency is useful context.

How features and functionality are documented

Beyond the contributor pages, the documentation also covers functional areas that affect both users and developers:

• Features – an overview of what PixivFE provides.
• Caching – how caching is handled.
• Tracing flamegraph – performance tracing output.
• Internationalization – translation and locale support, with an "Old I18n" page retained under an Archive section.
• Framework migration – also archived, indicating the project has moved between frameworks at least once.

The Archive section (containing Framework migration and Old I18n) suggests these are historical records rather than current guidance. If you are reading the docs, treat archived pages as background, not as instructions for the current codebase.

Where to find the project's current state

The documentation's Home page links to several entry points that matter for tracking status:

For development status specifically, the Roadmap and Feature tracker pages are the most direct sources. The Known quirks page is worth reading alongside them, since it captures behavior that may look like bugs but is documented as expected.

Getting involved

If you want to contribute, the documentation's Development section provides the starting points: read the Guidelines first, then check Testing and Tools to understand the workflow. The Coding tips page offers practical advice, and Design flaws tells you where the project already knows it has problems — often a good place to find work that needs doing.

The docs also note dates on the Home page (February 28, 2025 and August 26, 2024), which appear to be update markers. Because the project is actively documented, check the live documentation at pixivfe-docs.pages.dev rather than relying on any single snapshot, since roadmap items and feature status can change.