Repository navigation
Replies: 1 comment 1 reply
|
Thanks for flagging it, and you are right. It is worth saying at the outset that this is not one fix, it is a shell problem plus a list problem, and the shell is what makes every page unusable today. What is actually wrong. The admin layout renders the sidebar at a fixed What I think the scope should be. The realistic phone job is check and act: see today bookings, cancel or reschedule one, glance at availability. Configuring an event type with six intake questions on a phone is a rare task and probably not worth what it would cost, so I would scope this as "read and act on mobile, configure on desktop" rather than a full responsive port. Being explicit about that is better than half-doing everything. Rough order, cheapest win first.
What I would keep out of a first slice. Availability and the calendar month view. A seven-column week grid with drag interactions does not shrink to a phone; that needs a different presentation on small screens, not a smaller grid. Treating those as their own piece of work stops them sinking the rest. Why it is a reasonable thing to pick up. It is isolated: admin SPA only, no backend change, no public booking surface, so regression risk is low. One question that would help prioritize: which pages do you actually need on a phone? If it is mostly the bookings list then step 1 plus step 2 for that one page is a genuinely useful release on its own, and the rest can follow. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I've been using Calnode for a few days and I notice the admin side of this tool is not mobile friendly. Would be great to optimize calnode for mobile use too for admins
All reactions