Open mrsauravsahu opened 2 years ago
As rust can compile to web assembly and flutter can target the web definitely sounds feasible. This would also enable getting rid of the link to the trello roadmap which was a bit detering for me.
That would be an awesome step-up !
I don't know Rust yet, but if this requires learning Rust, that'd be a great secondary output for now.
I'm currently doing a home server and I think the same ! I would like to know if there are any updates about this idea ?
In my case I'm running the 64 bits raspberry pi OS, from what I saw there are no docker available for this architecture ? Should I try to install it via the code source (I don't know if someone tried this before) ?
Is this a duplicate of https://github.com/AppFlowy-IO/AppFlowy/issues/89
I'm currently doing a home server and I think the same ! I would like to know if there are any updates about this idea ?
In my case I'm running the 64 bits raspberry pi OS, from what I saw there are no docker available for this architecture ? Should I try to install it via the code source (I don't know if someone tried this before) ?
I was also looking into testing this but couldn't find any arm64 docker images as of February 2023.
Same here, please make it a priority to be able to run AppFlowy via the web! To me this looks like a (very) light version of NextCloud, with almost all of the important bits intact.
+1
I have no ideas why author decided to not build this on web based stack. Without web app this project is dead. You, you can have Rust based client, but main should be browser based and as web app. Main usecase is team collaboration for apps like this. Yes, I can setup stack with Firebase for sharing. But I will not able to allow comfortable UX like they're having for last few days - we all work in browser.
But you can still use your lovely Rust as server app (but why...) :)
Anyway, thank you for great job, this is a great project, but we can't use this yet :)
what is difference between appflowy web and appflowy web_app sub-folder?
I have no ideas why author decided to not build this on web based stack. Without web app this project is dead. You, you can have Rust based client, but main should be browser based and as web app. Main usecase is team collaboration for apps like this. Yes, I can setup stack with Firebase for sharing. But I will not able to allow comfortable UX like they're having for last few days - we all work in browser.
But you can still use your lovely Rust as server app (but why...) :)
Anyway, thank you for great job, this is a great project, but we can't use this yet :)
It seems users have different priorities. For me personally a web UI is a secondary feature, and I strongly prefer that all operating systems (macOS, Linux, Android, iOS and Windows) have a native application available. I chose AppFlowy especially because it isn't another Electron app bloating my OS with shipping and running its own browser, tons of nodejs libraries and other bloat. While rocket.chat and other Electron based apps consume more than a GB of RAM (each!) on my system, AppFlowy just sips 250 MB of RAM. That's the resource efficiency I am looking for in an application.
Not all work in a browser and having a dedicated, fast and resource efficient application is my biggest reason to use AppFlowy. Still I am in favour of having a web UI for guest users and users missing admin rights to add applications to their system. Preferrably as part of the appflowy-cloud docker-compose deployment, which offers the admin interface.
1~3 main use cases of the proposed feature
As a user, I want to be able to use AppFlowy as an app on my home network.
what types of users can benefit from using your proposed feature
Multiple users on a network and the same could be used on an enterprise level.
Additional context
I'm currently setting up my home network. And AppFlowy seems to be the perfect note-taking/planning/journalling app. Would love to install as a docker-compose file and use it through my network.
Awesome project! 💯