|Portability: Pure Java design provides for great advantage for portability - works more consistently across many platforms
Portability: use of native peers creates platform specific limitations. Some components may not function as expected in different platforms.
|Features: Swing supports a wider range of features including icons and pop-up tool-tips for components.||Features: AWT components do not support features like icons and tool-tips.|
|Look and Feel: The plug-gable look and feel lets one design a single set of GUI components that can automatically have the look and feel of any OS platform (Microsoft Windows, Solaris, Macintosh, etc.). It also makes it easier to make global changes to your Java programs that provide greater accessibility||Look and Feel: AWT components more closely reflect the look and feel of the OS they run on.|
|Applet Portability: Most Web browsers do not include the Swing classes, so the Java plugin must be use||Applet Portability: most Web browsers support AWT classes so AWT applets can run without the Java plugin.|
|Speed: Comparatively slower||
Speed: use of native peers speeds component performance.