Devlog #26: What's next
Current state of Quedula and directions for the near future.
Current state of Quedula and directions for the near future.
Looking back on six months of building Quedula and sharing observations.
What we accounted for when working with large video files — from upload to API transfer.
How we approached interface design — without a dedicated designer on the team.
How we made video upload comfortable — progress, states, errors.
Implementation details of the description editor with Markdown support and preview.
How we built the action history for users and what goes into it.
How we release new versions of Quedula — without going into infra details.
Our testing approach: what we cover with unit tests, what with integration tests.
What we validate on the Quedula side before a video goes to TikTok.
How we document internal APIs and why schemas matter more than comments.
How we implemented two-language support in the product without hacks.
How we added drag-and-drop for rescheduling posts and what came out of it.
Why Quedula has both views and how we decide which to show by default.
How drafts work in Quedula and why we made them first-class objects.
How we refresh TikTok API tokens so publications don't fail due to expired auth.
How we implemented video preview directly in the scheduler.
Why we chose object storage for video files and how it's structured.
How we built simple but sufficient authorization for the internal admin panel.
How we handle user time and why UTC internally is the only right choice.