R to @Tiago_Ferat: 🔥🔥🔥 Can't wait for v2!

R to @cristianeptic: Local database (SQLite, etc)

R to @Tiago_Ferat: Wdym access the database? A local database for the user only, right? Otherwise you are exposing your real database’s credentials, use an api.

A tip if you are creating a massive application in Electron and don't want to go crazy: use the Main process only for essential things like writing files, saving things to the DB, etc. Write the application logic in the Renderer process, and whenever you need things like reading a file, writing it, etc., you call the Main process asynchronously. It took me a while to understand this.

R to @abdiisan: My pleasure bro!! Por nada 😁

R to @Tiago_Ferat: there you go! ✨ awesome obg Tiago

R to @abdiisan: Hi @abdiisan almost there... I use VueJS for FrontEnd. The complete stack is Typescript/Javascript/PHP/Electron/TailwindCSS/VueJS (and probably WebAssembly soon)

R to @newdata_learner: It uses Typescript/Javascript/PHP/Electron/VueJS (and probably WebAssembly soon)

R to @isfarsifat: This is @VemtoApp but version 2, which is under development

R to @iamleehom: This is @VemtoApp but version 2, which is under development

R to @info_mahfoud: 😁🚀🚀🚀

R to @abdiisan: idk for Vemto 2x most probably the same tech stack, although in the Dev Notes @Tiago_Ferat did say that he had to remake the entire architecture from the ground up 👆 so tech stack might have also changed a bit, this is just based on my assumptions and tracking of Vemto devops

R to @newdata_learner: Vemto 1.x was built with Electron for backend, but if you want the frontend is most probably React or Angular 🤷‍♂️ @Tiago_Ferat am I right? 🤔

RT by @Ricky31015825: Vemto reacting to Laravel / PHP errors in realtime 🔥

RT by @LaravelErrors: 👀 creating laravel relationships