We reworked the production workflow

This is probably the change that affects the way we use Peliku the most.

Our old workflow wasn't terrible, but the more we used it, the more we found little moments where the stages didn't quite match what we were actually doing.

A script could be finished without the video being ready to film. An edit could be finished without the content being ready to publish. And ideas needed a clearer place before they became real production projects.

So we rebuilt the workflow around the way a piece of content actually moves through production.

Ideas stay ideas until we're actually ready to make them

We have lots of ideas. That doesn't mean we want all of them mixed into the content we're actively producing.

Ideas now stay in the Ideas space while they're still just possibilities. Once we decide we're actually going to make something, the project can move into Preparation.

It sounds like a small distinction, but it makes the active production much easier to understand.

Preparation now has a real place

Before writing the script, we often need to decide what we're making, who we're talking to and what the video is supposed to do.

That's what Preparation is for.

It gives us a proper stage between "we're making this" and "we're writing this".

Ready to shoot is separate from Script

We added this because a finished script doesn't always mean we can turn the camera on.

We might still need shots, props, equipment, a location or another part of the filming preparation.

Now we have a clear point where we can say: yes, this one is genuinely ready to film.

Approved, Scheduled and Published are different things

We also wanted the end of production to be clearer.

A finished edit can be approved without being scheduled yet. A scheduled video isn't published until it actually goes live.

Separating those stages makes it much easier to see what is really happening with finished content.

The Content page has been redesigned

Once the workflow changed, the Content page needed to change with it.

We wanted to be able to look through our projects and understand more without opening every single one.

So we've reworked the way content is displayed and made the information around each project much clearer.

• Clearer content cards
• Color-coded production statuses
• Several platforms visible on the same content
• More useful filters
• Shooting and publication dates shown separately
• A cleaner view when the content library starts growing

We especially wanted to stop treating the shooting date and publication date as if they were basically the same thing. They're two very different moments in production, so they now have their own place.

The Pipeline now follows the real production workflow

The Pipeline has been reorganized around the new statuses too.

The columns now follow the actual production journey, which means we can look at the Pipeline and immediately see what's waiting for a script, what's ready to shoot, what's being edited and what's waiting to go live.

This was one of those changes that became obvious once we had the new workflow in place. If the Pipeline is supposed to show production, it needs to speak the same language as the rest of the app.

The Dashboard has changed a lot too

We've kept working on the Dashboard because it's the page we want to open when we're not sure where to start.

Instead of being another place showing random information from the app, we're trying to make it answer a more useful question: what should we know right now?

The new Dashboard brings together:

• The Daily Brief
• Focus mode
• An overview of production
• Upcoming shoots
• Upcoming publications
• Tasks
• Appointments

And this information can now work across our workspaces instead of making us think about one space at a time.

The Daily Brief gives us a quick starting point

Sometimes we don't want to explore several pages just to understand the day.

The Daily Brief gives us a simple text overview of what matters, so we can get our bearings before deciding where to go next.

Focus mode helps us reduce the noise

The opposite problem happens when there's too much information.

Focus mode is there for the moments when we don't need the whole production picture. We just want to concentrate on what we're doing now.

We also reworked the Ideas page

Ideas have become more important now that they're clearly separated from active production.

So the Ideas page has also been redesigned to fit the new interface and make it easier to browse the things we might want to create later.

The goal is to keep ideas easy to capture without making the production area feel full of projects we haven't actually decided to make.

---

The whole interface is getting a new look

Peliku 1.3 isn't only a workflow update. We've also continued the visual redesign across the application.

The Dashboard, Content page and Ideas page are part of that, but there are smaller changes everywhere too.

• New status badges
• New icons
• Better platform display
• Clearer information hierarchy
• More consistent spacing and layouts
• Better readability across the app

We don't want the interface to be decorative for the sake of it. The redesign is mainly about making it easier to understand where we are and what we can do next.

We improved the help for new users

Peliku has changed quite a bit since some of the original tips and tutorials were written.

