Android xml vs java layouts performance

Android SDK offers to developers to write layouts in xml files or directly in java code. I have read about it and everyone says that xml are easier to maintain and simplyer to write, but they are static. Otherwise java layout are dynamic, but no one comments performance issues. The only one thing which I found about performance was nesting layout have negative impact of performance. Instead of writing nested layout it’s better to make custom one. So far so good ;).

What about layout design? xml or java code? How are xml files parsed my android, at runtime or compile time? Even if they are parsed at compile time, they should be used in runtime. So which will be faster to declare RelativeLayout in xml or to declare it in onCreate method?

  • How to embed i-jetty server into android application?
  • Call requires API level 23 (current min is 14): android.app.Activity#requestPermissions,checkSelfPermission
  • Using audioSessionId value to instantiate AudioFx class?
  • How to use server sent events (SSE) in android?
  • How can I move an image from one point to another using Android Canvas
  • Disable SSL as a protocol in HttpsURLConnection
  • Related posts:

    Datepicker: How to popup datepicker when click on edittext
    Open application after clicking on Notification
    Remove all fragments from ViewPager populated by FragmentStatePagerAdapter
    Missing “<sdk>/extras/google/google_play_services/libproject” fold...
    How to handle code when app is killed by swiping in android?
    “Your APP_BUILD_SCRIPT points to an unknown file: ./jni/Android.mk”
  • Using Call Enqueue function in Retrofit
  • Google IO Rest design pattern, Finished ContentProvider and stuck now
  • Detect Android app upgrade and set Application class boolean for show/hide of EULA
  • What is the semantics of the return value of the Android logging functions (e.g. Log.v() )?
  • How to use Google Login API with Cordova/Phonegap
  • ClassCastException: android.widget.EditText
  • 3 Solutions collect form web for “Android xml vs java layouts performance”

    A layout defines the visual structure for a user interface, such as the UI for an activity or app widget. You can declare a layout in two ways:

    • Declare UI elements in XML. Android provides a straightforward XML
      vocabulary that corresponds to the View classes and subclasses, such
      as those for widgets and layouts.

    • Instantiate layout elements at runtime. Your application can create
      View and ViewGroup objects (and manipulate their properties)
      programmatically.

    The Android framework gives you the flexibility to use either or both of these methods for declaring and managing your application’s UI. For example, you could declare your application’s default layouts in XML, including the screen elements that will appear in them and their properties. You could then add code in your application that would modify the state of the screen objects, including those declared in XML, at run time.

    The ADT Plugin for Eclipse offers a layout preview of your XML — with the XML file opened, select the Layout tab.

    You should also try the Hierarchy Viewer tool, for debugging layouts — it reveals layout property values, draws wireframes with padding/margin indicators, and full rendered views while you debug on the emulator or device.

    The layoutopt tool lets you quickly analyze your layouts and hierarchies for inefficiencies or other problems.

        The advantage to declaring your UI in XML is that it enables you to better separate the 
    presentation of your application from the code that controls its behavior. Your UI descriptions are
    external to your application code, which means that you can modify or adapt it without having to
    modify your source code and recompile. For example, you can create XML layouts for different screen
    orientations, different device screen sizes, and different languages. Additionally, declaring the
    layout in XML makes it easier to visualize the structure of your UI, so it's easier to debug 
    problems. 
    

    When you compile your application, each XML layout file is compiled into a View resource. You should load the layout resource from your application code, in your Activity.onCreate() callback implementation. Do so by calling setContentView(), passing it the reference to your layout resource in the form of:

    I think its too much just visit this link http://developer.android.com/guide/topics/ui/declaring-layout.html and get more information..

    One primary factor to decide where to declare a UI component is it’s behavior during the app life cycle. If it’s static I’d declare all attributes needed in XML, if it changes according to the user interaction I’d have to implement it in the activity.

    I would go for XML as much as possible for the benefits mentions above like coherence, better management for various screen sizes, localization, resource management etc.,

    It is not much of a difference performance wise because your resources xml file will also be precompiled using aapt tools.So the XML conversion will happen to source resources files and alongwith the java source files they will be compiled to Java class files . So it is also logical that performance should be around same only because ultimately both will be compiled and memory for both will be allocated at run time. Also i checked with my sample application that making similar views via XML and via Java and while profiling them i found that the rendering of Views takes around same time. 🙂

    Android Babe is a Google Android Fan, All about Android Phones, Android Wear, Android Dev and Android Games Apps and so on.