• OutcomeCreate will not be part of navigation history.
• After saving Frame.GoBack() will be invoked. This should be wrapped in something like ICloseable.
• On desktop this could be created using new window or modal-like panel.

Originally posted on #2.

A grid view of categories is missing vertical scrollbar.

When selecting an item from main menu, there is no need for processing a whole navigation.

#20. This wizard should support kind of "temporal" / not completely filled outcomes which can be later shown somewhere and completed to standard outcomes.

After merging total into list virw, bars has gone, because there is a binding for TotalAmount

1. Create outcome.
2. Navigate somewhere.
3. Create new outcome using tile from start.

Now a back button navigation is executed and OutcomrCreate is shown (again, instead of last displayed page).

• Mobile

The main menu on mobile, while organized bottom-up, should be transparent and only height of items should have background.

Try these features to measure loading time of bar/pie summary.

• Build better projections for summary view.
• Replace EF core with local file-based store for projections.
• Try memory caching of data.

Either via IReloadablePage or subscribe to OutcomeCreated event.

Every page should have a title.

On medium and large view it should be shown at the top, beside hamburger menu, all the time.

On small/mobile view we can think about hiding it in the main/hamburger menu.

Migration page should has some title, saying "Your application is upgrading".
Also, there should be some delay to finish transition-to, before transition out starts.

When no data is available, loading view is shown endless.

No data is displayed, instead of loading wheel.

Create drop-down list with theme switching options.

Wizards should be more integrated to the navigator.
They should respond to forward / backward navigation.

Currently the outcome wizard is missing a function for pinning secondary tile to a start.

Fix scrolling of content of summary page.

Move category edit button to the secondary buttons.

We should change semantics a bit.

• Every outcome will be placed in exactly one category.
• On the other, there will be tags which can be assigned multiply.

Category is a logical classification of outcome. On the other hand, tag is like a sub-category. This way can for example mark outcomes made by credit card.

• All navigation should be done in the Template page content frame.
• GroupPage should be transformed to kind of control with content, which will replace current frame.
• Summary page should be one. Because on larger displays, both graphs will be shown side-by-side.
• IParameterDecorator should be replaced with kind of parameter factory from parameter type or something. I'm not sure in this, but we need to pass a selected month/year from current group page, if any.

There should be controls for filtering in the category list.

1. Start from secondary tile.
2. Go to bar graph.
3. Go to pie chart.
4. Go to outcome creation.
5. Press back button.

The application will show a bar graph instead of pie chart.

After navigating back to the summary, "No data message" is displayed for a second.

1. Summary
2. Navigate to overview
3. Go back.

Add second tile which directly opens New outcome page.

After saving outcome, a dialog with timeout should be opened. The dialog will contain buttons for closing application (which will be executed after countdown is finished) or navigating to summary view.

Also, in this mode, no data should be loaded, so the application should start as quickly as possible.

When navigating to the categories and than back to the bar graph, menu button on bottom template bar has label on the right.

Foreground color of color should be taken dynamically based of background color.

For now, we can compute gray-scale version of background and decide whether is "more black" or "more white" and based on this decision take white or black as foreground.

Summary item in bar graph is not visible, unable to scroll to, when the app is landscape on phone.

Category overview should be also working without specific category key. In this mode it will simply show all outcomes from a specified period.

We have a very basic support.

• UI for managing currencies.
• Event for updates.
• Update symbol.
• Support for exchange rates.
• Removing exchange rate.
• Drop price factory.
• Selecting a currency as default to display amounts in it where possible (has exchange rates).
• To support exchange rates, we need a price with date everywhere.

• Introduce tags.
• No edit page for outcome. Instead use "Entity List" with action button for editing each property.
• Add icons for categories. It could be FA if there is a lib.
• Instead of deleting used category, it could be marked is "obsolete/hidden" and so displayed only in a managing page.

There should be some kind of switch between shown periods.
This switch should be part of the page, not the Template.

Originally posted on #2.

• Exception logging.
• Standart messagebox after exception when the apllication is built in debug.
• View last exception in settings.

On desktop align items top-down, like they are now.

On mobile and possibly only on mobile, align them bottom-up.

Add support for confirming `OutcomeDescription‘ by enter.

All content must be placed in the PivotItem content to fix scrolling to touch devices.

Refactor OutcomeCreate to control, which works like a wizard. Also this control can be used for editing existing outcomes. #8

A full page loading control should be part of the Template and when navigation starts inside content frame, this control should be shown before navigation in started (inner navigation, calling Navigate on Frame).

List of categories is missing vertical scrollbar.

Go to the summary and randomly start clicking on sorting buttons.
You will got an exception saying the SummaryTotalViewModel can't be casted to the SummaryCategoryViewModel.

No edit page for outcome. Instead use "Entity List" with action button for editing each property.

• Amount.
• Description.
• When.
• Categories.
• Delete.

It could be FontAwsome if there is a library for its use in the UWP.

When running on the phone, there is missing information about current state between steps.

For setting amount of outcome, try own in-app on screen keyboard.