That meant some explanations no longer matched the app as well as they should.

We've gone back through that guidance and updated it so the help inside Peliku actually reflects the features and workflow people are seeing now.

We want someone discovering Peliku to understand why something exists, not just be told which button to click.

Plans and team seats are easier to understand

The way subscriptions and team seats work can become confusing pretty quickly, especially when several plans and different types of members are involved.

So we've added more help directly to the Team and Subscription pages.

The goal is to make a few things much clearer:

• The difference between Creator, Team and Enterprise
• Who pays for what
• When a member uses an Enterprise seat
• When a member doesn't use one

We don't want people to need a spreadsheet just to understand which Peliku plan they're using.

Peliku's update system is much more reliable

This is one of the changes that isn't very exciting visually, but it matters a lot.

We completely changed the way Peliku detects new versions.

The app now checks an independent source hosted through Supabase. That means Peliku can detect that a newer version exists even if a browser is temporarily still connected to an older deployment.

Updates can happen automatically when it's safe

We obviously don't want the app refreshing in the middle of writing a script or changing a project.

So Peliku can now apply an available update automatically when there are no unsaved changes in progress.

If we're writing or editing something that hasn't been saved yet, Peliku waits.

We can also update manually

When a new version is available, a banner can let us launch the update ourselves instead of waiting.

We've also automated more of the activation process after a new release is published, with checks to make sure the new deployment is actually available before Peliku tells everyone to switch to it.

Content can now use banners too

We already had visual banners for ideas, and now the same system is available for content.

We can choose a banner when creating content or change it later from the General tab.

And when an idea already has a banner and becomes content, we can simply keep it.

A real thumbnail still wins

The banner is there to make projects easier to recognize visually while we're working on them.

If the content has a real thumbnail, that thumbnail stays the priority. We're not replacing the finished visual with a decorative banner.

Peliku now remembers some of our creation habits

This is a small quality-of-life change we wanted because creating similar content often meant choosing the same options again and again.

Peliku can now remember locally:

• The last platforms we selected
• The last format we used

The next time we create something, those choices can already be filled in.

And we keep the preferences for ideas and content separate. Choosing something while creating an idea doesn't need to change the defaults we use when creating content.

We've added more information to content preparation

The General tab already let us keep things like the goal, audience, angle and main message around the project.

We've now added three more optional fields:

These fields aren't there to turn every Reel into a marketing exercise. We just wanted somewhere to keep those decisions when they're useful for a project.

The Peliku community is coming closer to the app

We've started integrating the Peliku Discord community in more places.

There's now access to Discord from areas such as Settings and the quick-access menu.

Users can also receive a one-time invitation to join the community.

Discord is available before creating an account too

We also added access from the login screen.

That means someone who hasn't created a Peliku account yet can still join the community, ask questions, talk with other users or get help before deciding whether Peliku is right for them.

We like the idea that the community doesn't have to start after signup. If someone is curious about Peliku and wants to talk to us first, they should be able to.

Notifications now understand the workspace we're in

Notifications become more useful once Peliku is used collaboratively, but they also need to make sense in context.

For example, mentions in content discussions are useful when we're working with other people. They aren't particularly useful in a personal workspace where there's nobody else to mention us.

So notifications now take the active workspace into account.

Mentions appear where they make sense

Notifications linked to @mentions in content discussions are available in compatible collaborative spaces.

In personal spaces, those collaborative notifications stay hidden because they don't have a useful role there.

We can also see when another workspace needs our attention

There's now a visual indicator when a notification is waiting for us in another workspace.

This matters once we're part of several spaces. We don't want to manually open every workspace just to check whether someone mentioned us somewhere else.

Tutorials and smaller interface details got some attention too

A lot of this update is made up of little changes that probably won't get their own screenshot, but make Peliku nicer to use.

The Notifications page now has its own tutorial

As notifications become more important for collaborative spaces, we've added guidance directly to that page too.

Mobile tutorials behave better

