AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

Edit history

Earlier versions of Using Capacitor for Mobile Development over Flutter, newest first.

Current version | Edited by Rex
Changes
Sorry if this comes off as insensitive! I'm extremely excited for this project, and wish for it to flourish. I'm just curious about the reasoning behind the decision to move forward with Flutter.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show

Using Capacitor for Mobile Development over Flutter

Problem

From everyone I've spoken to regarding Discord alternatives, if Fluxer had a mobile app, it would be the no-brain alternative to Discord. Absolutely nothing stands close, unless you're wanting E2EE or serverless architecture. I'm worried that the proposed migration to Flutter, while robust and sensible in the long run, is going to stunt development time so much that Fluxer loses its momentum.

Proposed solution

It seems something like Capacitor would have a considerably smoother transition than Flutter, given that you can almost 1:1 reuse the existing React front-end. Furthermore, it would prevent the headache of having to juggle two disjoint code bases in the long-run. The back-end is a different story, of course, but that's always going to be a problem (VoiP on IOS).

Notes (optional)

Sorry if this comes off as insensitive! I'm extremely excited for this project, and wish for it to flourish. I'm just curious about the reasoning behind the decision to move forward with Flutter.
Original by Rex
Show

Using Capacitor for Mobile Development over Flutter

Problem

From everyone I've spoken to regarding Discord alternatives, if Fluxer had a mobile app, it would be the no-brain alternative to Discord. Absolutely nothing stands close, unless you're wanting E2EE or serverless architecture. I'm worried that the proposed migration to Flutter, while robust and sensible in the long run, is going to stunt development time so much that Fluxer loses its momentum.

Proposed solution

It seems something like Capacitor would have a considerably smoother transition than Flutter, given that you can almost 1:1 reuse the existing React front-end. Furthermore, it would prevent the headache of having to juggle two disjoint code bases in the long-run. The back-end is a different story, of course, but that's always going to be a problem (VoiP on IOS).

Notes (optional)

Sorry if this comes off as insensitive! I'm extremely excited for this project, and wish for it to flourish. I'm just curious about the reasoning behind the decision to move forward with Flutter.

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.