F-Droid App Market Survey - Minimize Bandwidth or auto-Maximize Info and Pictures?

F-Droid app UI now mixes two different approaches: 1) Latest Tab retrieves app icons and screenshots automatically (if it works), with endless “scroll down for more”; 2) Requires “clicks to show” info like Categories Tab View All, or Individual app display: More (description); Links to source, issues etc; Permissions list; Versions; Version detail.

How do others like this?

Personally, I get little benefit from app icons, rarely look at screenshots, prefer to minimize data/bandwidth required, and get annoyed with frequent “click to show” more details (except Versions detail).

This and response partly motivates this survey: Blank app icons - #11 by justsomeguy

The Poll(s)

How much do you agree or disagree with the following statements?

0: Strong Disagree, 10: Strong Agree

F-Droid UI is already awesome as-is, mixed! (0: Strong Disagree, 10: Strong Agree)
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Decreasing Data/bandwidth is a priority to reduce (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Photos and icons are so cool bandwidth does not matter (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Touch for more is annoying (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Click for more is annoying, but an exception for loading icons and screenshots is Good (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Auto-load of Screenshots and icons is best (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Polls are useful (0: Strong Disagree, 10: Strong Agree):
  • 0
  • 2
  • 4
  • 6
  • 8
  • 10

0 voters

Compromise used with my repo: screenshots are resized to max 350px on their small side and stored as JPG with quality 70%, featureGraphics to 512x250 and same JPG compression. This significally reduces bandwidth (as screenshot size usually drops from around 1 MB each to around 30 kB) while still keeping the pics available. Many users (myself included) prefer to see what to expect – before installation :wink:

2 Likes

I recently did that for my site. Made all screenshots from 1080x1920 to half size, and any with too much content cut into third size.
The page has 32 images and loads under 2.8MB.

Meanwhile you can go to a blog and the little header graphic alone is 4MB.

example <-- optipng makes that image go from 1.6MB to 80KB!

Images as a whole seem to be something many overlook for some reason, yet they add up extremely quickly and it isn’t all that hard to easily optimize.

I optimized the GnuCash documentation package a while back and reduced the size distros were shipping every update by 28MB!

Just a PSA:
jpegoptim, optipng, imagemagick and the like are you friend, please use them.

1 Like

IIRC PNGs are optimized on publish? https://gitlab.com/fdroid/fdroidserver/-/commit/387eebc4d69e0c89fd27a0bbe20ab31a5ea4be20

But are they also resized? Say I’d send in 4k screenshots. Would they be “downsized” – or just “optimized”? In my repo I do both, and @SkewedZeppelin reported the same (“half size”). I never checked, but it would be sane to cap their size – be it at 720px or 350px at the small side.