JNetStart facilitates launching Java Swing applications deployed on a remote server without installing or downloading the application component files. The technology narrows the gap between the web browser and Swing by making large client applications instantly available to the user and providing a web style experience in the startup process. One can see JNetStart as reinventing a web for Java Swing. The developer provides Swing classes in order to create the UI rather than HTML, CSS and JavaScript. The client application can be comprised of multiple jar files and the point of entry is a regular JApplet. There is no special API to implement. JNetStart uses a RemoteClassLoader optimized for Swing in order to load the client classes on demand, just as when the classes would be loaded if the client was run from the local disk. For best results the client should lazy load the application components when first used rather than in advance. The Swing developer should think web rather than desktop when developing applets deployed on JNetStart. The Swing clients can be launched in a specialized Swing browser that looks and feels like a regular web browser and with plugins for IE and Firefox. Java 6 is deployed with the Swing browser and a separate installation is not required making this method an excellent solution for deploying Java on the client. The installation package contains a modified version of SwingSet2 that loads the demos screens when the user clicks the corresponding toolbar button for the first time. The Java2D demo is also deployed with the installation package and this time only one line of code performing a class loader type conversion had to change. Please visit our website for more information. http://www.accendia.com