Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show a breakdown of the total size #76

Open
1 task done
sprite-1 opened this issue Nov 2, 2019 · 4 comments
Open
1 task done

Show a breakdown of the total size #76

sprite-1 opened this issue Nov 2, 2019 · 4 comments
Labels
Needs Design Waiting for input from the UX team Priority: Wishlist Not a priority, but something that might be nice

Comments

@sprite-1
Copy link

sprite-1 commented Nov 2, 2019

Prerequisites

  • I have searched open and closed issues for duplicates.

Feature

Is your feature request related to a problem? Please describe.

As an end-user, it seems absurd to install Telegram which I know is a relatively small application and be greeted by this size with no further information on why it's going to take up this much space.
Screenshot from 2019-11-02 20-13-40

Describe the solution you'd like

While I myself understand that Flatpak requires some common runtimes for the apps to work properly and it's generally a one-time install for the most part, the common layperson that elementary OS aims to target may not. So showing a list of to-download components with a break down of size would be a whole lot better. Maybe even indicating that certain components are runtimes that only need to be downloaded once and not again for subsequent applications. In the name of keeping the UI clutter-free, this can be hidden in a toggleable triangle.
sideload_mock1
sideload_mock2

Existing work

I don't know if this exists elsewhere but it would sure help in making elementary OS feel more premium and polished.

Describe alternatives you've considered

I haven't considered any other alternatives as I believe this would be the optimal approach. It keeps things simple while still giving the users the information in case they want it.

Additional context

None

@sprite-1
Copy link
Author

sprite-1 commented Nov 2, 2019

Added the mock design. I meant something like that

@cassidyjames
Copy link
Contributor

cassidyjames commented Nov 4, 2019

Could we go a step further and subtract the size of the the installed components from the estimate?

Edit: This is actually much more complex, as runtimes are basically diffed against one another (shared files are shared on disk and not re-downloaded), even if it's a different version or a different runtime entirely. But if the exact version of a runtime is already installed, we should be able to omit it. I'm not sure if Flatpak does that for us automatically or not.

@sprite-1
Copy link
Author

sprite-1 commented Nov 4, 2019

Could we go a step further and subtract the size of the the installed components from the estimate?

I wasn't sure how Sideload worked behind the scenes but I thought if the required component is already installed, it would automatically be omitted from the total size (thus, also the list)

@davidmhewitt
Copy link
Member

Yes, that should already be the case. Only components that are to be installed are included in the download size calculation. However, the actual download size may be less as the calculation can't work out any delta update reductions.

@cassidyjames cassidyjames added Needs Design Waiting for input from the UX team Priority: Wishlist Not a priority, but something that might be nice labels Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Design Waiting for input from the UX team Priority: Wishlist Not a priority, but something that might be nice
Projects
None yet
Development

No branches or pull requests

3 participants