Desktop Version Support
With local file system view and quick upload of assets/versions/attachments. Would even be awesome if the local file system (or just designated folders) was backed up to the cloud. Users could view that content from the desktop or cloud version and move content from a personal "Draft" state into a workspace.
Sub Libraries within Libraries
The ability to add folders or sub-libraries to a Library. To better sort and organize Libraries
I'd love to be able to sync the entire folder structure to my local disk like Dropbox or Google Drive. it's quite a hassle to download everything manually, and downloads fail frequently on slower connections.
Better 3D File Viewing
The 3d viewer needs to support environment settings (lighting, background color, scale, orientation). Even better would be if the viewer could import file attachments and use those as part of the file definition (i.e textures or normal maps assigned in .fbx or .3ds files).
Assign Tasks To Users
Tasks could represent uploading assets, providing reviews for existing assets, uploading supporting attachments to an asset, or completing steps in the upcoming workflows/pipelines. We would create views in the platform to allow users to see tasks assigned to themselves and other users, either as a kanban board or backlog view. We may even experiment with things like sprints and more robust project management utilities. Alternatively, or in tandem, we will likely look at integrating with existing project management tools such as Trello, Shotgun, Jira, Favro, or other project management platforms.
3D File Metadata Extraction
Peek into 3d files to view things like polycounts (quads, tris, n-gons), materials, animation layers, outliner (mesh/scene hierarchy).
I realize this might be a pipe dream as it may go against the mudstack company direction - Being able to host a backend for mudstack locally would be amazing. This would allow uploads / downloads to be on-network and thus not limited by internet speeds, and of course allow us to add storage as needed. We would be very happy to pay for the mudstack client and associated tech while also having the ability to self-host the storage backend (see: P4 model).
Automated posting to Discord or API connection be available for automated posting through Zapier or other webhooks.
mudstack cloud should have a folder structure over a flat file structure to better match how our team organizes files.