Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

OutSystems Exam Architecture-Specialist-11 Topic 4 Question 32 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 32
Topic #: 4
[All Architecture-Specialist-11 Questions]

"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Sharmaine at Nov 14, 2024, 08:09 AM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Stefania
2 months ago
Wait, wait, wait. Option A with the 'Screens as layouts' thing? That's straight out of the UI design playbook. Gotta love it!
upvoted 0 times
...
Monte
2 months ago
I'm feeling a bit lost here. Is option B about including the Common flow and Menu artifacts really a 'best practice'? Seems kinda vague to me.
upvoted 0 times
Alex
2 months ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
upvoted 0 times
...
Stacey
2 months ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
upvoted 0 times
...
...
Joesph
3 months ago
Nah, I think option D is the way to go. Grouping blocks in functional modules with independent life cycles? That's the key to a clean, maintainable UI.
upvoted 0 times
Antione
2 months ago
User 3: I think we're all on the same page here, option D is the way to go for avoiding monolithic mobile UI modules.
upvoted 0 times
...
Dorsey
2 months ago
User 2: Absolutely, grouping blocks in functional modules with independent life cycles is crucial for a clean and maintainable UI.
upvoted 0 times
...
Dominque
2 months ago
User 1: I agree, option D is definitely the best practice for splitting UI elements.
upvoted 0 times
...
...
Shenika
3 months ago
I believe putting CSS in blocks or screens is not a best practice. It can lead to performance issues.
upvoted 0 times
...
Jess
3 months ago
Hold up, what about option C? Putting CSS in blocks or screens for better performance? Sounds legit to me.
upvoted 0 times
Norah
2 months ago
Talia: Oh, I see. Thanks for clarifying that!
upvoted 0 times
...
Talia
3 months ago
User 3: Eulah is correct. CSS should be centralized in the mobile theme module for better management.
upvoted 0 times
...
Eulah
3 months ago
User 2: Really? I thought putting CSS in blocks or screens was a good idea for better performance.
upvoted 0 times
...
Allene
3 months ago
User 1: Option C is actually not a best practice. CSS should only be placed in the mobile theme module.
upvoted 0 times
...
...
Lynna
3 months ago
I agree. It helps to keep the code organized and makes it easier to maintain.
upvoted 0 times
...
Han
3 months ago
Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
upvoted 0 times
Rodrigo
3 months ago
User: Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
upvoted 0 times
...
Elise
3 months ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
upvoted 0 times
...
Willis
3 months ago
B) Include the Common flow and Menu artifacts
upvoted 0 times
...
Jin
3 months ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
upvoted 0 times
...
...
Virgina
3 months ago
I think splitting UI elements per functionality is important for mobile UI design.
upvoted 0 times
...

Save Cancel