The Android GUI system is far simpler that Swing. It's more like a cleaned up AWT. It still has a pretty good stable of nifty widgets, but they certainly are not the same widgets you find in Swing-based UIs.
The constraints on a mobile app GUI are, at least at the moment, different than those on a desktop app. Although many of the constructs you know and love, from Swing (single-thread, event queue, callbacks, view-hierarchy), will be entirely familiar, it is worth your while to make sure you understand how the UI fits in with the Activity lifecycle, before you go porting a Swing app, directly. -blake Programming Android, FTW! http://oreilly.com/catalog/0636920010364 On Sep 10, 12:40 pm, Aneem Talukder <aneemtaluk...@gmail.com> wrote: > Dear Community, > > I have just recently started coding for the android platform. Today, > in fact :) > > I know java pretty well and use the swing frameworks for my GUI > development. Is android compatible with swing, or is there a more > appropriate api for graphics? > > Thanks in advance! > Aneem -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en