element-hq / element-hq/element-meta

Consider moving to FLUTTER for development for some advantages?

Open
#570 0 comments 1 reaction 0 assignees View on GitHub
A-Developer-Experience S-Tolerable T-Enhancement
Dominant language
No language data
Stars
112
Forks
26
Avg merge
6h 6m
Merged PRs (30d)
4

Description

### Your use case

#### What would you like to do?
Ask if maintainers would consider developing FLUTTER version?

#### Why would you like to do it?
A Flutter version would likely be half the size of the current APK but most importantly would likely run better and faster and have a "unified" User Interface across iOS/Android and even Desktop. Perhaps it wasn't considered previously since FLUTTER WEB support wasn't as mature?

#### How would you like to achieve it?
Perhaps some funding help from community.

### Have you considered any alternatives?

Well yea I've seen there are one or two Flutter alternatives already out there, but they are AGPL licenses, need it same/Apache.

### Additional context

I confess that I hate javascript, though admit react native is commendable for what it's achieved. Yet I much prefer FLUTTER native and avoid Javascript run-time engines and bridges etc. Anyway, just wanted to know if the Devs have/would/will consider Flutter.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named in the issue. Start by reviewing the existing client architecture and maintainer discussion to determine whether a Flutter client is in scope; the issue has no concrete implementation boundary or acceptance condition yet.

Written by the indexing model from the issue text.

Assessment

Tech stack
flutter
Domain
desktop-dev, mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.