I'm curious of other experience using Sproutcore (particularly Sproutcore 2 since there has been a large refactor of code).
- How useful are the widgets in a rapid prototyping situation?
- Upon initial inspection, the state-model of Sproutcore records seems to be overly complex (ie, not very elegant). How does this design pattern work in the real world?
- If I build a webapp with Sproutcore, will it be easier to deploy this same app to mobile devices vs something like backbone.js?
The widgets are really useful. Your apps will not be very different if you use them with the same theme every time but I think it's ok for a demo to show customers during the Problem Interview phase.
I agree that the state model is a bit overly complex but if you go past the learning curve it can work well. Also there are ways to kind of bypass it and use an approach more similar to what Backbone/Spine does. There is a recent blog post by the SC team that shows you you can do that with 2.0 branch: http://blog.sproutcore.com/sproutcore-2-and-ajax/
It definitely helps your business plan, but I think it goes beyond just the business plan, it actually provides a process to align and direct your startup to success.