(tlDr below)
As I mentioned in the other thread (linked in post) I can't give you a concrete timeline, however work is happening on this front and is being done to resolve these sorts of things. It is important to stress that Fusion is a platform with very different "vertical teams" (mfg, modeling, electronics, etc) internally and externally. ...Each trying to ensure their users get the best experience while also ensuring they can find the software familiar anytime you explore other areas. I dont think anyone expected this to take much time given their use-case, but each user-persona has a somewhat different "ask" of those Fusion 360 vertical teams and as an end to end Platform, we wanted to examine each unique use-case to understand the implications.
Fusion's origins are no doubt 3D modeling and most other workspaces in Fusion are downstream of that. Yet an electronics user authors a completely new set of base-data and has a completely different intent / workflow, until they intersect with 3D & mechanical modeling / ID & CAD-CAM-CAE for MCAD. Someone interested in manufacturing may want to start with a model they had open previously, could be the same in PCB design, but perhaps not. An ME may want to start with the assembly? The parts + assembly? Pushing this flexibility on the user is easy, but comes with the cost of complexity. Easy to do, hard to explain, slows everyone down... And I know this sounds like a lame excuse, but I am just hoping to communicate that we hear you and we do care about getting these things "right". If there is someone to blame it is guys like me who are picky about the result and meddle to ensure we dont screw things up for anyone else.
That said...(tlDr;)
- We are working on a 'First Launch' experience that will be geared for each of the user personas but chose NOT to introduce anything "new" until we had this worked out and each team is looking after their users' interests.
- We want to avoid changing the workflow for anyone time and time again.
- We also dont want to impact one user positively and negatively impact another. I know this seems like an 'easy' change but we are trying to balance the changes with the frequency / severity of disruption. It is coming but it is going to take a bit longer to finalize.
The university use-case is a good one because this also raises questions of "what if this isn't 'my' computer...does the SW come up with the previous model? Does it come up clean? Does it load the last student's schematic and PCB file? Should Student A ever be able to see Student B's data? What if they are in the same class and the team (in Fusion) is defined at the class / semester / syllabus level?" ...This is something having taught, I had a lot of concerns about. Classrooms are a mix of collaboration followed by isolation / examination. ...All this to say that I fully agree with you in spirit - we could have communicated with you better, but it's a bit of Bloom's Taxonomy -- we have gathered information, we wrote code, weren't completely happy with it...evaluate, feed that back into the machine and iterate until we are satisfied. This is FAR easier with feature development than with Platform changes. @jorge_garcia
Best regards,
matt - Autodesk