hi, in AEMM what is the best way to implement a login screen/window that automatically opens after the splash screen upon app launch? i have entitlements working, but the user still must choose "Account" from app menu in order to login and see content, and it may not be clear that this sign-in method is available. this pop-up would only need to appear the first time, and anytime the auth token expires.
i am not a coder and did not setup the entitlement service, so apologies if this is common knowledge. just under a time crunch and hoping someone can point me down the right path.
There are a couple options to provide a more "up front" login experience to your users using either 1) An HTML Article or 2) A Dynamic Banner.
You can design an HTML article with login UI/information and place this article as the first item in your Top Level Collection. This means it will always be the first item that displays to your users. If you wan to include UI to enable a user to sign in directly from the article, you will need to Custom Authentication with a Generic Identity Provider and use APIs within the HTML. Another option is to include a UI element (link, button) that launches the sign in experience -- this also requires an API Call and will work with both Custom Authentication (SAML, OAuth or Generic IdPs) and authentication via a Direct Entitlement Server. Because the article will always display first, it's recommended to include logic to not display the article if the user is already signed in or to be able to dismiss the article to provide a good user experience.
You can use a Dynamic (HTML) Banner in a Browse Page to provide a login in message to your users and, by using the launchSignInUX API, enable the user to tap the banner to start the sign in process. Again, this API works with both Custom Authentication and authentication via a Direct Entitlement Server. By using a banner, you can continue to show a home browse page to your users as the first experience while still including a direct path for users to login.