mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 04:46:56 +00:00
[GH-ISSUE #7408] [FR] Android app widgets #3298
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3298
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Clos-Lapeyre on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7408
Description
Hello wonderful humans !
I just discovered App Flowy and I am in love with it. At the moment I just think it would be really awsome if there could be widgets for the android app.
Why Widgets ? Because otherwise it is very tedious to have to open the app every time and locate your pages. For example, if one uses Flowy as a daily calendar or an everyday To-Do list, a simple widget that would preview existing To-Dos and, on demand, directly create new ones without leaving the home screen would make things so much easier :)
In this way Flowy could truly become the one digital space of people, ditching the need for separate apps : calendar, To-Do, Notes, check list etc ...
To resume the request, widgets would allow 2 very practical things :
I hope you will find that possible new feature interesting,
All my support,
Theo
Impact
Everybody using Flowy on a regular basis on their smartphones would highly benefit from this. This feature could really help make Flowy easier and more practical to use.
To resume the request, widgets would allow 2 very practical things :
Additional Context
If there could be different widgets for diferent pages that would be amazing !
@annieappflowy commented on GitHub (Feb 23, 2025):
Hi
I'm using the Android app.
There are no widgets?
When I'm sharing content from other apps this one does not show up in the list of apps to share to?
For example if I read news and copy some text to huge clipboard, then share it.... Appflowy does not show up as a destination.
??
Thanks.....
@casainho commented on GitHub (Feb 25, 2025):
I also wish to have an Android widget so I could add a specific TODO list block or page!!
I have an high priority daily tasks that I wish to be show on my Android home screen with that widget!!
Currently I have my calendar, another app TODO list and meteo widgets.
@Artemis1-0 commented on GitHub (Mar 1, 2025):
And ios if there aren't any.
@annieappflowy commented on GitHub (Sep 2, 2025):
Supported in the upcoming release (both iOS & Android)
@Artemis1-0 commented on GitHub (Sep 2, 2025):
Nice!
@casainho commented on GitHub (Sep 2, 2025):
@annieappflowy I didn't see any commit or PR with code for this feature. Are you sure it will be implemented on next release? I also saw a mention on previous release of some implmentation for IOS, but not for Android.
@annieappflowy commented on GitHub (Sep 2, 2025):
@casainho , Yes, it’s currently in our premium repo. I know many Flutter developers may want to see how we implemented it. We’re happy to find a way to make the code public.
@Artemis1-0 commented on GitHub (Sep 2, 2025):
@annieappflowy Premium repo? Never heard of it.
@casainho commented on GitHub (Sep 2, 2025):
@annieappflowy please clarify, as I don't see any mention to premium in Appflowy site.
@annieappflowy commented on GitHub (Sep 3, 2025):
This year, we’re commercializing self-hosted AppFlowy, including AppFlowy AI, to make the project sustainable. There are closed-source features such as guest editors and permission management behind the paywall, only available in our premium repos.
Since the release of our new syncing protocol, the applications we released have been built from the AppFlowy-Premium codebase, which is not publicly available.
The premium repo is a fork of our open source repo plus closed-source features.
As mentioned in my previous thread, the code changes related to Widgets are committed to our premium repo as it's now used to build our applications. However, this feature is free for everyone and would be better to open source. We will find time to merge it back into our open source codebase.
@Artemis1-0 commented on GitHub (Sep 3, 2025):
I see. I feel mildly conflicted about this, but understand that you guys need a reliable revenue stream. Let's hope this doesn't lead to ens***ification :)
@casainho commented on GitHub (Sep 3, 2025):
@annieappflowy ok, and so I see you removed mention to OpenSource on your site. With this move, there are no guarantee in future you will fully close the app.
Time for me to start moving away, I don't want to build my knowledge base on closed source systems.
@annieappflowy commented on GitHub (Sep 3, 2025):
@casainho , we adopt an open core model. To make sure we can continue to maintain our open source project, we have to figure out the business side. Hope you can understand it, but I respect your choice.
@annieappflowy commented on GitHub (Sep 3, 2025):
@Artemis1-0 , thank you for your understanding. We are committed to open source, but we also have an urgency to make the project sustainable first. This is why we chose the open-core model.
@casainho commented on GitHub (Sep 3, 2025):
I need to better understand the risks for future. And about the future, I am ready to pay some value but only If I think the project will keep OpenSource.
@annieappflowy commented on GitHub (Sep 3, 2025):
@casainho , understood. Actions speak louder than words :)