aws-amplify / aws-amplify/amplify-hosting

"App with id: ###### not found" message is scary

Open
#2,195 2 comments 5 reactions 0 assignees View on GitHub
feature-request UX
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I'm always frustrated when I switch environments to check on another Amplify app and the banner is all red, scary, and obtrusive!

![image](https://user-images.githubusercontent.com/12780104/130453344-35ce9db0-7967-4b20-9a51-14176aa2892c.png)

Additionally, the difference between "connect app" and "new app" is unclear. Why can I at times create a new app and other times only connect? (I know it's because certain envs aren't supported yet, but maybe make this more clear)

![image](https://user-images.githubusercontent.com/12780104/130453405-9697c3e6-8828-4a2f-854f-de177871de60.png)

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

We should communicate more clearly that
- When switching envs: nothing bad happened to your app, it's simply not in that particular environment - maybe make the banner more of an informational / more easily dismissible?
- "Maybe “Your app isn’t available in X region. We see it in Y and Z regions."
- Clarify on connects vs. new

![image](https://user-images.githubusercontent.com/12780104/130453455-0a1c4262-b46d-4118-b852-dfc948901b2a.png)
![image](https://user-images.githubusercontent.com/12780104/130453497-72d38279-ea27-4d12-af04-da6e9f490f11.png)

**Additional context**
Add any other context or screenshots about the feature request here.
All images by @njreid

Contributor guide

Open the contributing guide

Research direction

The issue points to the environment-switching banner and the Connect/New app UI, illustrated by screenshots. Start by locating those UI entry points and review how unsupported environments are presented; done means the message is informational and dismissible, and the two actions explain when each is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.