Best practices for controlling flow data when moving to different activities flow and coming back
I have this situation where the user moves from the home page(it has many sections: gaming, cooking, technology, etc). When moving from home page activity to gaming, I am passing account information to gaming activity. From gaming activity then I have a flowdata(using singleton I am saving temporary data into a class) where I save information necessary to go to navigate to different game types such as action. Once I am in action section I retrieve data from previous flowdata and move to another activity where I can select the specific game. Finally I go to the pay activity and then have to come back to my section "gaming" not the homepage.
My problem is when navigating back to gaming activity the account information(which home page passed it to gaming activity) is gone(null) as activity called onDestroy().
My solution is to have a class SectionFlowControl, this class will have an object flowdata which will save at first the account data passed from homepage to this activity. As I move to different sections I will save the information needed to move to the selected sections such as gaming. Once I am done with gaming flow(paid the game) I will clear sensitive information and go to SectionFlowControl which will then take me to the respective section such as gaming, technology, everything saved through the section will be cleared but the account information and data needed to send to the sections.
Is this the right approach or is there something better? What would be the best practices to move temporary data when we have many flows?
android software-design edited Nov 11 at 23:32
Mark Keen
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
add a comment |
I have this situation where the user moves from the home page(it has many sections: gaming, cooking, technology, etc). When moving from home page activity to gaming, I am passing account information to gaming activity. From gaming activity then I have a flowdata(using singleton I am saving temporary data into a class) where I save information necessary to go to navigate to different game types such as action. Once I am in action section I retrieve data from previous flowdata and move to another activity where I can select the specific game. Finally I go to the pay activity and then have to come back to my section "gaming" not the homepage.
My problem is when navigating back to gaming activity the account information(which home page passed it to gaming activity) is gone(null) as activity called onDestroy().
My solution is to have a class SectionFlowControl, this class will have an object flowdata which will save at first the account data passed from homepage to this activity. As I move to different sections I will save the information needed to move to the selected sections such as gaming. Once I am done with gaming flow(paid the game) I will clear sensitive information and go to SectionFlowControl which will then take me to the respective section such as gaming, technology, everything saved through the section will be cleared but the account information and data needed to send to the sections.
Is this the right approach or is there something better? What would be the best practices to move temporary data when we have many flows?
android software-design edited Nov 11 at 23:32
Mark Keen
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
add a comment |
I have this situation where the user moves from the home page(it has many sections: gaming, cooking, technology, etc). When moving from home page activity to gaming, I am passing account information to gaming activity. From gaming activity then I have a flowdata(using singleton I am saving temporary data into a class) where I save information necessary to go to navigate to different game types such as action. Once I am in action section I retrieve data from previous flowdata and move to another activity where I can select the specific game. Finally I go to the pay activity and then have to come back to my section "gaming" not the homepage.
My problem is when navigating back to gaming activity the account information(which home page passed it to gaming activity) is gone(null) as activity called onDestroy().
My solution is to have a class SectionFlowControl, this class will have an object flowdata which will save at first the account data passed from homepage to this activity. As I move to different sections I will save the information needed to move to the selected sections such as gaming. Once I am done with gaming flow(paid the game) I will clear sensitive information and go to SectionFlowControl which will then take me to the respective section such as gaming, technology, everything saved through the section will be cleared but the account information and data needed to send to the sections.
Is this the right approach or is there something better? What would be the best practices to move temporary data when we have many flows?
android software-design edited Nov 11 at 23:32
Mark Keen
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
I have this situation where the user moves from the home page(it has many sections: gaming, cooking, technology, etc). When moving from home page activity to gaming, I am passing account information to gaming activity. From gaming activity then I have a flowdata(using singleton I am saving temporary data into a class) where I save information necessary to go to navigate to different game types such as action. Once I am in action section I retrieve data from previous flowdata and move to another activity where I can select the specific game. Finally I go to the pay activity and then have to come back to my section "gaming" not the homepage.
My problem is when navigating back to gaming activity the account information(which home page passed it to gaming activity) is gone(null) as activity called onDestroy().
My solution is to have a class SectionFlowControl, this class will have an object flowdata which will save at first the account data passed from homepage to this activity. As I move to different sections I will save the information needed to move to the selected sections such as gaming. Once I am done with gaming flow(paid the game) I will clear sensitive information and go to SectionFlowControl which will then take me to the respective section such as gaming, technology, everything saved through the section will be cleared but the account information and data needed to send to the sections.
Is this the right approach or is there something better? What would be the best practices to move temporary data when we have many flows?
android software-design android software-design edited Nov 11 at 23:32
Mark Keen
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
edited Nov 11 at 23:32
Mark Keen
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
edited Nov 11 at 23:32
Mark Keen
4,64441742
edited Nov 11 at 23:32
Mark Keen
4,64441742
edited Nov 11 at 23:32
Mark Keen
4,64441742
4,64441742
asked Nov 11 at 22:40
Albertano Santacruz
504
asked Nov 11 at 22:40
Albertano Santacruz
504
asked Nov 11 at 22:40
Albertano Santacruz
504
504
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If it's not a large amount of data I would store the relevant information using SharedPreferences.
I would store them on the Home Page and retrieve them in all the other Activities. This way you avoid the need to send and re-send the same info across them
answered Nov 12 at 2:46
sebasira
644521
add a comment |
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%2f53253965%2fbest-practices-for-controlling-flow-data-when-moving-to-different-activities-flo%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If it's not a large amount of data I would store the relevant information using SharedPreferences.
I would store them on the Home Page and retrieve them in all the other Activities. This way you avoid the need to send and re-send the same info across them
answered Nov 12 at 2:46
sebasira
644521
add a comment |
If it's not a large amount of data I would store the relevant information using SharedPreferences.
I would store them on the Home Page and retrieve them in all the other Activities. This way you avoid the need to send and re-send the same info across them
answered Nov 12 at 2:46
sebasira
644521
add a comment |
If it's not a large amount of data I would store the relevant information using SharedPreferences.
I would store them on the Home Page and retrieve them in all the other Activities. This way you avoid the need to send and re-send the same info across them
answered Nov 12 at 2:46
sebasira
644521
If it's not a large amount of data I would store the relevant information using SharedPreferences.
I would store them on the Home Page and retrieve them in all the other Activities. This way you avoid the need to send and re-send the same info across them
answered Nov 12 at 2:46
sebasira
644521
answered Nov 12 at 2:46
sebasira
644521
answered Nov 12 at 2:46
sebasira
644521
answered Nov 12 at 2:46
sebasira
644521
644521
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%2f53253965%2fbest-practices-for-controlling-flow-data-when-moving-to-different-activities-flo%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
