I think that double clicking on a line of the SELECT results should open a new window with the data of it shown as key : value and with the possiblity to modify the data (or not).

The reason why I'm asking for this, is that I need to read a database with articles and it's impossible to read if the data is correctly being saved :(

Currently the README is very basic and probably not enough for someone who is new in the ecosystem.

I guess it would help to extend it or add another Markdown file that explains more about the how's, why's and issues that might appear on adding new applications.

WinePak has the potential to be a game changer [for many people](h

It seems there is not link to the application in the build information page (or I've found it).

For example, the page https://flathub.org/builds/#/builders/32/builds/6051 has no link to the
corresponding application (https://flathub.org/builds/#/apps/org.kiwix.desktop)

The "title" of the build Build of org.kiwix.desktop seems a good place to add a link to the application. (But it could be

Right now it looks like we list apps alphabetically in search results, regardless of their relevance to the search. Performing the same search with appstreamcli seems to return better ordering, so if we can use that, we probably should—otherwise (or if we find it produces better results), we should order results by:

• App names starting with the term
• App names containing the term
• Eve

As pointed out by winepak/applications/pull/9, the appstream spec has the require and recommends tag, eg.

<requires>
    <memory>1024</memory> 
​</requires>
<recommends>
    <memory>2048</memory> 
​</recommends>

Allowing users to see required and recommend system specs needed for

I guess you're aware of most UI issues, but here is one you might have missed. When you download wallpapers, those might have very long names ..as you can see on screenshot

Two more issues here is that

1. The selection gets the full height
2. When yo

I believe that the elementary OS installation instructions for Flathub should also contain the CLI remote-add instructions as well as a repository file in addition to the tip about installing Flatpaks directly from the website.

Hopefully this would reduce potential confusion for those looking to work directly with the repository or use a CLI-only method of installing.

Hi, perhaps it wouldn't be a bad idea to include some minimal documentation for the different emulation cores. This could cut down on people submitting issues about for simple questions that they could look up themselves.

Or at the very least, include links to the official site for each core. This could take the guesswork out of trying to find out which core is being used for a particular emula

Some folks have pointed out that it might not be entirely accurate to say an app has not been reviewed for security and privacy, as Canonical may have reviewed apps in their repos, Flathub may have reviewed apps in their remotes, etc.

I think this can be resolved by being more precise, and saying they have not been reviewed “by elementary”.