Roadmap

chriswe73

Hi there!

How about a Roadmap, maybe including a voting optiion?

Helps you to understand customer needs and us as user.

Best Chris

paolo

We don’t use roadmaps because they create unrealistic expectations, which put unnecessary pressure on developers. Instead of locking ourselves into a fixed plan, we prefer the flexibility to prioritize what truly matters as we go.

This allows us to focus on what is most valuable at any given time rather than chasing arbitrary deadlines. It also allows us to adapt, respond to actual needs, and deliver better results without the stress of meeting pre-set promises that may no longer make sense.

link2selwyn

paolo
Hi Paolo,

Thanks for explaining your approach and the reasons behind avoiding a traditional roadmap. I can see the value in staying flexible and reducing developer pressure, and I respect that you want to focus on delivering what matters most in the moment.

That said, I’d like to offer a perspective from the user side, especially for those of us working across the full GeoDirectory ecosystem, including both the free core and multiple premium extensions.

While we’re not necessarily looking for strict delivery deadlines, there is a real need for better visibility and communication around:

Which features are planned or under review

What limitations or issues exist with current functionality

What improvements are being considered for premium extensions

Gaps between marketing descriptions and how certain features actually behave

This is especially important when using paid products. Sometimes features are technically present but function poorly, lack usability, or have a confusing UI. Without a way to track known issues or improvements, users are left in the dark and often disappointed after purchase. It also leads to repeated support tickets and unnecessary frustration.

A possible middle-ground solution could be a public feedback and development board, something lightweight but visible. It could include categories like:

Under Review

Planned

In Progress

Improvement Needed (for existing features)

Shipped

Won’t Implement (with reasoning)

It would also be helpful to have a dedicated section for premium plugin concerns, especially where existing functionality is unclear, incomplete, or below expectations. Adding basic community input, such as voting or commenting, could help surface the most common and impactful issues without committing your team to fixed timelines.

This approach would not compromise your agile method but would offer more transparency and build stronger trust with your user base, especially those who are investing in the full stack of your products.

Thanks again for the ongoing work with GeoDirectory and for considering ways to make the ecosystem more transparent and collaborative for everyone.

Best Regards