After Successful Login Automatically Show the App

[nelsonic]

At present, after successful authentication, we are presented with this screen:

As a user I don't want to have to click a button/link before seeing the app interface.

Todo

• Automatically show the interface with my items/timers
• Automatically "focus" the cursor on the text area to input an item.

[SimonLab]

I agree with displaying the list of captures once the user is authenticated.
This page can even be removed entirely as we can display the navigations at the top of the pages.

[SimonLab]

Removing the current home page means redefining the routes and url parser:

app-mvp-elm/src/Route.elm

Lines 15 to 31 in e7edc1a

	type Route
	= Home
	| Auth (Maybe String)
	| Logout
	| Capture
	| CaptureTimers Int
	routeParser : Parser.Parser (Route -> a) a
	routeParser =
	Parser.oneOf
	[ Parser.map Home Parser.top
	, Parser.map Auth (Parser.s "auth" <?> Query.string "jwt")
	, Parser.map Logout (Parser.s "logout")
	, Parser.map CaptureTimers (Parser.s "capture" </> Parser.int)
	, Parser.map Capture (Parser.s "capture")
	]

We also need to make sure to redirect to the authentication page when ther user is not logged in anymore.

[SimonLab]

Creating a login page where the user is redirected when not authenticated yet.
Currently the not logged in yet message needs to be created on all the pages:

app-mvp-elm/src/Pages/Capture.elm

Lines 224 to 230 in 0fe2775

	, case model.session of
	Session.Guest _ ->
	link [ centerX ]
	{ url = Route.routeToString Route.Home
	, label = text "Not logged in yet!"
	}

We can instead check the session of the user when the page is initialised and redirect to the new login page.

[nelsonic]

@SimonLab the login page will be covered by Auth. 👍

[SimonLab]

Yes at the moment the auth page is currently displayed when the session of the user is "guest":

I wanted to see if a login page could provide a nicer transition as for now when a session expired or when the user logout, the application redirect automatically to this auth page. This felt a bit abrupt and I think having a login page would help to explain why the user is not logged in anymore (session expired, logout...) and the user can choose to login again.
So the login page will only have some explanation text and a login link which redirect to the auth service. We can try this flow and if this step is not necessary it will be easy to remove.

[nelsonic]

@SimonLab what you are describing is a great feature to be added to https://github.com/dwyl/auth 💡
Let's open a separate issue for that. 👍