Breaking it up into multiple posts:
Hi,
We are considering using blueprint. it looks good and we tested a very quick page. we face big issues with device presentation issue for our site and need a solid framework. OK, so blueprint is not a framework - its a platform with many advantages and upside potiential. BUT due to the lack of information and no real solid review OR a large number of sites using it i have a few direct questions:
I can answer some of these.
1) why is blueprint not popular compared to something like phonegap?? (ok not directly comparable but an example to illustrate point!)
It's really a business decision as to what phones you want to support. Phonegap and other libraries are just libraries to enable cross platform development on more modern devices (iPhone, Android, WebOS). While I can't say much right now, you'll see a competitor from us in that space in the future. Even when that does happen, Blueprint will continue to exist because it serves as a complete platform for almost
all devices. Blueprint will generate markup that works on a outdated Motorola V3 all the way up to iPhone OS 4. So really it's just a question of "What phones do I want to support?". If you want to focus on just the most modern, cutting edge devices then a library will definitely give you more flexibility. If you need to support Blackberrys, Nokias, etc., then you will probably want to use Blueprint.
2) what are the limitations?
Because of the number of devices we support and their limitations, we have to enforce limitations in the language. You must use our elements and you will have limited options on styling and interaction. Keep in mind, though, we have already done the work on getting the display halfway decent on low end devices which I can tell you personally is not an easy task.
3) do i loose any control? If yes of what??
See last point. I would suggest trying out one of the example applications.