AppFlowy-IO/AppFlowy
1
0
Fork 0
mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 04:46:56 +00:00
Code Issues 952 Projects Packages Wiki Activity

[GH-ISSUE #3125] [Doc] AppFlowy Personal Cloud Private Beta #1371

New issue
Closed
opened 2026-03-23 20:48:24 +00:00 by mirror · 19 comments
mirror commented 2026-03-23 20:48:24 +00:00
Owner
Copy link

Originally created by @annieappflowy on GitHub (Aug 6, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3125

Originally assigned to: @LucasXu0, @annieappflowy, @speed2exe, @appflowy on GitHub.

Description

Define your goals

  • Thoroughly test the personal cloud functionality to guarantee smooth local data backup and seamless cross-device access, addressing any potential data loss issues.
  • Extend user outreach to gather comprehensive product feedback from a broader user base.
  • Enhance AppFlowy's visibility to increase awareness among a wider audience.

Define the target outcomes

  • Validate the stability of the personal cloud for a seamless public beta experience.
  • Aim to receive valuable feedback from at least 20% of 5,000 users during this period (1st round).
  • Targeting a public beta launch in two months (tentative).

Identify your participants

  • Existing AppFlowy users who are eager to use the Cloud functionality.
  • New users who are willing to adopt AppFlowy with an understanding of potential product instability during the beta phase.
  • Contributors, influencers, and writers who are interested in testing AppFlowy and providing their valuable feedback.

Distribute testing information starting on August 15th

  • Send a signup form to target users (Discord --> Twitter --> Email List --> Website --> Other platforms)
  • Screen qualified beta testers
  • Email a download link / access code with instructions

This may include product access materials like installation packages, download links, user guides, issue logging instructions, and anything else needed to facilitate the test.

Run the beta test

Gather and analyze feedback

Make final product updates

To-Dos

  • signup form
  • documentation
  • forum set up
  • beta tester award program
  • Windows package ready
  • Linux package ready
  • invite email
  • blog post
  • email subscribers
  • a new video marketing asset
  • risks and mitigations

Impact

Users who want to back up data to cloud and sync across devices

Additional Context

No response

Originally created by @annieappflowy on GitHub (Aug 6, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3125 Originally assigned to: @LucasXu0, @annieappflowy, @speed2exe, @appflowy on GitHub. ### Description ## Define your goals - Thoroughly test the personal cloud functionality to guarantee smooth local data backup and seamless cross-device access, addressing any potential data loss issues. - Extend user outreach to gather comprehensive product feedback from a broader user base. - Enhance AppFlowy's visibility to increase awareness among a wider audience. ## Define the target outcomes - Validate the stability of the personal cloud for a seamless public beta experience. - Aim to receive valuable feedback from at least 20% of 5,000 users during this period (1st round). - Targeting a public beta launch in two months (tentative). ## Identify your participants - Existing AppFlowy users who are eager to use the Cloud functionality. - New users who are willing to adopt AppFlowy with an understanding of potential product instability during the beta phase. - Contributors, influencers, and writers who are interested in testing AppFlowy and providing their valuable feedback. ## Distribute testing information starting on August 15th - Send a signup form to target users (Discord --> Twitter --> Email List --> Website --> Other platforms) - Screen qualified beta testers - Email a download link / access code with instructions This may include product access materials like installation packages, download links, user guides, issue logging instructions, and anything else needed to facilitate the test. ## Run the beta test ## Gather and analyze feedback ## Make final product updates ## To-Dos - [x] signup form - [x] documentation - [x] forum set up - [x] beta tester award program - [x] Windows package ready - [x] Linux package ready - [x] invite email - [ ] blog post - [x] email subscribers - [ ] a new video marketing asset - [ ] risks and mitigations ### Impact Users who want to back up data to cloud and sync across devices ### Additional Context _No response_
mirror 2026-03-23 20:48:24 +00:00
  • closed this issue
  • added the
    program
         label
mirror commented 2026-03-23 20:48:24 +00:00
Author
Owner
Copy link

@IMPranshu commented on GitHub (Aug 9, 2023):

Hey @annieappflowy. I would like to test this and give my feedback. How to get started?

<!-- gh-comment-id:1670664260 --> @IMPranshu commented on GitHub (Aug 9, 2023): Hey @annieappflowy. I would like to test this and give my feedback. How to get started?
mirror commented 2026-03-23 20:48:25 +00:00
Author
Owner
Copy link

@annieappflowy commented on GitHub (Aug 10, 2023):

You can sign up via filling out a form which will be shared next week.

<!-- gh-comment-id:1672625967 --> @annieappflowy commented on GitHub (Aug 10, 2023): You can sign up via filling out a form which will be shared next week.
mirror commented 2026-03-23 20:48:25 +00:00
Author
Owner
Copy link

@anhhtbk commented on GitHub (Sep 20, 2023):

Can you provide an update on the progress?

<!-- gh-comment-id:1727857854 --> @anhhtbk commented on GitHub (Sep 20, 2023): Can you provide an update on the progress?
mirror commented 2026-03-23 20:48:25 +00:00
Author
Owner
Copy link

@annieappflowy commented on GitHub (Sep 20, 2023):

It's on the private beta mode @anhhtbk

<!-- gh-comment-id:1727893233 --> @annieappflowy commented on GitHub (Sep 20, 2023): It's on the private beta mode @anhhtbk
mirror commented 2026-03-23 20:48:26 +00:00
Author
Owner
Copy link

@miztizm commented on GitHub (Sep 26, 2023):

Waiting with impatience, it's the only thing that keeps me from moving to Appflowy.

<!-- gh-comment-id:1734896696 --> @miztizm commented on GitHub (Sep 26, 2023): Waiting with impatience, it's the only thing that keeps me from moving to Appflowy.
mirror commented 2026-03-23 20:48:26 +00:00
Author
Owner
Copy link

@adriy-be commented on GitHub (Oct 10, 2023):

Hello, any news ? How to join the beta ?
I'm currently using Joplin with a self-hosted Joplin server, I'm really interesting to try and migrate to AppFlowy.

<!-- gh-comment-id:1754436576 --> @adriy-be commented on GitHub (Oct 10, 2023): Hello, any news ? How to join the beta ? I'm currently using Joplin with a self-hosted Joplin server, I'm really interesting to try and migrate to AppFlowy.
mirror commented 2026-03-23 20:48:26 +00:00
Author
Owner
Copy link

@annieappflowy commented on GitHub (Oct 12, 2023):

Hi @miztizm @adriy-be , please sign up for the Cloud beta
@adriy-be , have you tried self-hosting AppFlowy with Supabase?

<!-- gh-comment-id:1759734521 --> @annieappflowy commented on GitHub (Oct 12, 2023): Hi @miztizm @adriy-be , please [sign up](https://survey.appflowy.io/private-beta) for the Cloud beta @adriy-be , have you tried self-hosting [AppFlowy with Supabase](https://blog.appflowy.io/self-hosting-appflowy-free-using-supabase/)?
mirror commented 2026-03-23 20:48:26 +00:00
Author
Owner
Copy link

@adriy-be commented on GitHub (Oct 17, 2023):

Hi @miztizm @adriy-be , please sign up for the Cloud beta @adriy-be , have you tried self-hosting AppFlowy with Supabase?

Interesting ! I check that on my free time.
It's seem more complex than just deploy a container like Joplin server but supabase seem very interesting.
Thanks

<!-- gh-comment-id:1766288349 --> @adriy-be commented on GitHub (Oct 17, 2023): > Hi @miztizm @adriy-be , please [sign up](https://survey.appflowy.io/private-beta) for the Cloud beta @adriy-be , have you tried self-hosting [AppFlowy with Supabase](https://blog.appflowy.io/self-hosting-appflowy-free-using-supabase/)? Interesting ! I check that on my free time. It's seem more complex than just deploy a container like [Joplin server](https://github.com/flosoft/docker-joplin-server) but supabase seem very interesting. Thanks
mirror commented 2026-03-23 20:48:27 +00:00
Author
Owner
Copy link

@eitzenbe commented on GitHub (Dec 4, 2023):

Hi Annie, I have cloud version 0.3.8 docker hosted on one of my servers, but it seems this is not providing features like sharing pages amongst users accessing the server from different machines. I#d be happy to do beta tesing with a few colleagues if such a version is lurking around ;)

<!-- gh-comment-id:1839400776 --> @eitzenbe commented on GitHub (Dec 4, 2023): Hi Annie, I have cloud version 0.3.8 docker hosted on one of my servers, but it seems this is not providing features like sharing pages amongst users accessing the server from different machines. I#d be happy to do beta tesing with a few colleagues if such a version is lurking around ;)
mirror commented 2026-03-23 20:48:27 +00:00
Author
Owner
Copy link

@TheRealGramdalf commented on GitHub (Jan 22, 2024):

Edit: I think I found it: https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/DEPLOYMENT.md

I'm also interested in self-hosting appflowy, but in my perusal of the supabase guide it wasn't quite clear how everything fits together. Is there some guide I'm missing that can get me kickstarted with docker-compose? Or is deploying supabase the only thing to do, and appflowy takes the rest from there (once you've run the database setup etc.)?

<!-- gh-comment-id:1904522781 --> @TheRealGramdalf commented on GitHub (Jan 22, 2024): **Edit:** I think I found it: https://github.com/AppFlowy-IO/AppFlowy-Cloud/blob/main/doc/DEPLOYMENT.md I'm also interested in self-hosting appflowy, but in my perusal of the supabase guide it wasn't quite clear how everything fits together. Is there some guide I'm missing that can get me kickstarted with docker-compose? Or is deploying supabase the only thing to do, and appflowy takes the rest from there (once you've run the database setup etc.)?
mirror commented 2026-03-23 20:48:27 +00:00
Author
Owner
Copy link

@annieappflowy commented on GitHub (Jan 23, 2024):

@TheRealGramdalf , if you need help with self-hosting, please join our Discord server so we can offer quick support.

<!-- gh-comment-id:1905067665 --> @annieappflowy commented on GitHub (Jan 23, 2024): @TheRealGramdalf , if you need help with self-hosting, please join our [Discord](https://discord.gg/9Q2xaN37tV) server so we can offer quick support.
mirror commented 2026-03-23 20:48:27 +00:00
Author
Owner
Copy link

@xiaoxiaoimg commented on GitHub (Mar 23, 2024):

At present, it is a bit troublesome to use docker-compose to deploy, so why not host it on docker? docker run xxx?

<!-- gh-comment-id:2016440385 --> @xiaoxiaoimg commented on GitHub (Mar 23, 2024): At present, it is a bit troublesome to use docker-compose to deploy, so why not host it on docker? docker run xxx?
mirror commented 2026-03-23 20:48:27 +00:00
Author
Owner
Copy link

@Snuupy commented on GitHub (May 13, 2024):

looks like reminders on cloud beta isn't working (it is working on local)

<!-- gh-comment-id:2107292650 --> @Snuupy commented on GitHub (May 13, 2024): looks like reminders on cloud beta isn't working (it is working on local)
mirror commented 2026-03-23 20:48:28 +00:00
Author
Owner
Copy link

@speed2exe commented on GitHub (May 14, 2024):

@xiaoxiaoimg Appflowy Cloud comprises of a few services running. You could run each of them individually. docker compose makes the process easier.

<!-- gh-comment-id:2109197437 --> @speed2exe commented on GitHub (May 14, 2024): @xiaoxiaoimg Appflowy Cloud comprises of a few services running. You could run each of them individually. docker compose makes the process easier.
mirror commented 2026-03-23 20:48:28 +00:00
Author
Owner
Copy link

@speed2exe commented on GitHub (May 14, 2024):

@Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature.

<!-- gh-comment-id:2109198790 --> @speed2exe commented on GitHub (May 14, 2024): @Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature.
mirror commented 2026-03-23 20:48:28 +00:00
Author
Owner
Copy link

@Snuupy commented on GitHub (May 14, 2024):

@speed2exe

@Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature.

image
image

Even if I set a reminder in a shared workspace, it won't show up in Upcoming Notifications. I expected it to work as it did locally, that I would receive a notification if something was due.

<!-- gh-comment-id:2109205440 --> @Snuupy commented on GitHub (May 14, 2024): @speed2exe > @Snuupy What do you mean reminders on cloud beta isn't working? As far as I know, reminder are a local feature. ![image](https://github.com/AppFlowy-IO/AppFlowy/assets/964538/31f0159d-f8c5-4eb1-84a1-2446cb047afc) ![image](https://github.com/AppFlowy-IO/AppFlowy/assets/964538/92c9bc2d-e0b6-4201-b3b0-79e68404803c) Even if I set a reminder in a shared workspace, it won't show up in Upcoming Notifications. I expected it to work as it did locally, that I would receive a notification if something was due.
mirror commented 2026-03-23 20:48:28 +00:00
Author
Owner
Copy link

@therynamo commented on GitHub (Aug 5, 2024):

EDIT: Fixed.

Sorry for posting this and not digging further.

Hosted wtih Proxmox locally.

OS: linux x86_64 Ubuntu 22.04.4 LTS

Running with docker compose.

It turns out, despite my attempts to follow directions, I still ended up in a bit of an erroneous state.

Here is the error from MinIO: 
{"error":"code:Internal msg: Failed to create upload: ServiceError(ServiceError { source: Unhandled(Unhandled { source: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) }, meta: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) } }), raw: Response { status: StatusCode(404), headers: Headers { headers: {\"accept-ranges\": HeaderValue { _private: H0(\"bytes\") }, \"content-length\": HeaderValue { _private: H0(\"524\") }, \"content-type\": HeaderValue { _private: H0(\"application/xml\") }, \"server\": HeaderValue { _private: H0(\"MinIO\") }, \"strict-transport-security\": HeaderValue { _private: H0(\"max-age=31536000; includeSubDomains\") }, \"vary\": HeaderValue { _private: H0(\"Origin\") }, \"vary\": HeaderValue { _private: H0(\"Accept-Encoding\") }, \"x-amz-id-2\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-amz-request-id\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-content-type-options\": HeaderValue { _private: H0(\"nosniff\") }, \"x-xss-protection\": HeaderValue { _private: H0(\"1; mode=block\") }, \"date\": HeaderValue { _private: H0(\"<redacted>\") }} }, body: SdkBody { inner: Once(Some(b\"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><Key>[redacted path to image]</Key><BucketName>appflowy</BucketName><Resource>/appflowy/redacted/redacted/redacted.png</Resource><RequestId>redacted</RequestId><HostId>redacted</HostId></Error>\")), retryable: true }, extensions: Extensions { extensions_02x: Extensions, extensions_1x: Extensions } } })"},"target":"appflowy_cloud::api::file_storage","span":{"name":"create_upload"},"spans":[{"client_version":"0.6.6","device_id":"redacted,"method":"POST","path":"/api/file_storage/{workspace_id}/create_upload","payload_size":117,"request_id":"redacted","name":"request"},{"name":"create_upload"}]}

Here was the key to the puzzle:

<BucketName>appflowy</BucketName>

Turns out the bucket appflowy did not exist in MinIO.

Possible Reasons:

  • Initially when I booted up the VM I'd had kvm selected as my architecture, and MinIO complained about not supporting x_86. I saw on one of the github issues around here that I needed to use -AES in order to get MinIO to boot up. I changed the architecture, and restarted the machine, everything was good to go. But I imagine maybe there was a startup state missed? Idk. Then when MinIO started up no bucket was created
  • The appflowy bucket was missed in the docker compose startup 🤷 . I'm not sure.

Once I manually created the bucket named appflowy, images started syncing from mobile to desktop just fine, like they should!

WOOHOO! 🥳

Original Message:

Hey! Just wanted to say thank you so much for building this all in open source and offering a self hosted option. I'm very excited and hoping that AppFlowy can be our home Knowledge Base.

One thing with the self hosted cloud is this known issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4568

This is a really important feature for us in order to fully realize your platform.

I'm positive this is not a trivial issue, so I understand if it's still ongoing development. I'm hoping this is shored up sooner than later, but I know you all have your hands full. Any chance there is an update? (No pressure)

You've got a nice cross platform app here with an intuitive and easy to use UI. I'm very excited for what comes next for this project and team. Thanks again!

<!-- gh-comment-id:2269021602 --> @therynamo commented on GitHub (Aug 5, 2024): **EDIT**: Fixed. Sorry for posting this and not digging further. Hosted wtih Proxmox locally. OS: linux x86_64 Ubuntu 22.04.4 LTS Running with `docker compose`. It turns out, despite my attempts to follow directions, I still ended up in a bit of an erroneous state. <details> <summary>Here is the error from MinIO:</summary> ```json {"error":"code:Internal msg: Failed to create upload: ServiceError(ServiceError { source: Unhandled(Unhandled { source: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) }, meta: ErrorMetadata { code: Some(\"NoSuchBucket\"), message: Some(\"The specified bucket does not exist\"), extras: Some({\"s3_extended_request_id\": \"<redacted>\", \"aws_request_id\": \"<redacted>\"}) } }), raw: Response { status: StatusCode(404), headers: Headers { headers: {\"accept-ranges\": HeaderValue { _private: H0(\"bytes\") }, \"content-length\": HeaderValue { _private: H0(\"524\") }, \"content-type\": HeaderValue { _private: H0(\"application/xml\") }, \"server\": HeaderValue { _private: H0(\"MinIO\") }, \"strict-transport-security\": HeaderValue { _private: H0(\"max-age=31536000; includeSubDomains\") }, \"vary\": HeaderValue { _private: H0(\"Origin\") }, \"vary\": HeaderValue { _private: H0(\"Accept-Encoding\") }, \"x-amz-id-2\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-amz-request-id\": HeaderValue { _private: H0(\"<redacted>\") }, \"x-content-type-options\": HeaderValue { _private: H0(\"nosniff\") }, \"x-xss-protection\": HeaderValue { _private: H0(\"1; mode=block\") }, \"date\": HeaderValue { _private: H0(\"<redacted>\") }} }, body: SdkBody { inner: Once(Some(b\"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Error><Code>NoSuchBucket</Code><Message>The specified bucket does not exist</Message><Key>[redacted path to image]</Key><BucketName>appflowy</BucketName><Resource>/appflowy/redacted/redacted/redacted.png</Resource><RequestId>redacted</RequestId><HostId>redacted</HostId></Error>\")), retryable: true }, extensions: Extensions { extensions_02x: Extensions, extensions_1x: Extensions } } })"},"target":"appflowy_cloud::api::file_storage","span":{"name":"create_upload"},"spans":[{"client_version":"0.6.6","device_id":"redacted,"method":"POST","path":"/api/file_storage/{workspace_id}/create_upload","payload_size":117,"request_id":"redacted","name":"request"},{"name":"create_upload"}]} ``` </details> Here was the key to the puzzle: ```xml <BucketName>appflowy</BucketName> ``` Turns out the bucket `appflowy` did not exist in MinIO. **Possible Reasons**: - Initially when I booted up the VM I'd had kvm selected as my architecture, and MinIO complained about not supporting `x_86`. I saw on one of the github issues around here that I needed to use `-AES` in order to get MinIO to boot up. I changed the architecture, and restarted the machine, everything was good to go. But I imagine maybe there was a startup state missed? Idk. Then when MinIO started up no bucket was created - The `appflowy` bucket was missed in the docker compose startup 🤷 . I'm not sure. Once I manually created the bucket named `appflowy`, images started syncing from mobile to desktop just fine, like they should! WOOHOO! 🥳 --- Original Message: > Hey! Just wanted to say thank you so much for building this all in open source and offering a self hosted option. I'm very excited and hoping that AppFlowy can be our home Knowledge Base. > > One thing with the self hosted cloud is this known issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4568 > > This is a really important feature for us in order to fully realize your platform. > > I'm positive this is not a trivial issue, so I understand if it's still ongoing development. I'm hoping this is shored up sooner than later, but I know you all have your hands full. Any chance there is an update? (No pressure) > > You've got a nice cross platform app here with an intuitive and easy to use UI. I'm very excited for what comes next for this project and team. Thanks again!
mirror commented 2026-03-23 20:48:29 +00:00
Author
Owner
Copy link

@annieappflowy commented on GitHub (Sep 28, 2024):

@Snuupy , reminders syncing across devices should be fixed

<!-- gh-comment-id:2381025913 --> @annieappflowy commented on GitHub (Sep 28, 2024): @Snuupy , reminders syncing across devices should be fixed
mirror commented 2026-03-23 20:48:29 +00:00
Author
Owner
Copy link

@Fau57 commented on GitHub (Mar 4, 2025):

I'd love to be involved in any way I could for this

<!-- gh-comment-id:2698729669 --> @Fau57 commented on GitHub (Mar 4, 2025): I'd love to be involved in any way I could for this
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
copilot/fix-date-format-issue
feat/mention_a_person
merge_upstream_v6
mobile/release/0.9.3
release/0.9.3
release/0.9.2
select_source
release/0.9.1
refactor_import_data
release/0.8.9.1
release/0.8.9
anon_user_mode
release/0.8.8
fix_windows_selection
release/0.8.7
annieappflowy-patch-1
windows_local_ai
release/0.8.6
release/0.8.5
release/0.8.4
chore/optional-response-format
release/0.8.3
release/0.8.2
release/0.8.1
release/0.8.0
release/0.7.9
feat/support-rename-workspace
chat_rag_only
calculate_ui_test
release/0.7.8
release/0.7.7
stringfi_cells
hotfix/0.7.5
release/0.7.4
client-api-update
feat/collab-editing
fix_calculation_bug
feat/upload-file-in-document
update-client-api
feat/support-global-comment-on-web
update-client-api-2
feat/support-duplicate-publish-on-web
feat/ai-plan-billing
chore/test-web-deploy
chore/enable-billing-for-testing
build/test
ai_tag_feature
chore/enable-billing-plan
feat/billing-client-windows
chore/support-openai-chat
fix/try-no-media-kit
sign-in-error-format
workspace-invite-ci-test
last-workspace
workspace-invite-wip
feat/date-text-input
appflowy_v1
0.11.1
0.11.0
0.10.9
0.11.2
0.10.7
0.10.6
0.10.5
0.11.3
0.11.4
0.10.8
0.10.4
0.10.3
0.10.2
0.10.0
0.10.1
0.9.9
0.9.8
0.9.7
0.9.5
0.9.6
0.9.4
0.9.3
0.9.2
0.9.1
0.9.0
0.8.9
0.8.8
0.8.7
0.8.6
0.8.5
0.8.4
0.8.3
0.8.2
0.8.1
0.8.0
0.7.9
0.7.8
0.7.7
0.7.6
0.7.5
0.7.4
0.7.3
0.7.2
0.7.1
0.7.0
0.6.9
0.6.8
0.6.7.2
0.6.7.1
0.6.7
0.6.6
0.6.5
0.6.4
0.6.3
0.6.2
0.6.1
v0.6.1
0.6.0
0.5.9
0.5.8
0.5.7
0.5.6
0.5.5
0.5.4
0.5.3
0.5.2
0.5.1
0.5.0
0.4.9
0.4.8
0.4.7
0.4.6
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.3.9.1
0.3.9
0.3.8
0.3.7
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.9
0.2.8
0.2.7
0.2.6
0.2.5
0.2.4
0.2.3
0.2.2
0.2.1
0.2.0
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.9.1
0.0.9
0.0.8.1
0.0.8
0.0.7.1
0.0.7
0.0.6.2
0.0.6.1
0.0.6
0.0.6_beta.1
0.0.5.3
0.0.5.2
0.0.5.1
0.0.5
0.0.5_beta.2
0.0.5_beta.1
0.0.4
0.0.4_beta.3
0.0.4_beta.2
0.0.4_beta.1
0.0.3
0.0.3_beta.2
0.0.3_beta.1
0.0.2
0.0.1
Labels
Clear 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

Mirrored from GitHub 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 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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#1371
No description provided.