coracle/flotilla
1
6
Fork 23
Code Issues 42 Pull Requests 2 Actions Packages Projects 5 Releases Wiki Activity

Desktop App #51

New Issue
Open
opened 2026-02-17 18:05:43 +00:00 by hodlbod · 7 comments
hodlbod commented 2026-02-17 18:05:43 +00:00
Owner
Copy Link
Copy Source
  • Put together publish pipeline (app stores, zapstore, web, desktop)
  • Add downloads to website
- [ ] Put together publish pipeline (app stores, zapstore, web, desktop) - [ ] Add downloads to website
hodlbod added this to the Future milestone 2026-02-17 18:05:43 +00:00
triesap self-assigned this 2026-02-17 21:08:49 +00:00
triesap commented 2026-02-17 21:13:02 +00:00
Collaborator
Copy Link
Copy Source

I’ll start with a minimal Tauri baseline to get a native shell running

I’ll start with a minimal Tauri baseline to get a native shell running
hodlbod removed this from the Future milestone 2026-04-02 18:57:08 +00:00
hodlbod changed title from Desktop to Desktop App 2026-04-02 19:25:42 +00:00
hodlbod added the dev label 2026-04-02 19:25:45 +00:00
hodlbod added this to the Current milestone 2026-04-02 19:26:22 +00:00
triesap was unassigned by hodlbod 2026-04-02 19:26:27 +00:00
priyanshu_bharti commented 2026-04-05 07:45:49 +00:00
Contributor
Copy Link
Copy Source

Hi @hodlbod, I've been following the progress on Flotilla and I’m very interested in helping with the Desktop App implementation.

I see that the goal is to set up a minimal Tauri baseline. I have experience with React and Rust, and I’m comfortable setting up the necessary system dependencies on Ubuntu.

My proposed plan is:

  1. Initialize the Tauri configuration within the existing codebase.
  2. Ensure the current web frontend renders correctly within the Tauri native shell.
  3. Verify the basic build process for Desktop (Linux/Ubuntu).

Please let me know if I should go ahead with this or if there are any specific architectural preferences I should keep in mind before I start. Looking forward to contributing!

Hi @hodlbod, I've been following the progress on Flotilla and I’m very interested in helping with the Desktop App implementation. I see that the goal is to set up a minimal Tauri baseline. I have experience with React and Rust, and I’m comfortable setting up the necessary system dependencies on Ubuntu. My proposed plan is: 1. Initialize the Tauri configuration within the existing codebase. 2. Ensure the current web frontend renders correctly within the Tauri native shell. 3. Verify the basic build process for Desktop (Linux/Ubuntu). Please let me know if I should go ahead with this or if there are any specific architectural preferences I should keep in mind before I start. Looking forward to contributing!
hodlbod commented 2026-04-06 16:46:49 +00:00
Author
Owner
Copy Link
Copy Source

Sure, please go ahead — there is already a src-tauri directory, but I think the better direction will probably be @capacitor-community/electron, since tauri loses us access to capacitor plugins, which are a pretty significant dependency. Feel free to do some research on this tradeoff before getting started.

