Scribd Logo
Upload

Welcome to Scribd!

  • 0 views

    WIA2007_T5

    Uploaded by

    u2102186

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    WIA2007_T5

    Uploaded by

    u2102186
    0 views2 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    0 views2 pages

    WIA2007_T5

    Uploaded by

    u2102186

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    WIA2007 MAD Tutorial 5 Sem 1, 24/25

    WIA2007 Mobile Application Development


    Semester 1, Session 2024/2025
    Tutorial 5 (ViewGroup)

    1. In your opinion, which viewgroup (layout) is more…


    a. Flexible?
    - Constraint layout
    b. Easy (shorter development time)?
    - Linear layout
    c. Adaptive / Dynamic?
    - Constraint layout

    Provide ONE(1) justification for each of your answers in (a) to (c) above.

    2. Choose any THREE (3) viewgroup discussed in Lecture 4, and provide TWO (2)
    advantages and TWO (2) disadvantages for each of the viewgroup.
    Layout Pros Cons
    Constraint • Flexibility • Complex to use when
    • Not a nested layout designing simple UI
    Linear • Shorter development • Cannot create complex
    time layout
    • Faster processing time • Often requires nesting
    Relative • Positioning • More challenging become
    widgets/objects relative you need to relate
    each other everything
    • Better performance – • Performance not as good
    reduces the need of as constraint layout
    nested layout

    3. Debate over the use of nested layout in your mobile app UI.
    Pros Cons
    Nested layout allow for intricate design Can lead to slower performance and higher
    structure and alignments memory usage
    Each component can be encapsulated, A straightforward layout can achieve same
    making it easier to reuse and maintain parts result with better performance
    of layout individually
    Easy to manage elements in a hierarchical When hierarchy grows deeper, maintaining
    way layout become more challenging

    4. The navigation chart is a diagram that we used to illustrate the activity flows in the
    mobile application. For example, activity A to activity B, activity B to activity C and
    D, etc. The purpose of having a navigation chart is to ensure the following:

    1
    WIA2007 MAD Tutorial 5 Sem 1, 24/25

    (1) To prepare for the navigation methods (is it using a button? Navigation drawer?
    Navigation bar? Or others?)
    (2) To create a seamless browsing experience for the user (the navigation from one
    activity to another should be logical)
    (3) To ensure that there is no dead / isolated activity (viz., unreachable activity).

    Let’s draw a navigation chart by using UMTouch as our reference subject. The full
    navigation chart for UMTouch is very complex because it contains many activities.
    Hence, for your navigation chart, you only need to draw up to 10 activities with a
    minimum of 3 navigation levels.

    Tips: Refer to the slides in the lecture notes (Lecture 4, Slides 25-29) to see the examples
    of the navigation chart. Note that, the navigation chart can be of different formats (e.g.,
    different color, different arrow, use UI draft instead of the activity name), and you can
    use any tools such as Microsoft Word, PowerPoint, Lucid chart, pen-pencil, etc. to
    draw it.

    Submission

    Submit Q1-Q4 to the submission link provided in Spectrum before the next Tutorial session.
    Bring your answer for discussion.

    You might also like