Skip to content

Roadmap Overview

This roadmap exists to give a clear picture of where Crestr is heading over the next few years.

It likely won't remain the same, as I will be a university student and as such may not always be able to commit myself to long-term projects, most notably, the mobile app (which may be delayed beyond Nov. 2027)

A Personal Note

Crestr started as my A‑Level Computer Science project in 2025.
Most of the early work, such as the first A* implementation, the KDTree, the basic UI, the initial routing engine, was built during my spare time.

In 2026, I continued developing Crestr while finishing my A‑Levels and preparing for university.
From September 2026 onward, I’ll be starting my first year at university, which means development pace will shift depending on workload, deadlines, and life in general.

Some features may arrive earlier than expected and others will undoubtedly slip, that’s just the reality of being a solo dev working on a long‑term project.

How to Read This Roadmap

Each year in this roadmap represents a realistic snapshot of what I can achieve within that timeframe:

  • 2025 covers the foundational work; the core routing engine, KDTree, manual and automatic routing, and the basic structure of the app.
  • 2026 focuses on medium‑scale improvements that strengthen Crest’s core experience and prepare the groundwork for bigger architectural changes.
  • 2027 is reserved for the major, long‑horizon features; the kind of work that takes months of research, experimentation, and iteration.

Every year is broken into:

  • Achieved: completed work
  • In Progress: currently being developed
  • Planned: realistic goals for that year
  • All Items: a combined list for quick reference

The Journey Ahead

This roadmap will evolve as Crestr grows.
Ideas will be added, removed, or shift between years as I learn more and balance development with university life.

Crestr is something I enjoy building, and this roadmap is here to keep development transparent and structured.