Sure, please go ahead — there is already a src-tauri directory, but I think the better direction will probably be [@capacitor-community/electron](https://github.com/capacitor-community/electron), since tauri loses us access to capacitor plugins, which are a pretty significant dependency. Feel free to do some research on this tradeoff before getting started.
priyanshu_bharti was assigned by hodlbod 2026-04-06 16:46:59 +00:00
priyanshu_bharti was unassigned by hodlbod 2026-04-09 21:44:33 +00:00
priyanshu_bharti commented 2026-04-10 12:02:32 +00:00
Contributor
Copy Link
Copy Source

Hii @hodlbod
I am currently working on this (Desktop App implementation).
Will update you with progress shortly!
Thanks!

Hii @hodlbod I am currently working on this (Desktop App implementation). Will update you with progress shortly! Thanks!
priyanshu_bharti was assigned by hodlbod 2026-04-10 22:28:19 +00:00
priyanshu_bharti commented 2026-04-12 18:54:24 +00:00
Contributor
Copy Link
Copy Source

Hi @hodlbod,

Thank you for the suggestion about @capacitor-community/electron.

I have been working on the Desktop App implementation for the last 4 days. After researching the tradeoff between pure Tauri and Capacitor Electron, I agree that keeping compatibility with existing Capacitor plugins is important. So I will go with @capacitor-community/electron.

However, since this is a significant addition to the project, doing everything at once is not practical. To keep the changes small, clean, focused, and easy for you to review, I have divided the entire work into 6 incremental PRs:

My Proposed Plan (6 PRs):

PR 1: Minimal Electron + Capacitor baseline

  • Install and configure @capacitor-community/electron
  • Set up basic configuration so the existing web app runs inside a native desktop window
  • Add initial desktop dev script (pnpm dev:desktop)

PR 2: Desktop window & build configuration

  • Configure window size, title, resizable behavior, etc.
  • Proper dev vs production build handling
  • Update package.json scripts

PR 3: Desktop-specific UI/UX adjustments

  • Handle menu bar, title bar, and system theme
  • Fix any CSS or layout issues that appear only in desktop environment

PR 4: Build pipeline & packaging

  • Add build commands for Linux (.AppImage), Windows (.exe), and macOS (.dmg)
  • Configure icons and application metadata

PR 5: Native features (Phase 1)

  • System tray icon support
  • Basic notifications using Capacitor plugins
  • Deep linking support (if needed)

PR 6: Polish, Auto-update & Documentation

  • Auto-update setup
  • Final testing and fixes
  • Update README.md with desktop build and run instructions

I have already spent the last 4 days researching and building the foundation for this. That’s why it’s taking some time — because I want to do it properly in small, reviewable steps rather than one big PR.

I will start with PR 1 (Minimal baseline) and will post progress updates here after each PR.

Does this plan sound good to you?
Any suggestions or changes in priority before I open PR 1?

Looking forward to your feedback!

Thanks!

Hi @hodlbod, Thank you for the suggestion about `@capacitor-community/electron`. I have been working on the Desktop App implementation for the **last 4 days**. After researching the tradeoff between pure Tauri and Capacitor Electron, I agree that keeping compatibility with existing Capacitor plugins is important. So I will go with `@capacitor-community/electron`. However, since this is a significant addition to the project, doing everything at once is not practical. To keep the changes small, clean, focused, and easy for you to review, I have divided the entire work into **6 incremental PRs**: ### My Proposed Plan (6 PRs): **PR 1: Minimal Electron + Capacitor baseline** - Install and configure `@capacitor-community/electron` - Set up basic configuration so the existing web app runs inside a native desktop window - Add initial desktop dev script (`pnpm dev:desktop`) **PR 2: Desktop window & build configuration** - Configure window size, title, resizable behavior, etc. - Proper dev vs production build handling - Update `package.json` scripts **PR 3: Desktop-specific UI/UX adjustments** - Handle menu bar, title bar, and system theme - Fix any CSS or layout issues that appear only in desktop environment **PR 4: Build pipeline & packaging** - Add build commands for Linux (.AppImage), Windows (.exe), and macOS (.dmg) - Configure icons and application metadata **PR 5: Native features (Phase 1)** - System tray icon support - Basic notifications using Capacitor plugins - Deep linking support (if needed) **PR 6: Polish, Auto-update & Documentation** - Auto-update setup - Final testing and fixes - Update README.md with desktop build and run instructions I have already spent the last 4 days researching and building the foundation for this. That’s why it’s taking some time — because I want to do it properly in small, reviewable steps rather than one big PR. I will start with **PR 1** (Minimal baseline) and will post progress updates here after each PR. Does this plan sound good to you? Any suggestions or changes in priority before I open PR 1? Looking forward to your feedback! Thanks!
hodlbod commented 2026-04-13 20:39:01 +00:00
Author
Owner
Copy Link
Copy Source

This sounds great, thank you! One addition I would add: could you first remove all the tauri-related stuff? We added that a while ago as an experiment, but since we're going with electron it's not necessary to keep any more.

This sounds great, thank you! One addition I would add: could you first remove all the tauri-related stuff? We added that a while ago as an experiment, but since we're going with electron it's not necessary to keep any more.
priyanshu_bharti commented 2026-04-13 21:04:38 +00:00
Contributor
Copy Link
Copy Source

Thanks for the feedback, @hodlbod! 🙌
Sure, I'll first remove all the Tauri-related code and files before starting with PR 1. That makes sense since we're fully going with Electron now.

I'll clean that up today itself and then proceed with the minimal baseline (PR 1) as planned.
Appreciate the suggestion!

Thanks for the feedback, @hodlbod! 🙌 Sure, I'll first remove all the Tauri-related code and files before starting with PR 1. That makes sense since we're fully going with Electron now. I'll clean that up today itself and then proceed with the minimal baseline (PR 1) as planned. Appreciate the suggestion!
👍 1
priyanshu_bharti was unassigned by hodlbod 2026-04-20 17:52:54 +00:00
hodlbod modified the milestone from Current to Next 2026-05-06 20:14:11 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design
For issues related to design work. Development should be done in another issue and refer back to this one.
 dev
Issues related to development work
 easy
Issues that can be executed on by new contributors
 idea
For issues that aren't yet actionable
 priority
For issues related to high priority features and bugs
 usability
Issues that have to be validated with real live human beings.
No Label dev
Milestone
No items
No Milestone Next
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod) mplorentz (Matt Lorentz) sakshamjain (Saksham Jain) sondreb triesap userAdityaa (Aditya Chaudhary)
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/flotilla#51
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?