We fixed the positioning of tutorials on mobile so their buttons aren't hidden behind the navigation.

A tutorial isn't very helpful if the button needed to continue it is underneath another part of the interface.

Date fields are clearer in dark mode

We've improved the date field icon so it remains easier to see when Peliku is being used in dark mode.

The current Peliku version is visible in the sidebar

We've added the version number discreetly to the sidebar.

It's a small addition, but useful when we're checking whether an update has been applied or helping someone troubleshoot something.

The demo has been improved

We've also continued cleaning up the demo experience and the example data inside it.

If someone is discovering Peliku through the demo, we want the examples to make the app easier to understand instead of creating more questions.

The trash can now be emptied in one go

Until now, cleaning up deleted items could become pretty repetitive.

Peliku 1.3 adds the option to empty the entire trash in one action.

Because that's obviously not something we want to trigger by accident, Peliku asks for confirmation before anything is permanently deleted.

We also made the operation safer behind the scenes

Emptying the trash is handled atomically.

In simple terms, we don't want Peliku to delete half the trash and then stop because something went wrong. The operation is designed to complete as one action instead of leaving us with a partially deleted state.

---

There's also a lot of work in Peliku 1.3 that we can't really show

Some of the longest parts of an update aren't necessarily the ones that produce a new button.

We've continued working on the things underneath Peliku too, including security, subscriptions, permissions, team management and the general stability of the application.

It's not the kind of work that makes a very exciting before-and-after screenshot, but it matters more and more as Peliku grows.

Peliku 1.3 changes a lot without changing what Peliku is for

When we look at the full list, this update touches a lot of different parts of the app.

But they're all moving in the same direction.

We want Peliku to help us go from a rough idea to published content without having to rebuild our organization at every stage.

The new workflow makes production clearer. The redesigned pages make projects easier to read. The Dashboard gives us a better view of what's happening now. Preparation has more useful context. Updates are safer and easier to apply. And the collaborative parts of Peliku are starting to understand workspaces much better.

We're also trying to remove little bits of friction wherever we find them, whether that's remembering the last format we used or being able to empty the trash without deleting every item individually.

None of those things alone completely changes Peliku. Together, they make the app feel much closer to the way we want to work.

---

What's coming next?

The workflow and interface are getting much closer to where we want them, which means we can start pushing further into the parts that happen around publication and files.

There are four big areas we're working toward next.

Connecting social media accounts

We want to connect supported social accounts directly to Peliku.

The goal is to stop the workflow from ending with "now go to every platform and publish everything manually."

We're working toward direct publishing to platforms such as YouTube, Instagram and TikTok from Peliku.

Publication statistics inside Peliku

Publishing is only part of the story. Once content is live, we also want to know what happened.

We're working toward bringing social statistics back into Peliku so we can see performance alongside the project that created it.

That should make it easier to learn from published content without disconnecting analytics from the rest of the production workflow.

Built-in file storage

Files are another big part of production that still depends heavily on external tools.

We currently work with services such as Google Drive and Dropbox, but we want Peliku to offer its own file storage too.

The idea is to be able to keep project files with the content itself instead of always needing another storage service in the middle.

A dedicated mobile app

Peliku already works on mobile, and we're continuing to improve that experience.

But once the final version is stable, we also want to build a dedicated mobile application.

We don't want to rush that while the core product is still changing quickly. We'd rather stabilize the experience first and build the mobile app on top of something we're happy with.

Peliku 1.3 feels like a new chapter for us

A lot has changed since the first version of Peliku.

And honestly, some things will probably change again. That's part of building something we use ourselves.

We add a feature, use it in real projects and sometimes realise there's a much better way to do it. That's exactly what happened with parts of the production workflow and several of the pages we've redesigned in this update.

Peliku 1.3 gives us a much stronger base for what comes next. The workflow is clearer, the interface is easier to read and the less visible parts of the application are becoming more reliable too.

Now we can start connecting more of the things that still happen outside Peliku.