We’re excited about SketchUp 2024. It’s been great to hear the positive feedback on new improvements like the Ambient Occlusion making models more realistic and easier to understand and the improvements to graphics that make it much easier to view and navigate big models. But that’s not what this blog post is about. This post provides more context for less popular changes we’ve been making to SketchUp based on our “End of Support” policy.
End of Support: What’s that?
All software (and hardware) eventually dies. Windows 95 was a great operating system, but it’s dead in terms of support from Microsoft even as Windows still flourishes. To ensure SketchUp does the same, we have to make decisions about when to stop supporting older versions.
To this end, we formalized our End of Support policy a couple of years ago. SketchUp’s End of Support policy is how we constrain the cost of maintenance. We do this by asking ourselves, “How much effort does it take us to continue to support an old version, and how much value do our paying customers get from that support?”.
The burden of ongoing support
For an example, let’s consider Add Location. In SketchUp 2024, Add Location got a reboot. The feature needed to be rebuilt on new technology so that it could be efficiently improved with new functionality in the future. We were not able to update Add Location on old SketchUp versions, so we will now have two versions of that feature live for customers to use. We will maintain these two Add Location versions until SketchUp 2023 goes out of service in January 2026. This means for the next two years, we are committed to doubling our investment in:
- Security updates
- Customer support, documentation, and training
- Compatibility testing between versions
This extra cost is real and does not bring any value to customers. On the flip side, it forces us to invest in maintaining old code instead of investing those resources in fixing bugs and shipping new, high-quality features. The new version should be better and we should be able to just have everyone use it, but when it comes to desktop software, people don’t always want to and sometimes can’t update straight away. Introducing clarity around the End of Support policy has helped us a lot in planning, estimating, and controlling these costs.
Okay, but why restrict downsaving?
In SketchUp 2024.0, we have taken away the ability to downsave to versions of SketchUp older than 2021.
Including downsave capabilities in new versions adds cost and also constrains how we evolve file formats in the future. For example, if we included downsaving in 2024, we would task ourselves with doing QA (Quality Assurance) to make sure every file format works. We would try to fix bugs associated with failures in downsaving. If we spend R&D time on this, we have to take it away from other things people want.
Looking ahead, we would also need to think about whether new features would "break” downsaving and whether we should change designs or invest more effort in those features just to make sure we could keep downsaving to ancient versions. We don’t want our engineers worrying about that - we want them to be able to look forward and focus on capabilities that support customers with new technology.
This is why we have removed the downsave feature from 2024.0 and why we needed to start managing expectations better about downsaving in general.
In short - our focus is forward-looking. There are so many ways people want us to keep improving SketchUp. We’re prioritizing our development spend on addressing those needs.
Providing feedback
If you want to be part of the process of providing feedback on future development, check out our Labs page, where we share experimental projects we are seeking feedback on. We’d love to have you involved in our testing and development process - helping us make SketchUp a better product for you.
If you’re an existing user and this affects you directly, please tell us here. We’d like to understand your workflow and see if we can help make this easier.
Thanks for your time.