Viewport

Roadmap

What we are working on next, and what we have decided not to build. No dates, because a date on this page would be a guess dressed up as a promise.

このページはまだ翻訳されておらず、英語で表示しています。

How to read this

This is what we intend to do, in the order we currently intend to do it. It is not a contract. Things move down the list when something more urgent arrives, and things get dropped when they turn out to be a worse idea than they sounded.

Nothing here carries a delivery date. Anything already finished is on the changelog instead, which is the page that describes what actually exists.

Being worked on

  • Chrome Web Store listing. Screenshots, the store description, and the localised listing text for all twelve languages.
  • A Firefox build. The extension APIs differ enough that it is a separate build rather than a flag, which is why it is not simply shipped alongside Chrome.
  • Translating this site's documentation, changelog and roadmap. The interface and the marketing pages are already in twelve languages; these three are not yet.

Wanted, not started

  • More devices, particularly older and low-end Android hardware, where the interesting layout bugs usually are.
  • Exporting a visual regression run as a report you can attach to a pull request, rather than one diff image at a time.
  • Sharing a scene with a teammate, so a board of devices and URLs can be sent as a link instead of described in a message.
  • A CLI for running the same regression checks in CI, using the same baselines.
  • Cookie seeding alongside page state, which needs a permission Viewport deliberately does not ask for today.

Decided against

Saying no is part of a roadmap. These have been considered and are not planned.

  • Cloud rendering. Viewport runs in your browser, which is the reason nothing you preview leaves your machine. Moving rendering to a server would trade the single best property of the product for a marketing bullet.
  • Real device farms. Useful, genuinely different, and not something a browser extension can honestly claim to be.
  • Telemetry and usage analytics. The privacy policy says there are none, and we would rather keep that sentence true than know which button is most popular.
  • Team accounts and seat management, at least for now. A tool that works the moment it is installed, with no account, is worth more than one that needs an administrator.

Ask for something

The list above is shaped by what people ask for. If something you need is missing, say so, and say what you are trying to do rather than what feature you think would do it. That distinction is usually where the better idea comes from.

support@orbitexaio.com