Breaking down the Profile Section into Multiple Pages/Tabs

[Raj2503]

Problem

As mentioned in Setting #960, the profile section has become over-clustered as it contains the following options:

• Sign In
• Analytics Request
• Food Preference
• Allergies
• App Settings like (Themes, Light/Dark Mode)
• FAQ, Support, etc.

Proposed solution

Separate the "User/App settings" and "User Food Preferences" in the bottom Navigation bar, shifting the App Settings like themes and sign-in options under the new tab.
So I was thinking of either creating a slider App-Drawer for settings or adding A New Button in BottomNavigation for the same.

Before starting off with the idea, I would like to discuss with the community whether to make the changes or not and also to take in more suggestions.

Part of

• ⚙️ Settings (tracker) #960

[monsieurtanuki]

I do agree that the profile page is crowded.

My suggestion is perhaps simpler than yours:

1. keep a "main" profile page, with all the current "sections" but in a read-only/collapsed mode (for instance 3 lines max for each "collapsed" button)
2. when clicking on a section button, open a new page with read/write mode for only the selected section

[Raj2503]

Indeed it is a very brilliant and minimalistic idea.

I will work on implementing it and get back to you ✌️

[Raj2503]

@monsieurtanuki I am running into an error. For some reason, I am not able to make changes to the app_localizations.dart.

Every time I add an element ' String get app_personalization; ' and run the app, my changes get reverted and it gives an error that app_personalization isn't defined.

Can you guide me through what do I need to do to add new elements in app_localizations.dart.

[monsieurtanuki]

@Raj2503 I'm not an expert on localizations, but I'm pretty sure you should NOT edit app_localizations.dart.
If you want to add translations, you need to go to app_en.arb and add an entry.
Then, when you flutter run, the field will be automagically added to app_localizations.dart.

If you want my opinion, don't bother with translations in a first approach: if ever we finally decide that your code stinks, you would have put confusion in the translation files, where each entry is replicated into dozens of language-specific files.
First, do an interface we agree on with hard-coded English strings. Then maybe, later, localization.

[teolemon]

@Raj2503 @monsieurtanuki here's a mockup. Consent toggles go in app settings, food preferences in food preferences, all the app settings to … app settings ;-)

[monsieurtanuki]

Thank you @teolemon!
@Raj2503 It's up to you to code that, now :)

[Raj2503]

Thank you for the mockup @teolemon.

Sure @monsieurtanuki, I have already some progress. Now that I have a mockup, I will have a greater overview to refer to.

[teolemon]

Marking as in progress as a result

[teolemon]

hey @Raj2503 , are you still working on this one ?

[Raj2503]

@teolemon yeah I am implementing the idea you and @monsieurtanuki provided.

I ran into the following error:

The background of the new page section for App themes is not dynamically changing.
Apart from that, all other sections have been covered.

I have not been able to work at my full pace due to my University exams. But I assure you I will get back to it straight away as soon as I am done with my exams.

[monsieurtanuki]

Hi @Raj2503!
Perhaps there's a little misunderstanding: the point is not to have single items in full screen mode when in modification. The point is to have paragraphs (with several items) in full screen when in modification mode, instead of all paragraphs being editable at the same time on the same page.

And it's not what you display in your animated GIF:

• we don't want the dark mode edit to take the whole screen
• we just want the App Settings paragraph (that includes Dark mode) to be as little as a ListTile in the main settings mode, and then a click opens a full App Settings page, with the possibility to switch the Dark mode as right now as about 4 other app settings

Basically it should take one hour max to code; I'm afraid you started in a wrong direction and over-engineered the whole thing.

But first: study for you exams!

[M123-dev]

Any updates @Raj2503

[monsieurtanuki]

@Raj2503 If you don't mind I'll do it now. Don't worry: it was not the most interesting issue to code, and I'm sure that after you finish your exams there will be other issues to fix.