MENU
"Splitting UI elements per functionality" is a best practice to avoid monolithic mobile UI modules? Which of the below is not a best practice?
Suggested Answer: C
Get Premium Architecture-Specialist-11 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
JA
Jaclyn
11 months ago
Wait, CSS only in the theme module? That seems limiting!
MO
Moira
11 months ago
D is the way to go for modularity!
TI
Tien
11 months ago
C sounds right, but is it really that much better?
MI
Michell
12 months ago
I think E makes more sense for organization.
TR
Tricia
12 months ago
A is definitely a best practice!
AN
Angella
12 months ago
I vaguely remember something about screens and placeholders being a good practice, but I can't quite remember if that's true for this question.
RO
Rodney
1 year ago
I feel like the answer might be E, since we talked about keeping CSS centralized in the theme module during our last practice session.
RE
Reena
1 year ago
I think putting CSS in blocks might actually help with performance, but I can't recall if that's considered a best practice or not.
DA
Danica
1 year ago
I remember we discussed how splitting UI elements can improve maintainability, but I'm not sure which option is the odd one out here.
BE
Bettye
1 year ago
I'm pretty confident about this one. Option E, putting all CSS in the mobile theme module, is not a best practice. We want to keep CSS close to the UI elements it styles, not centralized in a single module.
MO
Mona
1 year ago
Okay, I've got this. Splitting UI elements by functionality is a best practice to avoid monolithic modules. The key is to group blocks into independent functional modules with their own lifecycles. That way, changes in one area don't impact the whole UI.
JO
Joni
1 year ago
Hmm, this is a tricky one. I'm not entirely sure about the difference between putting CSS in blocks vs. screens. I'll need to review my notes on modular UI design to make sure I choose the right answer.
ME
Mertie
1 year ago
This question seems to be testing our understanding of best practices for organizing mobile UI elements. I'll need to carefully read through the options and think about the pros and cons of each approach.
ST
Stefania
2 years ago
Wait, wait, wait. Option A with the 'Screens as layouts' thing? That's straight out of the UI design playbook. Gotta love it!
MO
Monte
2 years 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.
AL
Alex
2 years ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
ST
Stacey
2 years ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
JO
Joesph
2 years 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.
AN
Antione
2 years 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.
DO
Dorsey
2 years ago
User 2: Absolutely, grouping blocks in functional modules with independent life cycles is crucial for a clean and maintainable UI.
DO
Dominque
2 years ago
User 1: I agree, option D is definitely the best practice for splitting UI elements.
SH
Shenika
2 years ago
I believe putting CSS in blocks or screens is not a best practice. It can lead to performance issues.
JE
Jess
2 years ago
Hold up, what about option C? Putting CSS in blocks or screens for better performance? Sounds legit to me.
NO
Norah
2 years ago
Talia: Oh, I see. Thanks for clarifying that!
TA
Talia
2 years ago
User 3: Eulah is correct. CSS should be centralized in the mobile theme module for better management.
EU
Eulah
2 years ago
User 2: Really? I thought putting CSS in blocks or screens was a good idea for better performance.
AL
Allene
2 years ago
User 1: Option C is actually not a best practice. CSS should only be placed in the mobile theme module.
LY
Lynna
2 years ago
I agree. It helps to keep the code organized and makes it easier to maintain.
HA
Han
2 years ago
Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
RO
Rodrigo
2 years ago
User: Option E seems like a no-brainer, right? Putting all the CSS in one module is just asking for trouble.
EL
Elise
2 years ago
C) Put CSS in blocks or screens. Allows better performance and seamless screen transitions
WI
Willis
2 years ago
B) Include the Common flow and Menu artifacts
JI
Jin
2 years ago
A) Screens as layouts that have placeholders and load content from blocks. The blocks come from CW modules.
VI
Virgina
2 years ago
I think splitting UI elements per functionality is important for mobile UI design.