> Where does the 'Installable' part of IIA come from? It comes from "locally installed". The idea is that users are comfortable with the concept of downloading and installing applications, both to their desktop as well as to mobile devices. The web isn't the only way to build and deploy cross-platform content and functionality - Pivot (and other platforms like it) are a great alternative.
> To me, the term suggests that the application would undergo an installation > process over and above downloading a some jars & potentially setting the > classpath. It might. For the best user experience, it probably should. There are tools that can be used to help make this experience more seamless for Java apps. > Also the 'Internet' part suggests that Pivot contains some substantial code > to perform Internet based tasks. Is this really the case? I haven't worked > with any of the web/web server classes yet, so honestly don't know. Yes, the web query libraries (for both the client and server) make consuming web-based data (esp. JSON, XML, and CSV) very easy. > Obviously Pivot *can* be used to write connected applications, but in much > the same way it *could* be used to write just about any time of application. True, but non-connected applications aren't generally very interesting. :-) > Perhaps your text should mention that the same application is portable and > can be run on a desktop or mobile device directly or through a browser. It does say "cross-platform" - but saying that they can be deployed to a mobile device isn't currently accurate. I'm hoping we can support that for Pivot 3.0. > Sorry that I can't be more constructive right now! I'll think it over a bit > more and get back to you with anything useful. Sounds good!
