[US-37] Landing page

angie commented

2026-08-21 18:33:57 +02:00

Owner

@yousef, to answer the question that was brought up in our last meeting, what would a good default be for you?

niko commented

2026-08-22 19:20:11 +02:00

Owner

looking forward what a good default would be according to Yousef.

I can add that what was proposed was: the default would be the private store.
Because it is a place where the user can freely organize all what amtters to them, including having links to other documents and stores anythwere in the UserStorage.
Other options that could be selected in settings for the landing page could be: the protected store, the stream (aggregated timeline of all those I follow, also called "attention box" by some) and in fact, any document or store of the user.

looking forward what a good default would be according to Yousef. I can add that what was proposed was: the default would be the private store. Because it is a place where the user can freely organize all what amtters to them, including having links to other documents and stores anythwere in the UserStorage. Other options that could be selected in settings for the landing page could be: the protected store, the stream (aggregated timeline of all those I follow, also called "attention box" by some) and in fact, any document or store of the user.

niko changed title from ~~[Appendix] Landing page~~ to [US-37] Landing page

2026-08-22 19:53:46 +02:00

yousef commented

2026-08-25 09:11:32 +02:00

Owner

I think this could be modeled after Drive or Notion:

Notion: always land on a page (maybe a "main" page). Or a "create new document" if there is none
Drive: land on a root folder. (If we do stick to showing different stores to users, we could show different roots in a grid / below each other

My main point is that I'd prefer to first design sensible defaults before customizability. And imo that should be a generic concept; tons of settings / customization are only interesting for power users (users who actively use the product). As we don't have (power) users yet, we don't know their patterns / desires, so I'd consider it premature to design / implement power-features

I think this could be modeled after Drive or Notion: - Notion: always land on a page (maybe a "main" page). Or a "create new document" if there is none - Drive: land on a root folder. (If we do stick to showing different stores to users, we could show different roots in a grid / below each other My main point is that I'd prefer to first design sensible defaults before customizability. And imo that should be a generic concept; tons of settings / customization are only interesting for power users (users who actively use the product). As we don't have (power) users yet, we don't know their patterns / desires, so I'd consider it premature to design / implement power-features

🚀 1

niko commented

2026-08-25 10:08:56 +02:00

Owner

Hi Yousef. Thanks for the feedback you shared here and there already several times, about complexity versus prioritization. I think we already explained that we are not defining a roadmap nor an MVP here, but rather expanding the overall vision of what is in scope for the 2 years we have ahead. Could we stick to that? power features will be implemented later, but we still want to know about them right now. Hope that makes sense.

jeremiah commented

2026-08-25 10:37:33 +02:00

Owner

I think iCloud's is a great default.

Screenshot 2026-08-25 at 10.36.26.webp

132 KiB

niko commented

2026-09-01 20:39:10 +02:00

Owner

We could definitely propose this template to users, as the home document in their private store. with a document we can put anything we want, including complex layouts like you screenshot.

niko added this to the Product Design PDR project

2026-10-13 13:44:54 +02:00

Rows
Columns

[US-37] Landing page #15