
I'm not a developer and have limited coding experience, but I've been able to prototype and deploy a relatively complex UI with Storyboard. The platform is intuitive and user friendly. It's also feature rich, which gives you the best of both worlds. We're planning on leveraging Crank's development services to build our final UI, but it's really nice to prototype and get up and running quickly on our own.
We like Storyboard's cross-platform capabilities. Our first UI iteration is running on a Raspberry PI and we plan on migrating to a custom control board with a MPU in the near future.
The team at Crank have been very helpful and responsive throughout. Review collected by and hosted on G2.com.
Crank's online videos and documentation is pretty extensive. Since I'm not a developer, I would benefit from some "best practices" guidelines since there are often many ways to accomplish the same objective, but there are advantages to following certain approaches. Review collected by and hosted on G2.com.
Crank Storyboard was created by designer's for developers! At some stage in your UI Delivery Pipeline the non-technical design team is going to engage directly with the technical development team. Crank is the abstraction layer that facilitates that engagement and brings feature rich UI's as only imaged by designers to the embedded platform as only realised by developers.
From 1+ year experience as a software developer embedded into a design team, designers can create world class UI's in their designtools of choice ( photoshop, sketch, etc ) and then import directly into Crank. The designers then hand this Crank Project ( which now exists as a collection of imported UI Screens ) to the User Experience (UX) and Interaction team which bring the UI to life by binding interactive events (click, swipe, animations, etc ) to the screens. This is achieved entirely thought the Crank Storyboard interface without needing a single line of code.
The UX Team then hand this over to me, the software developer, which maps those click and swipe events to Storyboard IO Messages which get sent to the product.
The deployment to Embedded Target is one of the easiest I've expereienced in my 10+ years as embedded software developer.
The support from Crank in scoping, troubleshooting and integrating their product is second to none. Review collected by and hosted on G2.com.
I wish there was more activity and an active community in the Crank hosted forums and knowledge sharing platforms. This is made Review collected by and hosted on G2.com.
The support team is awesome. Whenever I have an issue, I contact support and with the very little information they get from me, they respond always very fast with information on how to fix it or even with a new engine.
Our product uses a low range processor without an operating system, and the portability is definitely the biggest feature of Crank. Our GUI designers can focus on the design only in the simulator, while the hardware engineers can focus on the embedded side. Review collected by and hosted on G2.com.
Not all features are available for my processor, which makes total sense, but sometimes it's hard to figure out what will work and what not. The simulator could use a feature that prevents the GUI designer from adding something that will not work on my target (or give a warning). Also, more documentation for my target would be useful. Review collected by and hosted on G2.com.
Storyboard Designer has a great set of features from 3D capabilities, back-in integration, animation and graphic capabilities. Review collected by and hosted on G2.com.
The interfaces and workflow does take getting use to but the learning curve is short. Review collected by and hosted on G2.com.
Using Photoshop to create the real UI and turn it into to a working UI was very powerful in convincing management about new operations and added features of our prouduct. Storyboard provided the quick UI idea to functional UI. With the added naming conventions the conversion from design to operating UI was time efficient. Review collected by and hosted on G2.com.
No software is perfect. The link between backend and front end was likely the weakest point. The data formatting to get it UI for more than base numbers, did require some work. It was not bad, just not perfect. Review collected by and hosted on G2.com.