I wrote TinyCld because Google in their infinite wisdom decided to cancel my 20 year old free Google Apps suite for "commercial usage". Which, to be fair it totaly was, and I obviously shouldn't complain about 20+ years of free usage.
But _still_, that wasn't the terms I signed up under, and nothing is more irratating than a good old fashioned rug pull. How hard could it be, right?
TinyCld is two things, a self contained workspace like the one we're all familiar with (mail/cal/contacts/drive/text/calc), as well as an easy to extend platform that brings all the batteries you'd need to write realtime web+native apps.
And yes, I used AI to write a lot of this. (really, ~200k loc by one author is a pretty good tell) Some may hate on that and thats fine, I get it. But I did look at each commit and there is a lot of bugfixing and tweaking features back and forth that went into it. If nothing else, I've got some good stories to tell here and have learned a lot.
Stack: Expo (React Native + web) on the frontend, PocketBase + Go on the backend. Standard protocols (IMAP/SMTP/CalDAV/CardDAV/WebDAV) so native clients work as well.
I'm currently using it myself with a few friends but has not been widely used beyond that.
Demo (no signup): https://tinycld.org/ and click the big Demo button.
One-line Docker install: https://tinycld.org/docs/installation Build a package in 10 min: https://tinycld.org/docs/creating-a-package iOS app: https://apps.apple.com/app/tinycld/id6762420971 Repo: https://github.com/tinycld
I'm very interested in any feedback anyone can offer. I've got a looong list of add-on packages I'm considering, suggestions welcomed!
Asking for a friend, who also enjoys building projects with LLMs, but publishing and supporting them not so much.
My biggest worry is your supply chain. If you're mostly using AI, would love to see you build your own library of functions and drop as many direct and transient dependencies as possible.
Nice work!
One question, I could not understand if a mail provider is needed or it handles on its own?
How is the Microsoft Office compatibility managed by these tools? There is a popular SDK providing the compatibility? I can't imagine everyone reimplementing the full compatibility layer
I was wondering what your reason is of developing it instead of just use nextcloud for your company or for mail, calendar, drive, docs and sheets? I mean at least with nextcloud you'd be up and running and have a battle tested solution.
I totally get the do it yourself approach and it's reason enough. And combining all the apps in one web interface is really solved well. Kudos. But I just wonder what your technical and maybe other reasons were.