Providing feedback
We love hearing your feedback on our GeoNadir features, how you are using them, and how we might improve them.
We are also open to suggestions on developing new or enhanced features that are not currently available on GeoNadir. Please send your feedback to [email protected]
Although we make every attempt to incorporate your feedback and requests into future releases, we cannot always develop your requests, or they or may be developed well into the future.
This does not mean that we don't value your thoughts and ideas. However, our product development cycle drives our roadmap, and not everything can fit into the immediate or short-term plans.
Paid feature development
If you really need a particular feature within a set timeline, we do offer feature development consultancies. The feature will be assessed against its likely use by others, and if it is technically achievable at our current stage of the roadmap and your budget.
Paid feature development consultancies have the ability to 'skip the queue' ahead of other features on the roadmap.
Please send an email to [email protected] describing the problem you are trying to solve, and we can then get in touch to discuss how a current feature might work, or if a new feature could be developed.
Our standard product development cycle
We generally have a product development plan that extends out to six months in advance. This plan is designed to develop a suite of features that come together to achieve a new capability across the platform – small releases to build something big overall.
We then have a detailed plan of two-week development cycles running out for three months in advance. These cover new features, updates, or bug fixes. We then deploy new features once a fortnight. If a major bug arises we will fix and deploy immediately.
Before a feature even gets to the start line of being developed there is a lot of work that happens that generally takes six to eight weeks. This includes:
Getting user feedback to understand the problem they are trying to solve and if the solution they think they want is actually what they need.
Understanding where this feature fits within the larger product roadmap and making sure it is something other users will use and what the different user behaviors might be.
Working with our developers to understand the technical viability of the feature.
Developing the desired workflow for the feature to make it as intuitive as possible.
Designing the feature with our product designer to make sure all the elements are pixel-perfect and match the design templates for the platform.
Developing the documentation to explain the workflow for the feature, including what happens if a user doesn’t follow the correct path and what error states may need to be implemented.
Only after all these steps have been completed, then the feature moves across to the developers for development, and it is generally released two weeks later. Larger developments may consist of a series of two-weekly deployments.
How do I see what is on the roadmap
We don't publish what is on our roadmap because it can change. We don't want to publish something, get our users excited, and then change timelines. Changes happen due to paid feature development requests, technical development issues, and priority changes.
If you have requested a feature to be developed, you can expect it to be given a rating of:
High - High priority for development and will be done ASAP within the current three month roadmap.
Medium - Medium priority for development and will be considered within the current six month roadmap.
Low - Low priority for development and will not be considered at this time.
Being given a priority rating does not guarantee development of the feature within the specified time period, but does give you an understanding of its consideration for development.
If you would like certainty around development of a particular feature that you need, please consider our paid feature development as above.
Bug reporting
Bugs you find on the platform should be reported to [email protected] and will be assessed as either:
Hotfix - Requires immediate attention as it is affecting overall usability or security of the platform.
Priority - Requires attention ASAP as it is affecting the usability of a feature.
Low - Requires attention in the future as it is a minor issue.
Bugs are unfortunately part of software development and we don't like them as much as you! If you can report them with a quick video screenshare or screenshots, that helps us find and identify the bug a lot faster.
Thanks in advance for your help in squashing these bugs!