User Story 1 & 2 notepad

[LibbyUX]

@andreasbueckle, I am starting an idea notepad for us here regarding User Story 1 & 2 UIs. Please capture all feature requests, UI inspiration screenshots, links, and more in this area!

[andreasbueckle]

Notes:

• Link to Map My Cells: https://portal.brain-map.org/atlases-and-data/bkp/mapmycells

• They have no sample data!

• Pretty neat use of button to cite the tool (could link to HRApop DOI once available):

  

• Link to R notebooks with use cases (could be Jupyter Notebooks for HRApop):

  

• And we already have a video tutorial. We may need to update it:

  

• Allows sign-in:

  

• Allows uploading anndata files. Our HRA U#2 requires much more preprocessing on the user's side:

  

[LibbyUX]

@andreasbueckle:

Last night I contemplated branding for these user story preview/beta tools. Concrete tool names and custom icon designs (see: tool icons) could elevate them when the time comes to revamp the features of these UIs.

Screenshot list of our current user stories in preview/beta mode:

[andreasbueckle]

@LibbyUX Yeah, that might be worth revisiting for US #1-2 especially. Also, a clearer link to HRA US numbers these previews are serving would be good.

[LibbyUX]

@andreasbueckle - We are getting closer to needing official names for these two products as the Atlas Applications design matures. Do you have any ideas off the top?

Atlas Apps Menu Design

Note: This will change. We are adding screenshots to make it more visual instead of having the product icons.

[LibbyUX]

@andreasbueckle Can we add features to already existing products to consolidate our products? Or do you see these two user stories as requiring their own product identity?

HRA Product Line

• Figma - Information Architecture: Products

[andreasbueckle]

@andreasbueckle - We are getting closer to needing official names for these two products as the Atlas Applications design matures. Do you have any ideas off the top?

Atlas Apps Menu Design

Note: This will change. We are adding screenshots to make it more visual instead of having the product icons.

I like the two suggestions you have on the right. @bherr2 could we rename https://apps.humanatlas.io/us1/ and https://apps.humanatlas.io/us2/ to match those names?

[andreasbueckle]

@andreasbueckle Can we add features to already existing products to consolidate our products? Or do you see these two user stories as requiring their own product identity?

HRA Product Line

* Figma - [Information Architecture: Products](https://www.figma.com/board/H3CK8StFdAphCFtFAHAwhM/Information-Architecture?node-id=479-1486&t=OddD7ooQ6GXHbEGc-4)

I think these two user stories need their own identity. These are demo apps that we are documenting with the paper. There will probably be other ways to access the data, and the HRA API also allows the usage of HRApop data for prediction.

[LibbyUX]

Hey Andi, regarding:

I like the two suggestions you have on the right. @bherr2 could we rename https://apps.humanatlas.io/us1/ and https://apps.humanatlas.io/us2/ to match those names?

and

I think these two user stories need their own identity. These are demo apps that we are documenting with the paper. There will probably be other ways to access the data, and the HRA API also allows the usage of HRApop data for prediction.

If they are having their own product identity, they will need strong names, branding, etc. I created the HRA Product Line board in our Figma Design System file to bring order to our HRA internal/external product jargon, naming inconsistencies, and product identities. US1 & US2 can be found in the Emerging Products section.

Can you please analyze the full board in Figma along with the US1 & US2 entries and let me know what you think?