Aves

Ask an Android user what their gallery app does and the answer is usually “shows my photos.” The default is whatever the phone maker bundled, or Google Photos and its steady pull toward the cloud. The third-party field is crowded with viewers that pay their way through ads. Aves, developed by Thibault Deckers and built with Flutter, takes a different line on every count. It is free, ad-free and open source under the BSD-3-Clause license, with its code public on GitHub.

The product has two halves. The first is a gallery. It scans the device’s media library, sorts it into albums, dates, places and tags, and opens an unusually wide range of formats: JPEGs and MP4s, but also multi-page TIFFs, SVGs and older AVI videos. The second is a metadata explorer. It shows the information embedded in each file and lets users edit dates, location, ratings and tags. That second half gives Aves its identity. Most galleries treat a photo as a picture. Aves treats it as a record and builds its navigation on the fields inside that record.

The positioning follows from that design. This is a gallery for people who manage their own library rather than handing it to a service. That includes phone photographers who care when and where a shot was taken, archivists with mixed-format collections, and users who want their media software free of ads. With the ‘libre’ F-Droid build, it can be free of Google services too.

Reception is warm but thin. On AlternativeTo, Aves holds an ‘Excellent’ rating from a small handful of reviews. That is too few to settle anything, but the reviews agree on what they reward: the price, the open license, the absence of ads, an attractive interface, the collection statistics, the format support and the depth of the metadata tools. The complaints concern trust and onboarding, not missing features.

• Wide format support: Opens common JPEG and MP4 files alongside multi-page TIFFs, SVGs and older AVI videos, so mixed archives don’t need a second viewer.
• Automatic media detection: The library scan identifies motion photos, panoramas (photo spheres), 360° videos and GeoTIFF files without manual sorting.
• Linked browsing: Albums, dates, places and tags connect to one another, so any attribute leads to related media.
• Map view with reverse geocoding: Plots where photos were taken and turns raw coordinates into readable place names.
• Metadata viewer and editor: Shows the information embedded in each file and lets users change dates, location, ratings and tags.
• Search, filters, favorites and statistics: Standard library management, plus collection statistics that most galleries don’t offer.
• System integration: Home-screen widgets, app shortcuts, a screen saver, global search support, wallpaper setting, and the option to act as the media viewer or picker for other apps.
• Biometric vault: A locked space for media that shouldn’t sit in the main library.
• Android TV support and a ‘libre’ build: Brings the library to the living room, and offers an F-Droid version without Google services.

Everything Is a Filter

The defining design choice is that albums, dates, places and tags are linked. A folder-based gallery makes users remember where a file is stored. Aves lets them remember what the file was: a trip, a month, a tag, a city. From there they can move sideways. A photo’s date leads to everything else from that day. Its place leads to everything shot there. Its tags lead to everything filed the same way. Search, filtering and favorites sit on top of these links rather than replacing them.

This is the right model for large libraries. The folder trees that cameras and messaging apps create say almost nothing about what a photo is. The weakness is that the model depends entirely on the data underneath. A scanned print with no capture date, a screenshot with no coordinates, a download stripped of its metadata: these files fall out of the timeline or off the map. That is why the editing tools matter so much. They are the maintenance layer that keeps the linked model accurate.

Collection statistics push the same idea further by presenting the library as a dataset. Users praise them, and they suit an app this focused on what’s inside files. They will mean little to someone who just wants last week’s photos.

Metadata as the Main Event

The metadata viewer shows the information embedded in each file, and the editor lets users change dates, location, ratings and tags. The use cases are concrete:

• correcting photos from a camera whose clock was set wrong
• adding a location to photos that lack one
• rating and tagging a backlog so search has something to work with

Many photos now live only on a phone. Having these tools inside the gallery saves a trip to desktop software.

The stakes are real. In a linked library, an edit spreads. A wrong date moves a photo to the wrong point in the timeline. A wrong location moves its pin on the map and its entry in the places view. Aves gives users powerful tools and trusts them to use them carefully. That is the right trade for the audience it courts. It is less forgiving for anyone who opens the editor without knowing what it does.

Format Coverage and Smart Detection

Support for multi-page TIFFs, SVGs and older AVI videos shows who Aves is built for. Phone cameras don’t produce these formats. They come from scanners, design tools, document workflows and older cameras. A gallery that opens them means one less specialist viewer on the device. GeoTIFF detection goes further into niche territory. GeoTIFF is a mapping format, and its inclusion suggests GIS hobbyists and professionals are part of the intended audience.

