Design

The Schedule Timeline

Jun 16, 2014

After a ton of work on the budgeting side of Cushion, I decided to step back and focus on scheduling. I met with a few more fellow freelancers and the verdict seems to be that scheduling is a day-to-day activity, whereas budgeting is done less often—maybe week-to-week. If this is the case, I definitely want to have scheduling from day one, so everyone could get some frequent use out of Cushion. A weekly-used app won’t cut it.

2014-06-15-schedule-tabs

The navigation for switching between the scheduling and budgeting views stumped me for a few days. With the model tabs as an established navigation on the app, I didn’t want to add anything that would compete too much. I decided to scrap the Cushion title in the top-left for now. With UI real estate becoming a premium in this app, that spot is much better suited for the view switcher—it also allows more views in the future.

Along with the positioning of the view tabs, I had difficulty deciding on a URL structure, since this completely flips the current one on its head. With these two views, essentially every page will have two pages—one for scheduling and one for budgeting. If you look at a project page, instead of /projects/:id, it would be /projects/:id/schedule or /projects/:id/budget. This makes complete sense, but for some reason, it didn’t seem like the clear answer at first. I started thinking of what /projects/new would be, since it currently shows the budgeting timeline. Would it now show both scheduling and budgeting, or neither?

2014-06-15-schedule-coded-vs-mockup

The scheduling timeline layout has been designed from the start of the app, but now that I needed to code it, a new challenge arose. Positioning a bunch of rectangles in a mockup is easy—the positioning logic is executed by the designer. With code, the simplest layout could come with a few hurdles of its own. For the scheduling timeline, all projects should rest on the baseline if they fit. If a project overlaps another project, it should rest above it.

2014-06-15-schedule-timeline

Unfortunately, this can’t be done solely with CSS, like the budgeting timeline. After a few searches describing the layout I was after, I found a chart that depicted the basic idea. It’s called a “swim lane” and is often used in flow charts. Once I saw the code required, I realized that this layout is actually pretty simple. Since I have start and finish dates for each project, I can just check for overlaps with those dates—no need for hit-detection. If a project’s finish date comes after another project’s start date, but its start date comes before that project’s finish date, you have an overlap. Upon finding an overlap, simply use a new “lane” for that item.

2014-06-15-actual-schedule

At the moment, I have two dates for each project—started_on and finished_on. These represent the actual dates for when the project started and finished, not their planned dates, which is why I use the past-tense. The next step is to add two more dates for estimated start and finish dates. These will be set upon creating the project and represent the agreed upon dates with the client. When you start a project, you set its started_on date and its finished_on date upon completion, so we have something to diff against. These four dates will let you see which clients are late to start or which ones drag on too long. From there, I can then find trends in specific clients.

Share this on Twitter or Facebook

Archive

  1. My Typical Week as a Startup Founder
    Story
  2. Building Components in a Sandbox
    Dev
  3. Reactive Time with Vue.js
    Dev
  4. Visualizing Daylight Saving Time
    Dev
  5. Recording Screencast GIFs
    Dev
  6. Writing a Job Listing
    Story
  7. Using Feature Flags to Run Betas
    Dev
  8. Our First Company Lunch
    Story
  9. How to embed Vue.js & Vuex inside an AngularJS app... wait what?
    Dev
  10. Funding Cushion
    Story
  11. Hiring a Team of Freelancers
    Story
  12. Taking a Real Break From Work
    Story
  13. Slack as a Notification Center
    Dev
  14. Document Your Features
    Story
  15. 300
    Story
  16. Vacations
    Design
  17. Offering Discounts
    Design
  18. Waves of Traffic
    Story
  19. Less Blogging, More Journaling
    Story
  20. Retention Through Useful Features
    Design
  21. The Onboarding Checklist
    Design
  22. Spreading the Word
    Story
  23. From Beta to Launch - The Subdomain
    Dev
  24. From Beta to Launch - Sign up
    Design
  25. From Beta to Launch - Messaging
    Design
  26. Launch
    Story
  27. Authenticating with 3rd Party Services
    Dev
  28. Intro to Integrations
    Design
  29. Inspiration vs Imitation
    Story
  30. The Emotional Rollercoaster
    Story
  31. Designing Project Blocks
    Design
  32. Everything in Increments
    Story
  33. Deleting Your Account
    Design
  34. Designing the Subscription Page
    Design
  35. Rewriting the Timeline
    Dev
  36. Restructuring the Individual Project Page
    Design
  37. Project Blocks
    Story
  38. Redesigning the Homepage
    Design
  39. Multiple Timelines
    Design
  40. Archiving and Estimate Differences
    Design
  41. Multiple Financial Goals
    Design
  42. Zooming in on the Timeline
    Design
  43. Currency
    Dev
  44. Preferences, Accounts, and a Typeface Change
    Design
  45. Sending Out the First Email
    Story
  46. Currency Inputs, Notifications, and Invoice Nets
    Design
  47. Dots and Lines
    Design
  48. Calculating in the Database and Revealing Tendencies
    Dev
  49. Improved Form UX
    Design
  50. Cushion is Online
    Story
  51. Schedule Timeline Patterns
    Design
  52. A Slimmer Schedule Timeline
    Design
  53. The Schedule Timeline
    Design
  54. Plugging in Real Data for the First Time
    Design
  55. Transitions and Project Lists
    Design
  56. Death to Modals
    Design
  57. The Individual Project Page
    Design
  58. Estimated Incomes and Talks with Other Freelancers
    Story
  59. Statuses to Lists and the Paid Beta
    Story
  60. The Timeline
    Story
  61. Invoice Terminology
    Dev
  62. Modal Forms
    Dev
  63. Wiring the Backend to the Frontend
    Dev
  64. Balancing Design and Dev
    Story
  65. Timecop, Monocle, and Vagrant
    Dev
  66. Going with Ruby and Sinatra
    Dev
  67. Ditching local-first and trying out Node.js
    Dev
  68. Switching to AngularJS
    Dev
  69. Building the Table with Vue.js
    Dev
  70. Clients, Projects, and Invoices
    Dev
  71. Introduction
    Story

Ask a Freelancer

A podcast series where experienced freelancers answer questions about freelancing.

Listen to the Podcast

Talking Shop

An interview series where we talk to freelancers about important topics in the freelance world.

Read the Interviews

Running Costs

Take a close look at the costs that go into running a web app and why we use specific services.

View the Costs

How It’s Made

Follow along with the journal for insight into the overall experience of building an app.

Read the Journal