Mixing
What is the best way to pass data or arguments between flutter app screens?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
In order to send an argument from one screen to the other I have to set this argument as a field in the widgets class. With many arguments being passed down to several widgets I think this might cause a problem for bigger applications.
What is the best way to pass data between screens efficiently?
user-interface architecture dart
flutter state edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
add a comment |
In order to send an argument from one screen to the other I have to set this argument as a field in the widgets class. With many arguments being passed down to several widgets I think this might cause a problem for bigger applications.
What is the best way to pass data between screens efficiently?
user-interface architecture dart
flutter state edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
use state management
– Ahmed
Jan 3 at 3:01
add a comment |
In order to send an argument from one screen to the other I have to set this argument as a field in the widgets class. With many arguments being passed down to several widgets I think this might cause a problem for bigger applications.
What is the best way to pass data between screens efficiently?
user-interface architecture dart
flutter state edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
In order to send an argument from one screen to the other I have to set this argument as a field in the widgets class. With many arguments being passed down to several widgets I think this might cause a problem for bigger applications.
What is the best way to pass data between screens efficiently?
user-interface architecture dart
flutter state user-interface architecture dart
flutter state edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
edited Jan 3 at 3:40
Oswin Noetzelmann
3,9881529
3,9881529
asked Jan 3 at 2:59
Salma.Salma.
2716
asked Jan 3 at 2:59
Salma.Salma.
2716
asked Jan 3 at 2:59
Salma.Salma.
2716
2716
use state management
– Ahmed
Jan 3 at 3:01
add a comment |
use state management
– Ahmed
Jan 3 at 3:01
use state management
– Ahmed
Jan 3 at 3:01
use state management
– Ahmed
Jan 3 at 3:01
add a comment |
1 Answer
1
active
oldest
votes
Typically the best way is to use app state management. You edit the state before switching routes and read the state on the new screen. If done with persistence this also has the benefit of being able to restore your app to the last state after being closed (which happens frequently on phones).
Depending on the complexity of your app state you could use the flutter built in state management or an addon like redux.
Redux requires more boilerplate coding but also offers more flexibility and for very large apps that is often required.
Here are a few interesting articles about the subject.
Official docs for state management
Redux or not
Help with choosing state management
Alternatives are to pass arguments on route navigation. This can be done either as part of the route string (which doesn't work with static route strings) or with a MaterialPageRoute for example (see this answer).
There is also package that makes passing parameters easy: https://pub.dartlang.org/packages/navigate.
An example with the navigate package looks like this (taken from this github issue):
Map arg = {"transactionType":TransactionType.fromLeft,"replaceRoute":ReplaceRoute.thisOne};
Navigate.navigate(context,
"home",
transactionType:TransactionType.fromLeft ,
replaceRoute: ReplaceRoute.thisOne,
arg: arg
);
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
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%2f54015775%2fwhat-is-the-best-way-to-pass-data-or-arguments-between-flutter-app-screens%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
Typically the best way is to use app state management. You edit the state before switching routes and read the state on the new screen. If done with persistence this also has the benefit of being able to restore your app to the last state after being closed (which happens frequently on phones).
Depending on the complexity of your app state you could use the flutter built in state management or an addon like redux.
Redux requires more boilerplate coding but also offers more flexibility and for very large apps that is often required.
Here are a few interesting articles about the subject.
Official docs for state management
Redux or not
Help with choosing state management
Alternatives are to pass arguments on route navigation. This can be done either as part of the route string (which doesn't work with static route strings) or with a MaterialPageRoute for example (see this answer).
There is also package that makes passing parameters easy: https://pub.dartlang.org/packages/navigate.
An example with the navigate package looks like this (taken from this github issue):
Map arg = {"transactionType":TransactionType.fromLeft,"replaceRoute":ReplaceRoute.thisOne};
Navigate.navigate(context,
"home",
transactionType:TransactionType.fromLeft ,
replaceRoute: ReplaceRoute.thisOne,
arg: arg
);
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
add a comment |
Typically the best way is to use app state management. You edit the state before switching routes and read the state on the new screen. If done with persistence this also has the benefit of being able to restore your app to the last state after being closed (which happens frequently on phones).
Depending on the complexity of your app state you could use the flutter built in state management or an addon like redux.
Redux requires more boilerplate coding but also offers more flexibility and for very large apps that is often required.
Here are a few interesting articles about the subject.
Official docs for state management
Redux or not
Help with choosing state management
Alternatives are to pass arguments on route navigation. This can be done either as part of the route string (which doesn't work with static route strings) or with a MaterialPageRoute for example (see this answer).
There is also package that makes passing parameters easy: https://pub.dartlang.org/packages/navigate.
An example with the navigate package looks like this (taken from this github issue):
Map arg = {"transactionType":TransactionType.fromLeft,"replaceRoute":ReplaceRoute.thisOne};
Navigate.navigate(context,
"home",
transactionType:TransactionType.fromLeft ,
replaceRoute: ReplaceRoute.thisOne,
arg: arg
);
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
add a comment |
Typically the best way is to use app state management. You edit the state before switching routes and read the state on the new screen. If done with persistence this also has the benefit of being able to restore your app to the last state after being closed (which happens frequently on phones).
Depending on the complexity of your app state you could use the flutter built in state management or an addon like redux.
Redux requires more boilerplate coding but also offers more flexibility and for very large apps that is often required.
Here are a few interesting articles about the subject.
Official docs for state management
Redux or not
Help with choosing state management
Alternatives are to pass arguments on route navigation. This can be done either as part of the route string (which doesn't work with static route strings) or with a MaterialPageRoute for example (see this answer).
There is also package that makes passing parameters easy: https://pub.dartlang.org/packages/navigate.
An example with the navigate package looks like this (taken from this github issue):
Map arg = {"transactionType":TransactionType.fromLeft,"replaceRoute":ReplaceRoute.thisOne};
Navigate.navigate(context,
"home",
transactionType:TransactionType.fromLeft ,
replaceRoute: ReplaceRoute.thisOne,
arg: arg
);
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
Typically the best way is to use app state management. You edit the state before switching routes and read the state on the new screen. If done with persistence this also has the benefit of being able to restore your app to the last state after being closed (which happens frequently on phones).
Depending on the complexity of your app state you could use the flutter built in state management or an addon like redux.
Redux requires more boilerplate coding but also offers more flexibility and for very large apps that is often required.
Here are a few interesting articles about the subject.
Official docs for state management
Redux or not
Help with choosing state management
Alternatives are to pass arguments on route navigation. This can be done either as part of the route string (which doesn't work with static route strings) or with a MaterialPageRoute for example (see this answer).
There is also package that makes passing parameters easy: https://pub.dartlang.org/packages/navigate.
An example with the navigate package looks like this (taken from this github issue):
Map arg = {"transactionType":TransactionType.fromLeft,"replaceRoute":ReplaceRoute.thisOne};
Navigate.navigate(context,
"home",
transactionType:TransactionType.fromLeft ,
replaceRoute: ReplaceRoute.thisOne,
arg: arg
);
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
edited Jan 3 at 3:37
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
answered Jan 3 at 3:25
Oswin NoetzelmannOswin Noetzelmann
3,9881529
3,9881529
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.
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%2f54015775%2fwhat-is-the-best-way-to-pass-data-or-arguments-between-flutter-app-screens%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
use state management
– Ahmed
Jan 3 at 3:01