The automatic detection of motion photos, panoramas and 360° videos serves a much broader group. In a generic viewer, these files tend to look like ordinary stills or clips. Because the library scan flags them, users don’t have to hunt for the shots that need special handling.

Living Inside Android

The most important integration is also the least glamorous: Aves can act as the media viewer or picker for other apps. Without that, users would be sent back to the stock gallery every time they attach a photo or open an image from a chat. Aves avoids that trap. Home-screen widgets, app shortcuts, global search support, a screen saver and wallpaper setting follow the same logic. They make the library reachable from across the system, not just from the app icon.

The choice of Flutter makes this more interesting. Flutter is a cross-platform toolkit, yet Aves ships only on Android and still reaches deep into the platform’s system features. The framework provides a consistent interface, and the Android-specific work provides the integration. The result is an app fully committed to one platform.

Vault, Consent and Trust

The biometric vault meets a real need. Some media shouldn’t be in a library that anyone holding the phone can scroll through. Locking it behind the device’s biometrics is a low-friction way to protect it.

Trust is where Aves draws its only real criticism. One AlternativeTo user objected to being asked to accept data-collection terms before using the app. According to Aves’s own terms, the only data collected is optional, consent-based, anonymous crash reporting through Firebase Crashlytics. Asking for consent is the right behavior. Asking for it before the app can be used is poor onboarding. It adds friction at the worst moment and makes a modest crash-reporting option look more invasive than it is.

A second user reported that Google Play flagged the app as unsafe. One report doesn’t establish a cause. Still, a warning from the platform’s own store hurts trust, especially for an app that needs access to a user’s entire photo library. Two things soften the problem. The code is public, so anyone can audit it. And the F-Droid ‘libre’ build removes Google services, which settles the Crashlytics question entirely.

Users specifically praise the attractive interface, which matters in this category. An app this heavy on metadata risks looking like a spreadsheet. The design problem Aves takes on is hierarchy: showing a photo as a photo first, while keeping its dates, coordinates, ratings and tags one step away. The linked filters, the map and the statistics view each answer a different question about the library: when, where, what and how much.

The metadata viewer has the hardest job. Embedded data is dense and varies between file types, and no design makes it easy reading. The best a viewer can do is order it sensibly and separate the fields users can edit from the ones they can only read. Users who come for this view will accept the density. Casual users will rarely open it.

Flutter apps typically draw their own interface instead of relying on stock Android components. Aves should therefore look the same across phone makers’ Android skins and Android versions.

Performance expectations follow from the design. Detecting motion photos, panoramas, 360° videos and GeoTIFFs, and reverse geocoding locations, requires an indexing pass over the library. That work grows with library size, so owners of very large collections can expect the first scan to take time. Multi-page TIFFs and older AVI videos are also inherently heavier to decode than a standard JPEG. None of this is unusual for a gallery with this many features.

Aves is Android-only, with no official iOS release. Within Android, the meaningful differences are these:

• Phone and tablet vs. Android TV: On phones and tablets, Aves is a touch-driven gallery with widgets, shortcuts and the biometric vault. On Android TV, users navigate with a remote, and different features matter. The screen saver and big-screen viewing make sense there. Metadata editing remains a phone-first task, and the vault assumes a device with biometric hardware.
• Google Play vs. F-Droid: The Play build includes the optional Firebase Crashlytics reporting described in the app’s terms. The ‘libre’ F-Droid build drops Google services, making it the obvious choice for users who avoid them.
• Pricing: Free and ad-free.

Aves earns a qualified recommendation by taking metadata seriously. The linked library, the map and the editor work as one system: the editor repairs the data, and the links and the map turn that data into ways to navigate. Add format support that reaches multi-page TIFFs and GeoTIFFs, system integration deep enough to replace the stock gallery, and a price of zero with no ads, and the value case holds for its audience.

It has flaws. Asking for consent before first use is clumsy onboarding for a modest, optional crash reporter. A reported Play Store safety flag is a trust problem whatever its cause. The F-Droid build addresses both for users willing to install outside Google Play. Casual users will find more app than they need. The audience Aves targets — anyone who cares when, where and how a photo was made — gets a gallery built around exactly those questions. We recommend it to that audience, with reservations.