pass-tomb VS mobile

By itself, Passwordstore will not encrypt file names or directory names, which might not be a problem if no one else has access to the machine that hosts your git repo, but if that's not the case (even if it's a private repo on whatever platform), you might want to use either Tomb or git-crypt-remote to have full end-to-end encryption. There are even some tools that glue tomb and pass together (https://github.com/roddhjav/pass-tomb for one), though I'm not sure what's the situation is like when it comes to mobile integration with tomb/git-crypt-remote.

That can of course be fixed by using pass-tomb, but that isn’t implemented in mobile clients (at least not on iOS).

- https://pujol.io/blog/tomb-with-gpg-keys/ - https://github.com/roddhjav/pass-tomb

A plug-in called pass-tomb exists to fix this, but doesn’t work with mobile apps (a least not iOS)

Currently I am learning golang. And I just thought why not create an Android app in GoLang... And luckly I stumbled upon this GitHub repo: https://github.com/golang/mobile - checked the docs but was not able to comprehend the terms: native, SDK apps, stuff...

If you use C#, Java, or Node.js for developing your backend, you may have to rewrite the same existing business logic in Dart on the Flutter frontend. The Go mobile project offers a way to call Go code from the platform-specific mobile development environments, i.e., Java and Android.

NDK is a fairly cursed thing dude, depending on your background I can suggest either looking at how golang interop is implemented (here or here), or going for flutter/dart ffi.

The other way is waaaay more complex, run a IPFS node directly on the android phone with their go-ipfs lib and making use of go mobile lib. Check this one https://github.com/cusspvz/react-native-ipfs

This part is one that I struggled the most with as the gomobile package is unstable and also lacks documentation and guides (as we all could have guessed that it's rarely used in a practical sense).