Version of the App:
Adobe Express Mobile: Version 0.0.1
Adobe Express Desktop: Web version on Chrome (latest as of May 2025)
Platform and OS Version:
Mobile: iPhone with iOS 18.3.2
Desktop: PC running Windows 11 Pro
Summary of the Issue:
Draft posts created in the iOS version of Adobe Express do not appear at all on the desktop/web version. Additionally, there is no visible “Unscheduled Posts” section in the iOS app, meaning any unscheduled posts created on desktop can’t be accessed or edited from mobile. This severely limits the ability to work fluidly across devices.
Steps to Reproduce the Problem:
On the Adobe Express iOS app, upload a video into the Content Scheduler and save it as a draft post.
Open Adobe Express on desktop and check for that draft. It will not appear.
On mobile, remove the scheduled date from the draft post, prompting the app to confirm that the post will be moved to Unscheduled.
Check the desktop version again. The unscheduled post still does not appear.
On desktop, create a text-only post and move it to the Unscheduled Posts section.
Return to the iOS app — you’ll find there is no Unscheduled section, and the post is not accessible.
Expected Result:
Draft posts saved in the iOS app should appear on desktop.
Removing a scheduled date on iOS should sync the post into the desktop's Unscheduled section.
Desktop-created Unscheduled posts should be visible in the mobile app.
Both versions should have consistent access to all post statuses.
Actual Result:
Drafts created in the iOS app are not visible on desktop.
Unscheduled posts from mobile do not show up on desktop.
Desktop-created Unscheduled posts are not accessible on iOS, which has no Unscheduled section at all.
Impact:
This breaks basic cross-platform functionality. I often edit & upload videos from my phone and write or schedule captions on my laptop. Without proper syncing of drafts and unscheduled posts, the Content Scheduler is difficult to use in any kind of fluid or professional workflow.
Would appreciate any input from the Adobe team or community — is this a known bug, or is there a fix on the way?
Thanks!