Viewing a dat in full-screen (browser vs. desktop)

[okdistribute]

Hey!

What does it feel like to interact with a dataset? Let's start thinking about this problem. The user can get to this screen in the following ways:

1. Click on a link to a dataset in the browser (http://dat.land/#6a63b293fg78e3...)
2. Click on a 'preview contents' button in the desktop application.

What are the differences between browser and desktop?

1. 'Download .zip file' in browser?
2. We want to prioritize people opening/downloading/sharing data using the desktop app rather than in browser.
3. Desktop app gives notifications when data is updated
4. Desktop app is faster
5. 'Reset' button in both desktop and browser might not make sense. 'Reset' is really creating a new dat instance.

Current mockup on http://dat.land

[max-mapper]

Reset feels kinda like a bandaid for the demo in the browser.... I think we can provide a better way for users to understand that they are viewing a specific dat and that they can create a new dat or switch to a previous dat. Maybe a two level hierarchy where you have a list of dats and a breadcrumb kinda thing showing you which one you're currently viewing?

[laurengarcia]

^^ yes. i had been imagining a thing like this as well. then instead of "reset" at the top of the list of "previous" dats, you'd also have a "create new dat" button.

[juliangruber]

Desktop app gives notifications when data is updated

ftr this can be replicated on web as well

To me that big difference between browser and desktop is that browser is for previewing a dat while desktop is for working with it. Browser doesn't need to focus on replication (right?) but rather in telling you what a dat is about. what's in it, "do i want to replicate it in desktop?".

[okdistribute]

Here's a the set of things a user should be able to do, let me know if this is helpful. I could also be missing things or adding too many things:

• View a file list
• Click on a folder, and navigate to its contents
• Click on a file, and preview its contents
• Download a single file
• Download the whole archive as a .zip
• Click a button to open the repo in the dat desktop app
• Get a share link to a single file (could be reflected in just the URL)

It might also have a name, owner, readme, and description at some point in the future.

Inspirations: GitHub/BitBucket/GitLab repositories, DropBox folders

[Kriesse]

Here's a wireframe to get a visual idea of the points mentioned above.

I'd like to have a top bar with logo + the global actions (i.e. Create New Dat or Import Existing Dat). That should replace 'Reset'. Stuff like Log In/Log Out can live there as well once we have it.

Name and metadata of the Dat are grouped with actions per dat (download, open in desktop app…).

Here's a more fleshed out version to clarify: