Should you use an Image View for a solid background color, or change the background from the view?
up vote
0
down vote
favorite
When putting a solid background color should you use an image for more accessibility or just change the color in the view settings?
NOTE: I need to change the background later on in the app.
ios
edited Nov 11 at 16:09
rmaddy
236k27307374
asked Nov 11 at 15:23
alvileg
31
add a comment |
up vote
0
down vote
favorite
When putting a solid background color should you use an image for more accessibility or just change the color in the view settings?
NOTE: I need to change the background later on in the app.
ios
edited Nov 11 at 16:09
rmaddy
236k27307374
asked Nov 11 at 15:23
alvileg
31
1
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When putting a solid background color should you use an image for more accessibility or just change the color in the view settings?
NOTE: I need to change the background later on in the app.
ios
edited Nov 11 at 16:09
rmaddy
236k27307374
asked Nov 11 at 15:23
alvileg
31
When putting a solid background color should you use an image for more accessibility or just change the color in the view settings?
NOTE: I need to change the background later on in the app.
ios
ios
edited Nov 11 at 16:09
rmaddy
236k27307374
asked Nov 11 at 15:23
alvileg
31
edited Nov 11 at 16:09
rmaddy
236k27307374
asked Nov 11 at 15:23
alvileg
31
edited Nov 11 at 16:09
rmaddy
236k27307374
edited Nov 11 at 16:09
rmaddy
236k27307374
edited Nov 11 at 16:09
rmaddy
236k27307374
236k27307374
asked Nov 11 at 15:23
alvileg
31
asked Nov 11 at 15:23
alvileg
31
asked Nov 11 at 15:23
alvileg
31
31
1
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46
add a comment |
1
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46
1
1
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
If you have to change the background image/color dynamically, it would mostly be lighter on the app size and view (though the adverse effect might be insignificant) to manage background color of a UIView, than have an additional UIImageView loading up your background image from the assets.
You might also have to keep multiple colored assets in the bundle to account for the dynamicity, if you are to use image assets for handling the same.
If you are targeting for iOS 11.0+, you should surely go with using colors, as you can use color asset to manage your colors at a centalized location, which can be used directly from both the Interface builder and code.
answered Nov 11 at 15:39
D V
31329
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
If you have to change the background image/color dynamically, it would mostly be lighter on the app size and view (though the adverse effect might be insignificant) to manage background color of a UIView, than have an additional UIImageView loading up your background image from the assets.
You might also have to keep multiple colored assets in the bundle to account for the dynamicity, if you are to use image assets for handling the same.
If you are targeting for iOS 11.0+, you should surely go with using colors, as you can use color asset to manage your colors at a centalized location, which can be used directly from both the Interface builder and code.
answered Nov 11 at 15:39
D V
31329
add a comment |
up vote
0
down vote
accepted
If you have to change the background image/color dynamically, it would mostly be lighter on the app size and view (though the adverse effect might be insignificant) to manage background color of a UIView, than have an additional UIImageView loading up your background image from the assets.
You might also have to keep multiple colored assets in the bundle to account for the dynamicity, if you are to use image assets for handling the same.
If you are targeting for iOS 11.0+, you should surely go with using colors, as you can use color asset to manage your colors at a centalized location, which can be used directly from both the Interface builder and code.
answered Nov 11 at 15:39
D V
31329
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
If you have to change the background image/color dynamically, it would mostly be lighter on the app size and view (though the adverse effect might be insignificant) to manage background color of a UIView, than have an additional UIImageView loading up your background image from the assets.
You might also have to keep multiple colored assets in the bundle to account for the dynamicity, if you are to use image assets for handling the same.
If you are targeting for iOS 11.0+, you should surely go with using colors, as you can use color asset to manage your colors at a centalized location, which can be used directly from both the Interface builder and code.
answered Nov 11 at 15:39
D V
31329
If you have to change the background image/color dynamically, it would mostly be lighter on the app size and view (though the adverse effect might be insignificant) to manage background color of a UIView, than have an additional UIImageView loading up your background image from the assets.
You might also have to keep multiple colored assets in the bundle to account for the dynamicity, if you are to use image assets for handling the same.
If you are targeting for iOS 11.0+, you should surely go with using colors, as you can use color asset to manage your colors at a centalized location, which can be used directly from both the Interface builder and code.
answered Nov 11 at 15:39
D V
31329
answered Nov 11 at 15:39
D V
31329
answered Nov 11 at 15:39
D V
31329
answered Nov 11 at 15:39
D V
31329
31329
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250177%2fshould-you-use-an-image-view-for-a-solid-background-color-or-change-the-backgro%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I don't understand the question. If you need to change the view's background color you just have to use its property. An image is heavier to load, to process and to display on the screen.
– Yannick Loriot
Nov 11 at 15:38
@YannickLoriot I believe that the OP is talking about having multiple views in multiple screens with the same color, which can be quickly switched to another color (which would be a bit tedious if only the Attributes inspector is being used to set the background color).
– D V
Nov 11 at 15:42
@DV you can always copy paste a view in storyboard (keeping the bg color) and set its constraints as needed in the current context. Using an image for that seems wasteful
– giorashc
Nov 11 at 15:44
@giorashc Of course, and that is the same effort is the OP is talking about, if I'm right. To me, it looked like the OP wanted to identify the most effortless/best way to handle this case. Copy-pasting and settings the constraints again require you to do this for each of the items you need to change, which I would not personally suggest.
– D V
Nov 11 at 15:46