This forces them to make sure it is a usable UI and that it is intuitive and natural in terms of its interaction. For any new capabilities that they want to put into Shapr3D, they have to have five successful live user tests before those features go in to the app. They have 10 live tests of that prototype per week. On a weekly basis, they have a new prototype. They really focused on creating a polished UI. The thing that I guess surprised me and makes me think this might be a little bit different is their development and deployment capabilities. Shapr3D Development and Deployment Capabilities It is an app that you download onto your iPad Pro. It uses a D-Cubed for constraint management for sketches and even with the direct modeling capabilities that it has. This means it uses Parasolid’s modeling kernel. The other thing is that it uses the Siemens stack. It shows you the simple capabilities first and exposes advanced stuff through multi-touch gestures, which is a fairly efficient way to get up to speed and actually be efficient with the tool itself. But it has an extremely short learning curve because it uses a very different interface. What does that mean? Today, it runs on an iPad Pro and you actually use an Apple pen with it and multi-touch gestures.
0 kommentar(er)
