Add net.cachapa.tudo

[cachapa]

Please confirm your submission meets all the criteria

• Please describe your application briefly.
• I have read the App Requirements and App Maintenance pages.
• My pull request follows the instructions at App Submission.
• I have built and tested the submission locally.
• I am using only the minimal set of permissions. (If not, please explain each non-standard permission.)
• All assets referenced in the manifest are redistributable by any party. If not, the unredistributable parts are using an extra-data source type.
• I am an author/developer/upstream contributor of the project. If not, I contacted upstream developers about submitting their software to Flathub. Link:
• The domain used for the application ID is controlled by the application developers either directly or through the code hosting (e.g. GitHub, GitLab, SourceForge, etc.). The application id guidelines are followed.
• Any additional patches or files have been submitted to the upstream projects concerned. (If not, explain why.)

Description: tudo is an experiment on simple, private, synchronized to-do lists.

[bbhtt]

So how does this work? You should not use dir sources, it should be a direct link to the source code/tarball/binary etc.

[cachapa]

To be honest this is my first time generating a Flatpak so I'm not sure if my approach is correct.

In the first case, the directory contains the executable + precompiled libs required for the application to run.

In the second the assets directory contains metadata for the Flatpak: build script, icon, .desktop, etc.

[bbhtt]

the directory contains the executable

And how is said directory found from here? We cannot go and grab it from your PC nor we can ship your PC.

It has to be a link.

[hfiguiere]

also what happens with the aarch64 flatpak?

[cachapa]

The application only supports x86_64 at the moment.

My goal is to add aarch64 later once the x86_64 is published and running.