Thank you.
Yes, desktop native app, mobile apps. All are planned and will come. Cross platform support was important to so people can run it on all platform. Hence the frontend is in Flutter which for most part is cross platform.
Although this so far have been hundreds of hours of work and there is much more upcoming to build it so as of now I am trying to make this project sustainable so I can continue working on it and it develops to the shape I want it to be.
Understood about docker.
Yes, those are planned and on roadmap. Apps will be coming soon. But software takes effort and time and just to get it here I have put in hundreds of hours and there is much more to build. Currently my focus is to make the project sustainable so I can continue developing it.
Yes definitely.
This is a very good feedback. Its surprising how being a developer and self hosted enthusiast who is neck deep on hosting everything of my own I completely forgot that there will be people who will like to use this and not know about docker and all the stuff (very common thing in self hosted community).
I would love to guide you through installing and using the application and your experienced feedback would definitely be very helpful in improving the app.
Are you on discord? Then you can join Journiv's community discord server https://discord.com/invite/CuEJ8qft46 if you aren't then just send me a message here.
No not rude at all :)
All this is a good feedback. If the lack of documentation confused you then I am sure there are many others who will get confused for the same thing. It is definitely something I should improve upon so everyone can understand the project and use it if they want to.
Cross platform for various reasons. There are two parts to Journiv
Backend: This is what you run on your local machine (ideally a small server/nas) which can run docker. You can run it on any machine.
Frontend: As of now this is a web app which you can run any where. The frontend of Journiv is in flutter which is cross platform and allow native desktop and mobile apps. Mobile apps will be launched soon.
Journiv is source-available but not “Free Software” under the FSF/OSI definition. I chose the PolyForm Noncommercial 1.0.0 license intentionally to keep the code open for personal and educational use which allow hosting for non-commercial while preventing "commercial" redistribution or hosting for commercial gain without permission.
My motivation behind Journiv is to give a solution to self hosted people like me and other a journal first experience on par with any major cloud offering so that they don't have to mold their usage to a notes app and be unsatisfied and frustrated like me. This license enables everyone in the self hosted community to use Journiv.
I did consider permissive and copyleft licenses (Apache, GPL, BSD, etc.), but sustainability is a major concern for this project. I have already spent hundreds of hours on this over last couple of months and there is so much more to build (take a look at the issues page of github repo). I want to keep development open and transparent while ensuring that commercial entities can’t simply repackage and profit from it.
Thank you. Yes, as a software engineer, not using AI for tasks where it can significantly accelerate development would be unrealistic. Much of the boilerplate code such as database ORM models, serialization/deserialization logic, and documentation was written with AI assistance, as mentioned in the project’s README. No developer writes such consistent and complete API docs :D. The architecture, UI/UX and harder aspects (see below) are done by me.
It took me 2 months of late nights (hundreds of hours so far) and spending every minute outside of job and family on this and without AI would have taken much more. What you see now is the result of many iteration, refining the UI/UX, redesigning the database, and reworking the overall architecture, flighting with CORS configs make video player work on web in flutter etc etc... much of which isn’t visible from the outside.
Thank you. Yes, desktop native app, mobile apps. All are planned and will come. Cross platform support was important to so people can run it on all platform. Hence the frontend is in Flutter which for most part is cross platform.
Although this so far have been hundreds of hours of work and there is much more upcoming to build it so as of now I am trying to make this project sustainable so I can continue working on it and it develops to the shape I want it to be.
Stay tuned!