What is the best approach to store logged in user details in MVVM?
I have an E-commerce android app in which the user should be signed in to perform some functions (Adding product to cart, Marking product as favorites etc) and there are some function which would work without signing in. (Searching products)
So whenever an user tries to perform a function which requires signing, I have to switch to an activity to sign-in the user.
Users are signed in using Firebase authentication (Google provider).
What is the best approach (in MVVP) to store user details (like Firebase user id, name etc) to be accessible in the app globally (in all required activities).
Possible solution (I came up with):
1. One ViewModel to store logged in user details, which is accessed in all required activities. (Using this as of now)
2. To use shared preferences to store user details.
3. Using global data variable by using a class extending Application.
If any alternate approach is better than specified ones, please do mention !
android mvvm asked Nov 16 '18 at 19:36
AbhiAbhi
13013
add a comment |
I have an E-commerce android app in which the user should be signed in to perform some functions (Adding product to cart, Marking product as favorites etc) and there are some function which would work without signing in. (Searching products)
So whenever an user tries to perform a function which requires signing, I have to switch to an activity to sign-in the user.
Users are signed in using Firebase authentication (Google provider).
What is the best approach (in MVVP) to store user details (like Firebase user id, name etc) to be accessible in the app globally (in all required activities).
Possible solution (I came up with):
1. One ViewModel to store logged in user details, which is accessed in all required activities. (Using this as of now)
2. To use shared preferences to store user details.
3. Using global data variable by using a class extending Application.
If any alternate approach is better than specified ones, please do mention !
android mvvm asked Nov 16 '18 at 19:36
AbhiAbhi
13013
1) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extendSupplier<T>interface for abstraction. For alternates you could always store user details using firebase.
– Mark Keen
Nov 16 '18 at 19:45
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06
add a comment |
I have an E-commerce android app in which the user should be signed in to perform some functions (Adding product to cart, Marking product as favorites etc) and there are some function which would work without signing in. (Searching products)
So whenever an user tries to perform a function which requires signing, I have to switch to an activity to sign-in the user.
Users are signed in using Firebase authentication (Google provider).
What is the best approach (in MVVP) to store user details (like Firebase user id, name etc) to be accessible in the app globally (in all required activities).
Possible solution (I came up with):
1. One ViewModel to store logged in user details, which is accessed in all required activities. (Using this as of now)
2. To use shared preferences to store user details.
3. Using global data variable by using a class extending Application.
If any alternate approach is better than specified ones, please do mention !
android mvvm asked Nov 16 '18 at 19:36
AbhiAbhi
13013
I have an E-commerce android app in which the user should be signed in to perform some functions (Adding product to cart, Marking product as favorites etc) and there are some function which would work without signing in. (Searching products)
So whenever an user tries to perform a function which requires signing, I have to switch to an activity to sign-in the user.
Users are signed in using Firebase authentication (Google provider).
What is the best approach (in MVVP) to store user details (like Firebase user id, name etc) to be accessible in the app globally (in all required activities).
Possible solution (I came up with):
1. One ViewModel to store logged in user details, which is accessed in all required activities. (Using this as of now)
2. To use shared preferences to store user details.
3. Using global data variable by using a class extending Application.
If any alternate approach is better than specified ones, please do mention !
android mvvm android mvvm asked Nov 16 '18 at 19:36
AbhiAbhi
13013
asked Nov 16 '18 at 19:36
AbhiAbhi
13013
edited Nov 16 '18 at 20:00
Abhi
asked Nov 16 '18 at 19:36
AbhiAbhi
13013
asked Nov 16 '18 at 19:36
AbhiAbhi
13013
asked Nov 16 '18 at 19:36
AbhiAbhi
13013
13013
1) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extendSupplier<T>interface for abstraction. For alternates you could always store user details using firebase.
– Mark Keen
Nov 16 '18 at 19:45
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06
add a comment |
1) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extendSupplier<T>interface for abstraction. For alternates you could always store user details using firebase.
– Mark Keen
Nov 16 '18 at 19:45
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06
1) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extend
Supplier<T> interface for abstraction. For alternates you could always store user details using firebase.– Mark Keen
Nov 16 '18 at 19:45
1) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extend
Supplier<T> interface for abstraction. For alternates you could always store user details using firebase.– Mark Keen
Nov 16 '18 at 19:45
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53344299%2fwhat-is-the-best-approach-to-store-logged-in-user-details-in-mvvm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53344299%2fwhat-is-the-best-approach-to-store-logged-in-user-details-in-mvvm%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) Authentication details don't belong in a view model - as the name suggests 2) Is this secure enough i.e rooted phones 3) If it needs to be accessible for the lifetime of the application class then this is the correct scope - suggest you extend
Supplier<T>interface for abstraction. For alternates you could always store user details using firebase.– Mark Keen
Nov 16 '18 at 19:45
@MarkKeen I want to store details like name ,id etc which don't require much security (I had mistakenly used "authentication details" instead of "user details").
– Abhi
Nov 16 '18 at 19:56
Then I'd suggest shared preferences if it's non sensitive information, which you can still implement a supplier class for as it's just implementation changes only.
– Mark Keen
Nov 16 '18 at 20:06