Imagine you have a toy box. But instead of keeping it just at home, it’s stored in a magical, super safe cloud where you can reach it from anywhere. This app is like that magical toy box – it remembers how your toys (files) are arranged in folders, even if you move them between your computer and your phone.
The problem: Autonomi has no concept of folders or file structure. Files are just… there. That’s confusing and unusable for regular people.
The solution: A cross-platform file manager (built with MAUI Blazor Hybrid) that creates a virtual file system by:
Saving folder structure in a local database
Tracking which files are where in the network
Syncing content between devices (PC ↔ Android)
Real-time notifications
Most decentralized systems forget about UX. This app fixes that.
Vision & Scalability
Full folder sync (like Dropbox – but decentralized)
AI-assisted file categorization
File previews for media & docs
Search by content & tags
File sharing across users via Autonomi
Tag-based organization alongside folders – assign multiple tags to a file for more flexible structure
In-app preview for images, PDFs, and videos – view content without downloading it
Offline mode – queue uploads/downloads and sync when reconnected
Optional IPFS integration – enable one-click sharing of selected files via public IPFS gateways for external access outside Autonomi
Goal: to become a daily-use decentralized file manager – simple enough for grandma, powerful enough for devops engineers.
Features
Virtual folder structure: Feels like a real file system, but built over Autonomi
Cross-device sync: Upload from PC, auto-appears on Android
Database-backed tracking: Remembers structure even if the network doesn’t
Upcoming bidirectional folder sync: Delete from synced folder → removes from Autonomi; upload on one → appears on the other
Live updates: New file? Everyone gets the ping
Target Users
Power users & tech enthusiasts
People using multiple devices (PC + mobile)
Privacy-focused users who want decentralization without pain
You guys have presented several interesting apps, most of them seem to need some serious efforts and time to develop. Are you two planing on developing all apps or have you just presented several options hoping 1 or 2 gets choosen among the 12 that goes to the next round?
We do plan to develop all of them - someday! Sadly, we haven’t found the “build everything instantly” button yet, so we’ll prioritize based on time and budget. But the ideas keep coming - I’ve got a whole AI army in my brain just waiting to be unleashed.
That is understandable, I hope you will make all those apps reality in the future, they sound interesting. As voting on apps they need to be working in june, then i will limit my voitng to just one or two of your presented apps. Do you have any experience in training small Ai’s to work on ordinary PC’s and phones?
It would be intersting to know how Ai will be implemented in the apps as that might be another layer of difficulty, what data will it be trained on and how is it meant to work in the app.
Half of the apps are nearly finished already, so yes, you’ll definitely see them working. You’re right - by June, only the working ones will matter. I usually leave the hardest parts for last, and in this case that’s the local AI model.
It’s possible to run a local AI on a desktop and expose it via an API - something like Qwen 3, for example. Then Queeni AI can talk to it the same way it currently talks to OpenAI’s API. That way, the app logic doesn’t change much - just the backend model.
There are also smaller models like LLaMA variants that can run completely offline on both laptops and Android devices - no internet, no external APIs, just local inference.
Just a question here. You said transferring between computer and phone. How can my phone know the folder structure if it is kept local on the computer? Especially if instead of it being my phone it is another person’s or a new phone which are not in the same location as the computer. Or even another time when the computer is not even there any more.
Surely the folder database must be shareable as well and not just stored on a local database
There are two ways the app syncs folder structure between devices:
Real-time notifications - when you create a folder or add a file on one device, the other (if it’s running) receives a notification and mirrors the change locally. You can already see this in action with Queeni AI, where the two apps talk to each other and stay in sync like gossiping coworkers.
Sync on start and exit - when the app starts, it downloads the database from the Autonomi network. When you close it, it uploads the updated version. This is how it’s currently done because ant-cli (the tool used to interact with the network) still lacks full capabilities. For example, it doesn’t yet support Scratchpad, which would let us make real-time changes without uploading the whole database. Once that’s available, we’ll switch to a more efficient method. For now, we just upload and download a small sqlite file (a few KB) - simple but effective. At 2:32 in the video, when I click Save and Exit, that long wait you see under “Saving data…” is actually the app uploading the database to Autonomi. That’s the sync process I mentioned - it sends the full database file when the app closes.
There’s no official .NET library for Autonomi yet, so we’re working with the tools we’ve got.
And hey, until Scratchpad support arrives, just think of it like carrying your entire office in your backpack - not ideal, but at least you won’t lose your stapler.