Marshall et al. — I am the current Product Owner of TBC, and I wanted to share my thoughts on your submission and comments from others who have taken the time to post here.
First of all, thank you!
All of you clearly care enough about the product, it’s features, and it’s shortcomings to take time out of your busy day to voice their opinions and frustrations. While at first glance, this thread may feel intimidating and disheartening; to me, it is the complete opposite. Your comments about features and issues based on your usage and experience are worth consideration, and I wanted to share what I and the rest of the TBC are going to do about it.
Please note that while I cannot discuss specific timelines due to established Trimble policy, my goal here is to share my thought process and what I will do about the discussion points mentioned in Marshall Cant’s original post.
1) Retaining customizations — this has been on the team’s list for a while, and there is ongoing effort to finalize the infrastructure and changes needed in TBC to support it.
Action — actively working on this, will be provided in a future release.
2) Cleanup utility — this is not needed for all installations, and it is recommended to make sure that no other program or unintended actions taken by the user on their machine would interfere with the product. If you find yourself having to run the utility for every install, this might be related to what’s on your computer, and cleanup would be necessary in such cases.
Action — no change needed, I welcome suggestions if you believe otherwise.
3) Dark theme — the decision to remove the dark theme was a practical one due to the effort it demanded from the team. It was a trade-off — either spend time maintaining a theme, or spend time providing functionality. While this may not be the most persuasive reasoning for taking it away, it is the real reason. Instead of delivering a half-baked solution, the decision was made to take it away. I now believe this to have been an error and needs to be rectified.
Action — needs to be addressed.
4) Light interface — this was a result of the Trimble branding initiative across multiple products. I am sure we can agree that no theme will be perfect for everyone and some will like it more than others. However, I don’t want to brush this off merely as a disagreement, and I will reach out to our design team with your feedback.
Action — comments to be shared with the Trimble design team.
5) Layer Manager — no arguments here, these are all valid asks, and while I cannot speak to what happened two years ago when you asked for it, I will work with the team and put this in our backlog, so we don’t lose sight of it. Again, I cannot share timelines, as I mentioned above.
Action — candidate for backlog item for future consideration.
6) Interface inconsistency — this one is interesting, and I would like to explore this further with you. My email address is below, and I would appreciate it if you could drop me a line so we can continue this conversation further.
Action — follow-up needed, potential for future consideration.
7) 4K monitor support — the team looked into this before, and there was not much adoption of 4K monitors to justify the effort given that this is a significant undertaking. Since then, the adoption of 4K monitors seems to be gone up, and I believe we are at a point when this will need to be looked into.
Action — needs to be addressed.
I would also like to add that while the community is fundamentally a tool for asking questions and getting answers from other users, noting features and defects here is not the best way to get such items into the backlog. I realize that there is no good way at the moment to be sure that these items get into the backlog.
I am going to change that and provide a way for you and other users to add items on the list for consideration, and that isn’t just content floating around in an endless thread of emails.
Here’s what I am doing — I am working with the team that administers this community to provide a way for capturing ideas and defects and allow for a way to vote on such items so that I can prioritize and provide feedback on such asks. This setup will take some time, so I ask for your understanding as I look into all the moving pieces to make this happen.
And finally - Sanjeev_Saha@trimble.com - I am leaving my email address here so you and others can contact me directly to follow-up on this and any other thoughts you might have. I realize I am opening myself to a world of overflowing inbox, and I believe this is necessary until I can get the setup to track requests from the community that will work for the long term.
I hope this gives you and everyone else a sense of my thought process.
Again, I want to thank you and everyone who has taken the time to share thoughts, opinions, frustrations, and candid feedback. This community wouldn’t be of much help without your active engagement.
Sanjeev