To put this nicely, ACC handles photos (e.g. images) very poorly. There is no consistency across the platform.
And while there are numerous ideas on this board regarding specific photo features, this idea is to deal with the larger matter that there is no coherent approach across ACC.
Two licenses, two approaches, two problems
The first and biggest problem is that there are two approaches to how photos are managed, depending on whether you are a Docs user or a Build user.
Docs has the bare minimum features integrated into the standard folder/file browsing, while Build has a dedicate Photos module with some awesome organisation functionality. The fact that the Photos module is only available to the Build users borders on contempt to the Docs users who participate only during the design phase.
ACC fails to understand workflows and requirements for users anywhere from early site investigation through to pre-construction where photos play an important role leading up to the transition to build. They can't be treated as a second-class file in the Docs space.
Photo Features
Let's now look at the features between the Docs and Build spaces.
- Management - Build's Photos module has great management features through AI feature tagging, photo types, and locations including the photo's geolocation for viewing on a map.
- 360 Photos - Build's Photos module correctly supports 360 photos.
- Markups - Build supports basic markups on the mobile app, but not the desktop. Photo files in Docs supports the full markup toolset, but only on the desktop since there is no mobile app support for Docs.
- Duplicated Photos - Build's Photos, when marked up on the mobile app duplicates the photo. This results in the newly marked up photo no longer maintaining references with other documents, such as a photo markup on a document. I suspect it does this due to the Build Photos module not supporting the full markup toolset that is available in Docs.
Mobile App Access
Build's Photos module experience is fairly similar between the desktop and mobile app.
But since Autodesk Docs is not supported on the mobile app, it means there is currently zero way for a Docs user to make use of any image/photo features while on site. It means that the Docs user cannot effectively undergo a site inspection during the early design stages.
There are some great features for managing photos/images across Docs and Build. But it comes with a confusing and messy message that greatly favours a particular role of user.
This idea is to consolidate the Photos module across both Docs and Build, ensuring that any early photographic work can start in Docs during design, and ultimately be available in Build during construction.
