Our recent work at AnyShift has focused on making the app more useful for both sides of a shift: the employer organising the work and the shifter carrying it out. We have implemented new designs for employers and shifters, brought employer access into the app, added direct contracts through favourites, and implemented clock-in and clock-out. Together, these changes bring more of the everyday shift workflow into the mobile experience.

This is the first entry in our AnyShift development journal. I work on AnyShift with the team, and these updates will explain what we are building and why it matters in practice. This entry brings the recently implemented changes together in one place.

New designs for employers and shifters

We have implemented new designs in the app for both employers and shifters. The two groups use the same platform with different jobs to do. An employer is arranging work and reviewing the planning. A shifter is engaging with the work they will carry out. Both sides need an experience that makes the next action understandable.

For me, a useful way to judge a redesign is to follow a real task from beginning to end. Can someone understand where they are, find the relevant information and see what to do next? That is the practical lens behind this update. A new design should support the work happening around a shift, as well as the screen itself.

Employers can now work from the app

Employers can now log into the app, giving them another way to manage their work alongside the web dashboard. They can post shifts, handle acceptances, look at reviews and consult their time planning from the app. Employer access is therefore part of the mobile product, rather than being limited to the dashboard web portal.

The aim is straightforward: make those everyday actions easier to reach. For a hypothetical employer checking the upcoming planning away from a desk, having these functions in the app offers a direct mobile route into that work. That example explains the intended use; it is not a claim about measured time savings or a particular customer’s results.

Direct contracts through favourites

Direct contract is another feature we have implemented. The workflow is simple to describe: mark a person as a favourite, then send a contract directly to that person. It gives employers a route from a saved favourite to a direct contract, within the product.

The useful distinction is between finding people and taking the next action with someone already selected. Favourites make the selected person easier to return to; the direct-contract feature provides the next step. That gives favourites a practical role in the employer’s workflow: a selected person becomes the starting point for the contract action.

Clock-in and clock-out are implemented

We have also implemented clock-in and clock-out. This adds the start and end of the working period to the set of actions supported in the app. Alongside posting, planning and direct contracts, it extends the product beyond arranging a shift to recording when work starts and finishes.

It is useful to view those moments as part of the wider workflow. Planning describes the intended work; clock-in and clock-out relate to its actual start and finish. Keeping that distinction clear is an important product principle. The product should make those different moments understandable to the people doing the work.

Making the whole shift journey clearer

The common thread in this work is a more practical mobile experience: new designs for both groups, employer actions in the app, a direct-contract route through favourites and clock-in/clock-out. Each addresses a different moment in the shift journey. Our aim is to make the product easier to use as part of everyday work.

You can explore the product and business offering on the AnyShift website. For the wider context of my operating work, see my ventures. I will use this journal to share further confirmed developments as there is something useful to report. If you use AnyShift, tell us which task feels clear and where the next step is still difficult to find through AnyShift’s contact page.

About this update: the development details are based on my team update of 9 November 2026. The AnyShift website provides public product context. This is a first-person update about a business I work on.