<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The Cushion Journal - Medium]]></title>
        <description><![CDATA[Building an app from idea to launch - Medium]]></description>
        <link>https://medium.com/the-cushion-journal?source=rss----3323a709bc75---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Cushion Journal - Medium</title>
            <link>https://medium.com/the-cushion-journal?source=rss----3323a709bc75---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:39:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-cushion-journal" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Recording Screencast GIFs]]></title>
            <link>https://medium.com/the-cushion-journal/recording-screencast-gifs-c2743fb00273?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/c2743fb00273</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[screencast]]></category>
            <category><![CDATA[gif]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Tue, 21 Mar 2017 16:28:49 GMT</pubDate>
            <atom:updated>2017-03-21T16:28:49.393Z</atom:updated>
            <content:encoded><![CDATA[<p>I use GIFs a lot. So much so that I <a href="http://destroytoday.com/writings/gif-workflow/">wrote a blog post</a> about the perfect GIF workflow using Alfred and Dropbox. Aside from reacting to tweets with a <a href="https://dl.dropboxusercontent.com/u/121678/gifs/seinfeld-jerry-enough-thats-it-nope.gif">favorite Seinfeld clip</a>, GIFs provide a fantastic way to capture and share new features in <a href="https://cushionapp.com/">Cushion</a>. I can record an interaction to <em>really</em> show off the little details that make it special, rather than simply sharing a screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4UaLRyuLL3IPpbQn.png" /></figure><p>For the past few years, I’ve relied heavily on a little-known app named <a href="http://www.cockos.com/licecap/">LICECap</a>. Despite the unfortunate name, this single purpose app was great for quickly and easily recording a segment of the screen as a GIF. After a while, however, I noticed that the quality of its generated GIFs wasn’t ideal. With Cushion’s subtle variation of light grey colors, LICECap had trouble distinguishing between them all and would often remove a few when optimizing. I also had to record a GIF several times to get it right because LICECap didn’t provide any way of editing a clip after the fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*akzcssMQsNufww9J.png" /></figure><p>I decided to try a different workflow, which involved multiple apps and several additional steps, but would preserve the colors and quality I was after. In this new workflow, I would record the interaction using <a href="https://www.telestream.net/screenflow/overview.htm">ScreenFlow</a> — an app for recording and editing video screencasts. After exporting the screencast, I would import the video file into Photoshop and save for web as a GIF — making sure to optimize it enough to reach the 5mb maximum filesize for Twitter uploads.</p><p>Phew.</p><p>This workflow certainly wasn’t ideal and took much longer than using LICECap, but the GIF quality it produced was worth it… until recently. Earlier this year, I stumbled upon an app created by <a href="http://giphy.com/">Giphy</a>, the internet’s beloved GIF search engine. The app is called <a href="https://giphy.com/apps/giphycapture">Giphy Capture</a> and it’s by far the best way I’ve found to record a screencast GIF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*34ui3Ca2g8DtBoW9.png" /></figure><p>The app itself is expectedly rough and quirky — even the filename, which is in all caps. When you open the app, it shows a transparent, cyan window, which is your recording area. Clicking record starts capturing the screen, then clicking the stop button ends the recording.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hxvVxrQBuQ-9z711.png" /></figure><p>Once you’ve finished recording, Giphy Capture lets you trim the clip or edit its dimensions, frame rate, or looping style. Even if you maximize the settings to full size and a high frame rate, the filesize is still incredibly small, so I choose these settings every time. Unfortunately, the app doesn’t have a way of saving default settings, so each time I record a GIF, I need to adjust the settings before saving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AO-kmCA0kmMp6fKT.png" /></figure><p>When you’re ready to save the GIF, you can either download it as a file or upload it to Giphy. I save the GIFs to my hard drive, so I can keep local copies and easily upload them to Twitter or our website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*cvtfOl0YB0uxkfksAYil7Q.gif" /></figure><p>Compared to LICECap and ScreenFlow, I’m blown away by the quality of Giphy Capture’s GIFs. The frame rate is smooth, Cushion’s light grey colors are defined, and the filesize is surprisingly small. Despite its scrappy feel, Giphy Capture is my new go-to tool for recording interactions. If you need a screen recording app for GIFs, definitely give <a href="https://giphy.com/apps/giphycapture">Giphy Capture</a> a try.</p><p><em>Originally published at </em><a href="https://cushionapp.com/journal/recording-screencast-gifs"><em>cushionapp.com</em></a><em> on March 21, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2743fb00273" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/recording-screencast-gifs-c2743fb00273">Recording Screencast GIFs</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing a Job Listing]]></title>
            <link>https://medium.com/the-cushion-journal/writing-a-job-listing-7f1fbd13e5f?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f1fbd13e5f</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 00:58:42 GMT</pubDate>
            <atom:updated>2017-03-20T00:58:42.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently at <a href="https://cushionapp.com/">Cushion</a>, we realized that we need to hire a front-end dev. I think it was when we discovered that our GitHub Issues list is 10:1 front-end/backend, or the dozen features we launched on the backend, but are hidden because they have no front-end. As the founder, designer, front-end dev, and customer support person, I’m spread pretty thin, but I make up for it by spending my time wisely and working all hours of the day — the passion for what we have planned keeps me going.</p><p>On my own, I was able to keep a consistent pace, but once I hired our backend dev, <a href="https://twitter.com/larrythefox">Larry</a>, the pace changed. Larry is <em>really</em> fast and only focuses on the backend, so while I’m designing a new feature or writing a post like this one, he’s already wrapping up another feature. In his first month alone, he launched <a href="http://cushionapp.com/blog/overbooking">three</a> <a href="http://cushionapp.com/blog/availability">major</a> <a href="http://cushionapp.com/blog/availability-badge">features</a> almost entirely on his own. I absolutely love the progress, but feel bad for not keeping up. I decided that it’s time to hire.</p><p>This is terrifying because the process itself is completely new to me. With Larry, I worked with him in the past and he expressed interest in joining Cushion without me asking. Hiring him was simply a matter of letting him join. Our current situation is quite different — we don’t have an obvious person in mind who we’ve worked with in the past, so we need to look outside of our own network and post a <a href="http://cushionapp.com/jobs/front-end-dev">job listing</a>.</p><p>Writing the job listing was an interesting exercise because I had to really think about Cushion as a company and describe how we work as a team. I’m not a big fan of job listings because most of them are written in a way that leaves me more intimidated than interested (“You are <em>this</em>, You are <em>that</em>”, etc.) I wanted ours to be inviting and casual — identical to how we are as a team.</p><p>I started simply writing about how we work. Our schedule was never intentionally structured in a specific way, but rather an organic result of showing up each day. I spend the morning at home, then wander in the late afternoon. Larry gets to the studio early and leaves before the rush. We sync up when we need to, but otherwise, we know what we need to accomplish.</p><p>Describing what we need in a front-end dev was the tough part because I latched onto specific tech — must know SASS, bonus points for knowledge of Vue.js, etc. My friend <a href="https://twitter.com/riklomas">Rik Lomas</a> of <a href="https://www.superhi.com/">SuperHi</a> recently hired a few people, so he had a several pointers for me. The most important one was to dial down the tech specifics. By listing Vue.js, we’re filtering out people who see that as something they <em>don’t know</em> rather than something they <em>can learn</em>. We mention that we’re interested in someone who is passionate about learning, so if the person is familiar with <em>any</em> JavaScript frameworks, Vue.js will be easy to pick up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PdAkwsdtzKM0gw7L.png" /></figure><p>We kept the job listing itself concise and to-the-point, but at the end, I didn’t want to have a simple “Apply” button with a mailto link. Every company has a different hiring process, but unless you know someone who has gone through them, each step is a mystery. Keeping in line with our transparency, I decided to list the steps that we intend to follow with our hiring process, which involves applying, an interview, a paid assignment, and a 3-month trial period. By being transparent about it, there are no surprises. I doubt we’ll have anyone decide <em>not</em> to apply because of one of these steps, but it’ll at least give them a chance to come prepared with any questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fUy41koTO1v9luP9.png" /></figure><p>I also wanted more structure to the application process itself, so we could get the factual information upfront, then go from there. I decided to use <a href="https://www.typeform.com/">TypeForm</a>, which we use for our Cushion surveys. This made it quick and easy for people to apply (compared to most job listings) while funneling all of the applicants into a spreadsheet for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*izM32JAZXYxf4Msx.png" /></figure><p>Since the team is more than myself now, I wanted to involve Larry in the process, too. I set up a <a href="http://zpr.io/ZnSS">Zapier</a> integration with TypeForm to post new applicants into our <a href="https://slack.com/r/0271gg39-02e8cjv0">Slack</a> channel. Now, both of us can check out the person’s portfolio and answers as soon as they come in. Even if the team is currently only the two of us, I still value having everyone on the same page with the same information.</p><p>So far, we’ve received a few dozen applications in the first day alone and I couldn’t be happier about that. Before immediately moving onto interviews, however, we’re going to let the listing sit for now to give people enough time to see it and apply. So, if you’re a front-end dev, interested in building tools for freelancers, <a href="http://cushionapp.com/jobs/front-end-dev">we’re hiring</a>.</p><p><em>Originally published at </em><a href="https://cushionapp.com/journal/writing-a-job-listing"><em>cushionapp.com</em></a><em> on March 16, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f1fbd13e5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/writing-a-job-listing-7f1fbd13e5f">Writing a Job Listing</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Feature Flags to Run Betas]]></title>
            <link>https://medium.com/the-cushion-journal/using-feature-flags-to-run-betas-c28bdba667ac?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/c28bdba667ac</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Mon, 20 Mar 2017 00:56:08 GMT</pubDate>
            <atom:updated>2017-03-20T00:56:07.686Z</atom:updated>
            <content:encoded><![CDATA[<p>Lately at <a href="https://cushionapp.com/">Cushion</a>, we’ve been releasing most of our larger features as betas first. We do this in order to launch an MVP of the feature, then have people test it while we incrementally improve upon it. For invoicing, we ran betas for <a href="http://cushionapp.com/blog/invoicing">line items</a>, <a href="http://cushionapp.com/blog/invoice-logos">invoice logos</a>, and <a href="http://cushionapp.com/blog/sending-invoices">sending invoices</a>. Currently, we’re running betas for time tracking and <a href="http://cushionapp.com/blog/stripe-beta">accepting payments</a> through Stripe. We use “feature flags” to toggle these betas.</p><p>In all honesty, there’s not much involved in implementing feature flags. On the user model, we have a features column, which is an array of strings. Each string is a key that we use to identify a beta (invoicing, time_tracking, etc.). When a user asks to be part of a beta, we simply add the beta key to the features column and they’re good to go.</p><p>On the front-end, all we need to do is show or hide features based on whether the keys exist in the user’s features array. For the Stripe beta, we enable the ability to authorize the integration. For the time tracking beta, we simply show the tab for the time tracking section. This way, the backend never needs to know about anything.</p><p>Well, almost never.</p><p>So far, the only beta that was tricky to toggle was invoices with line items. Previously, we only had invoices with a total amount, so the line item beta required the backend to handle both types of invoices. Still, this was easy because it simply meant calculating a total for line item users and manually entering a total for everyone else. After that beta, we decided to only release betas with a simple toggle on the front-end.</p><p>For customer support, we use <a href="https://intercom.io/">Intercom</a>, which lets us tag users with specific properties. We tag beta users with the features that they’re testing and we segment them to send messages to only the testers. For our time tracking beta, we created an automated onboarding message that appears when beta users visit the time tracking section for the first time. This has been incredibly helpful for setting expectations and listing the sub-features that we’re actively working on.</p><p>As we release new betas and people request to be a part of them, using Intercom tags, we can easily see if the person has tested a previous beta. If someone has tested multiple betas, we could easily message them when a new beta is ready to test.</p><p>Because betas have a “private“ feel, most people assume that we limit the number of “spots”. We actually welcome anyone who asks. As long as they’re well-aware that the feature is in-progress and might have a few loose ends, we’re always open to another set of eyes.</p><p>If you’re interested in testing any of our new features, hit me up inside Cushion and I’ll invite you to the beta.</p><p><em>Originally published at </em><a href="https://cushionapp.com/journal/feature-flags"><em>cushionapp.com</em></a><em> on March 9, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c28bdba667ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/using-feature-flags-to-run-betas-c28bdba667ac">Using Feature Flags to Run Betas</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our First Company Lunch]]></title>
            <link>https://medium.com/the-cushion-journal/our-first-company-lunch-24b1b0e7e2eb?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/24b1b0e7e2eb</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Mon, 20 Feb 2017 15:53:24 GMT</pubDate>
            <atom:updated>2017-02-20T15:53:24.158Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ao6pxy9HbwDkwN9m.jpg" /></figure><p>Ever since moving to New York and freelancing, I’ve worked out of a co-working space, which is now where we work on <a href="https://cushionapp.com/">Cushion</a>. Our co-working space is more of a tight-knit community than a rent-a-desk situation, so we all eat lunch together. Lunch is <em>very</em> important at our space — we even have a <strong>#lunch-train</strong> Slack channel to plan our lunches and handle reimbursement.</p><p>Occasionally, someone has a great idea for lunch, which has become known as “adventure lunch”. On a typical day, we’d pick up food from a nearby place, order delivery, or bring leftovers from home. Adventure lunch is when someone suggests going to a restaurant that involves a long walk or ride on the subway — it’s a real treat and a great way to close out a long week.</p><p>An extension of the adventure lunch is what we call the “executive lunch”. We have a few small companies at our space among a wider group of freelancers. Whenever one of us is taking an executive lunch, it’s simply an adventure lunch that’s business-related. Recently, Cushion took its first-ever executive lunch.</p><p>Larry and I rode the subway to DUMBO, walked past our old building at 10 Jay St, and ended up at the finest restaurant for a business meeting — Shake Shack. We talked about our upcoming plans for Cushion, discussed how everything’s been going, and brainstormed what we could do to improve. We also made the mistake of ordering double burgers, cheese fries, <em>and</em> milkshakes. Larry had the brilliant idea of skipping a few subway stops, so we could walk off the extra pounds. We arrived back at the studio and got back to work.</p><p>I’m writing about this because I started my career in the corporate tech world where team dinners were at fancy restaurants — the kind of place I’d never dream of going with my own wallet. If we were with an exec, they would order for the entire table and only half of it would get eaten. The free-flowing drinks would catapult the bill into the thousands.</p><p>I think about this a lot now, and even though we have <a href="http://cushionapp.com/journal/funding-cushion">funding</a>, I’m still running Cushion the way I ran it when we were bootstrapped — the only difference is that we can now afford to hire more people. We don’t need to live beyond our means when something can be expensed. We can have just as good a time at our favorite burger spot.</p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/our-first-company-lunch"><em>cushionapp.com</em></a><em> on February 20, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24b1b0e7e2eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/our-first-company-lunch-24b1b0e7e2eb">Our First Company Lunch</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to embed Vue.js & Vuex inside an AngularJS app… wait what?]]></title>
            <link>https://medium.com/the-cushion-journal/how-to-embed-vue-js-vuex-inside-an-angularjs-app-wait-what-e10c9aa812a7?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/e10c9aa812a7</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Mon, 13 Feb 2017 00:56:48 GMT</pubDate>
            <atom:updated>2017-02-13T00:56:47.732Z</atom:updated>
            <content:encoded><![CDATA[<p>Since launching <a href="https://cushionapp.com/">Cushion</a> a couple years ago, we’ve been using <a href="https://angularjs.org/">AngularJS</a> (1.x) as our front-end framework. If you’re curious how we ended up with Angular, I <a href="http://cushionapp.com/journal/switching-to-angularjs">wrote</a> about the decision (keep in mind this was 2014). I came from an MVCS background, so Angular really resonated with me, and it has served us well this entire time. Recently, however, with our <a href="http://cushionapp.com/blog/scrolling-and-zooming">improvements</a> to the scheduling graph, we reached a point where performance has become an issue.</p><p>In previous attempts to improve performance, I found myself using <a href="https://lodash.com/">lodash’s</a> lightweight <a href="https://lodash.com/docs/4.17.4#template">template function</a> within Angular, which made me feel like I was cheating on Angular. In times when performance was absolutely crucial, I had to write raw JavaScript, which I have no problem writing, but it’s not exactly ideal for quick prototyping or iterating.</p><p>Now that our next big feature is time-tracking, I wanted to take this opportunity to try a new approach. What’s exciting this time around is that 1) there’s this new thing called the <a href="https://www.codecademy.com/articles/react-virtual-dom">virtual DOM</a>, and 2) almost every modern framework has adopted it. I was eyeing <a href="https://facebook.github.io/react/">React</a> last year (because my west coast friends wouldn’t stop raving about it), but it never really resonated with me — especially once you get into the whole Flux, Redux, Muppetdux, Hufflepux thing (those last two aren’t real). At one point, React was the only option if you wanted the performance of a virtual DOM, but one-by-one, every other framework caught on. Now, there are faster frameworks and some with a more familiar syntax to what I’m used to — like <a href="https://vuejs.org/">Vue.js</a>.</p><p>I <a href="http://cushionapp.com/journal/building-the-table-with-vuejs">tried Vue</a> a <em>very</em> long time ago, before it was even 1.0. The creator, <a href="https://twitter.com/youyuxi">Evan You</a>, borrowed a few ideas from Angular and had a similar syntax, so Vue felt like a younger brother to Angular — a lightweight alternative, but not quite there yet. Because of its solid grounding, I chose Angular. While I started building Cushion on Angular, Evan began working full-time on Vue. Fast-forward several years and Vue is the new hot framework. It also feels much more solid than when I previously tried it, and it’s <em>incredibly</em> fast because of the virtual DOM — perfect timing for me.</p><p>I gave Vue another shot and was immediately blown away by how powerful it is while still so easy to use. I also appreciated all the nice touches that were added, like <a href="https://vuejs.org/v2/guide/syntax.html#Shorthands">shorthands</a> (@click instead of v-on:click) and <a href="https://vuejs.org/v2/guide/events.html#Event-Modifiers">event modifiers</a> (@click.prevent to call event.preventDefault). Vue is now the lightweight alternative I’ve been searching for, and more importantly, it immediately makes sense to me.</p><p>The problem now is that I have years of code written with Angular and there’s absolutely no chance of me taking the time to replace Angular in one shot — especially if I want to make <em>any</em> progress on actual features. As a first step, I wondered if I could take advantage of Vue’s speed by replacing Cushion’s graphs with Vue components. I reached out to Evan — would it be possible to “embed” a Vue component within Angular? Apparently, yes! Evan pointed me to <a href="https://medium.com/@graphicbeacon/how-to-use-vue-2-0-components-in-an-angular-application-4d85bacc42dc#.ctjsp7tm0">this article</a> that suggests wrapping the Vue component with an Angular directive and using the ng-non-bindable directive to tell Angular not to interact with Vue’s HTML.</p><p>I tried using this technique and it does, in fact, work… but it’s not ideal. If I ever wanted to communicate between Angular and Vue, I would need to trigger Angular’s $apply method with every change within the Vue component. While this would be possible with some inconvenience, it didn’t feel right. Even though I <em>could</em> do it, doesn’t mean I <em>should</em> do it. The same could be said about embedding Vue within Angular, but I wasn’t ready to give up. I had one last idea.</p><p>Similar to React’s <a href="https://github.com/reactjs/react-redux">Redux</a>, Vue has its own state management library — <a href="https://vuex.vuejs.org/en/">Vuex</a>. Vuex keeps the app’s state in a centralized store rather than in the components. In my previous Angular/Vue experiment, Angular would’ve been the centralized store, as long as I called $apply with any changes—and I could only send data to Angular through the directive. With Vuex, a new possibility presented itself—what if I built time-tracking as a Vue app within Cushion? (I know this sounds so wrong, but hear me out.)</p><p>Without using Angular’s state management or http services, it serves simply as a router in Cushion. And considering Cushion’s tabbed navigation structure, I <em>could</em> contain an entire app in one of its tabs. Vue’s view model instance is incredibly lightweight and performant, so when a user switches to the time-tracking tab, Cushion can mount the instance and make any requests to the API from Vuex. Then, when the user navigates to a different section, Cushion can destroy the instance and clean up any loose ends. At this point, I no longer need to write hypothetically because I actually did this and it works <em>really</em> well.</p><p>I decided to go a step further. At its core, Vuex is simply a JavaScript object that stores data. What if I wanted more than one Vue instance to communicate with each other? For example, if a user starts a timer in the time-tracking section of Cushion and navigates to another part of the app, I’d still want them to know there’s a timer running. As long as Vuex is still available for the timer, I could destroy the time-tracking instance and mount another instance for the timer. Apparently, it couldn’t be simpler.</p><p>In Angular, there are <a href="https://docs.angularjs.org/guide/providers">providers</a>, which are by far the most confusing aspect of Angular. (After three years writing an Angular app, I still need to reference the documentation for these, and they still confuse me.) One of these providers is called a “service”, which can be used to create a single store to reference throughout the app. All it needs is a function that returns an object. With a single line of code, I can return Vuex as an Angular service. Now, I can reference the Vue app’s state across the rest of Cushion and inject it into any Vue instance by simply specifying the store. On top of that, this opens up a way for me to migrate Cushion from Angular to Vue in steps, rather than rewriting the entire app all at once.</p><p>When we’re ready to start migrating other sections of Cushion, I can start treating each section as an app. I could rewrite the Angular controllers as Vue instances, and simply create new store modules in Vuex. Everything remains modular, and I wouldn’t abuse $rootScope as much as I do right now. Eventually, I’d be able to replace Angular’s router with Vue’s router and shake all the excess weight.</p><p>So far with Vue and Vuex, I’ve been able to create a much more clearly defined app structure, with state that “can only be mutated in a predictable fashion” (to quote the Vuex docs). I’m also taking this opportunity to ween myself off CoffeeScript in favor of <a href="http://es6-features.org/">ES6</a>. As long as I’m improving one aspect of my dev life, I might as well kick another habit.</p><p>Learn more about <a href="https://vuejs.org/">Vue</a> &amp; <a href="https://vuex.vuejs.org/en/">Vuex</a>.</p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/vuejs-inside-angularjs"><em>cushionapp.com</em></a><em> on February 12, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e10c9aa812a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/how-to-embed-vue-js-vuex-inside-an-angularjs-app-wait-what-e10c9aa812a7">How to embed Vue.js &amp; Vuex inside an AngularJS app… wait what?</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring a Team of Freelancers]]></title>
            <link>https://medium.com/the-cushion-journal/hiring-a-team-of-freelancers-943789f9e803?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/943789f9e803</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Wed, 23 Mar 2016 12:24:56 GMT</pubDate>
            <atom:updated>2016-03-23T12:24:56.328Z</atom:updated>
            <content:encoded><![CDATA[<p>This past month, I did something I never thought I’d do — I hired people. From the very beginning, I always saw myself building <a href="http://cushionapp.com/">Cushion</a> as a solo developer, riding into the sunset with a small, sustainable app. I romanticized growing Cushion to the point where I could live off its income alone. Once I reached that goal, I would retire to a cabin upstate and simply maintain it for years to come.</p><p>That all sounds lovely, but it’s far from reality. Growing an app is incredibly hard — especially when you’re also the designer, developer, and support person. Aside from the daunting task of making an app profitable, loneliness starts to creep in after years of trudging in the same direction. Whereas I once dreamed of running Cushion by myself, I now dream about collaborating with a small team.</p><p>Recently, this dream has begun to take shape. Late last year, I started brainstorming with freelance writer <a href="http://twitter.com/carlyayres">Carly Ayres</a> on where to take Cushion from a content perspective. Ever since, we’ve been working toward a goal of supporting the freelancer community and providing truly useful content — not the same listicles that have overtaken every other app’s blog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8O4WWnZuK14IiM8ZK-PhA.jpeg" /></figure><p>Last week, we launched the first interview in our new series, <a href="http://cushionapp.com/blog/stephanie-hider">Talking Shop</a>, where we talk to freelancers about freelancing. Like building an app on your own, freelancing can be incredibly lonely, too. Most freelancers don’t work in a co-working space or big city where other experienced freelancers are within arm’s reach. Talking Shop is our attempt to bring the conversation to those who are eager to learn more about the freelance world from those who live in it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPBYooLuoltjmLGpXqKw-w.png" /></figure><p>Alongside Carly, I hired freelance illustrator <a href="http://pingszoo.com/">Ping Zhu</a> to illustrate each person we interview. I see illustration as a primary area where Cushion can embrace the freelancer community even further. Each piece of content we publish should be paired with its own illustration that lends itself to the writing. The content is then a collaboration between several freelancers and credited as such.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FxUazEgRwcsZ9EIlupFsOA.png" /></figure><p>In February, I hired freelance developer <a href="http://larryfox.us/">Larry Fox</a> to help with the actual app. We’ve worked really well together in the past, so I reached out immediately when he decided to go full-time with freelancing. In his first month alone, working only a few days a week, Larry and I were able to launch <a href="http://cushionapp.com/blog/overbooking">Overbooking</a>, <a href="http://cushionapp.com/blog/availability">Availability</a>, and the <a href="http://cushionapp.com/blog/availability-badge">Availability Badge</a>. Needless to say, Larry has been essential to taking Cushion where I want it to go.</p><p>If I didn’t hire the help I so desperately needed these past few months, I would probably be stuck on a single feature, spinning my wheels, and only imagining the things I want to do with Cushion. Instead, I’m leading a team of freelancers, building features at a lightning pace, and publishing new content on a schedule. I’m not alone anymore, and I think I prefer it this way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=943789f9e803" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/hiring-a-team-of-freelancers-943789f9e803">Hiring a Team of Freelancers</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking a Real Break From Work]]></title>
            <link>https://medium.com/the-cushion-journal/taking-a-real-break-from-work-70189a1ca83b?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/70189a1ca83b</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Wed, 24 Feb 2016 16:22:53 GMT</pubDate>
            <atom:updated>2016-02-24T16:22:52.900Z</atom:updated>
            <content:encoded><![CDATA[<p>Last night, I landed at Laguardia after a week-long vacation in <a href="https://www.instagram.com/p/BCGMmlPCMSw">Southern California</a>. For my <a href="http://jenmussari.com/">wife</a> and I, this was our first real vacation for only the two of us. It was also a much needed break from work — for both of us.</p><p>Since we work out of the same co-working space and set our own schedules, we tend to enable each other’s workaholic lifestyle. And, because we’re always together at work, there’s less of a pull for either of us to get home at a normal hour. Over time, this takes its toll on us, as our deadlines result in a constant string of deadlines.</p><p>We’re well-aware that we work too much, which is why we decided to get away. We traded the depressing, below-freezing weather in Brooklyn for sun and a poolside seat. At first, I thought it would be difficult to disconnect from work. Cushion has constantly been on my mind for the past two years, so I could only assume it would remain there — even if I didn’t want it to.</p><p>As soon as we arrived, however, work disappeared from my thoughts completely. Maybe it was the sun or the private patio and outdoor fireplace (we splurged a bit), but my mind was finally able to relax. Instead of deciding where to take Cushion next and what was on my agenda for the upcoming week, I let go. For the first time in a long while, I just enjoyed sitting and taking in my surroundings.</p><p>Our week of rest went by with a blink, and we’re now back in Brooklyn. This time, however, we’re fully recharged and excited to return to work. Apparently, I needed this break more than I thought — and I learned a lot from this. Even if I feel like I can’t possibly take time off, a week away won’t hurt. In actuality, a week away will help <em>repair</em> the toll I’ve taken from <em>not</em> taking a break.</p><p>I can guarantee we won’t wait another 10 years to take a vacation. We’re actually thinking about where to go next already.</p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/taking-a-real-break-from-work/"><em>cushionapp.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70189a1ca83b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/taking-a-real-break-from-work-70189a1ca83b">Taking a Real Break From Work</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slack as a Notification Center]]></title>
            <link>https://medium.com/the-cushion-journal/slack-as-a-notification-center-40f2c3fd49f0?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/40f2c3fd49f0</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Sun, 07 Feb 2016 09:01:01 GMT</pubDate>
            <atom:updated>2016-02-07T09:01:00.743Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://slack.com/r/0271gg39-02e8cjv0">Slack</a> is commonly used as a chat tool for teams, but for the past year and a half, I’ve used Slack as a notification center for <a href="http://cushionapp.com/">Cushion</a>. Until recently, I’ve been a one-person team, so people were always surprised when they learned that I had a Slack for Cushion. When you consider all of Slack’s integrations and how trigger-happy most services are with emails, Slack becomes the perfect solution for wrangling notifications into one place.</p><p>Initially, I set up every integration to use the <strong>#general</strong> channel, but this quickly became a mess of alerts. I found myself sifting through dozens of notifications, hoping to see new subscribers, but finding mostly error alerts. That’s when I decided to split the notifications into several channels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*JSwKO0IX5uboksWK.jpg" /></figure><p>The <strong>#build</strong> channel consists of two integrations — <a href="http://github.com/">GitHub</a> and <a href="https://codeship.io/">Codeship</a>. The GitHub integration is less useful for solo devs, but nice to have when referencing commits in the latest pull request. Cushion deploys through Codeship, which runs all of its tests prior to pushing to Heroku. Codeship notifications are very important because I instantly know when a build fails and, with one click, I can find out what went wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*4pW0bRKnxP_13_TX.jpg" /></figure><p>The <strong>#errors</strong> channel is tied to <a href="https://getsentry.com/">Sentry</a>, which catches any errors along with their stacktraces. Fortunately, Cushion hasn’t seen too many serious bugs, but when the occasional hiccup comes through, I try to fix it same-day. Because this channel is pretty quiet, I allow Sentry to catch non-bug errors, too, like validation errors. This helps me spot any usability issues, like a specific form field that might trip people up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*6oFmZSmKHcN5CAfe.jpg" /></figure><p>The <strong>#marketing</strong> channel keeps track of people who sign up for the newsletter. This was originally handy when Cushion was in private beta. Now, it simply gives me a positive boost with each signup. When Cushion’s expenses page reached #1 on Hacker News, this channel was a firehose. That was a good day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*L2eRu3ghcJmrSXsi.jpg" /></figure><p>The <strong>#users</strong> channel listens for new <a href="http://stripe.com/">Stripe</a> customers. Cushion requires a payment method upfront, so Stripe is a good indicator of new (real) users. These certainly aren’t guaranteed customers, but I can get a sense of how much Cushion is making the rounds based on the number of signups I see in a day. Since most users are freelancers, I often visit the website tied to their email address and check out their work. Eventually, I’d like to build a Slack integration that inserts a screenshot of a new user’s website when they sign up — that would be next level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*5Ljf49AuFx8JnQ2N.jpg" /></figure><p>Cushion also has a <strong>#stripe</strong> channel for new subscribers and charges. I originally included cancelled subscriptions, but those quickly became too depressing. To protect morale, I only whitelist the positive notifications while keeping an eye on cancellations on a day-to-day basis. Now, this is my favorite channel. Anytime it’s highlighted, I know I either received money or, even better, someone subscribed to Cushion. I can’t stress enough how important these boosts are when you’re building an app for so long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/0*SXI8EcSzB7XPbVG9.jpg" /></figure><p>The <strong>#support</strong> channel is tied to <a href="https://www.intercom.io/">Intercom</a>, which I use for Cushion’s customer support. When a user emails support or sends a message in the in-app chat widget, I receive an abridged notification in Slack. This helps me know <em>exactly</em> when a user needs help, so I can respond right away. This is important to me because delighting a users with an instant response goes a long way. At this point, I need whatever advantage I can get, so lightning-quick support is my leg-up.</p><p>Since Cushion is still young and the traffic is bearable, I’m able to handle support by myself. Considering I’m the one who designed and wrote the app, I’m also the best person to respond to questions. I often go into great detail with answers, so the user feels closer to the app than they would with a trained support person using canned responses. If Cushion really takes off, I might eventually need help with support, but I still plan to stay in the loop as long as I can.</p><p>Running Cushion with <a href="https://slack.com/r/0271gg39-02e8cjv0">Slack</a> as a notification center has helped me immensely these past couple years. Without it, I imagine my inbox would be overflowing and I’d be behind with what’s happening at any given moment. Support emails would be gathering dust and the build server would be on fire. Maybe that’s too dramatic, but it goes to show how much I love Slack.</p><p><em>ps — Sign up for Slack with </em><a href="https://slack.com/r/0271gg39-02e8cjv0"><em>this link</em></a><em> and you’ll get a $100 credit, which is 15 months free for solo paid accounts.</em></p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/slack-as-a-notification-center/"><em>cushionapp.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40f2c3fd49f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/slack-as-a-notification-center-40f2c3fd49f0">Slack as a Notification Center</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Document Your Features]]></title>
            <link>https://medium.com/the-cushion-journal/document-your-features-cd5080e51e92?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd5080e51e92</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Sun, 31 Jan 2016 14:50:39 GMT</pubDate>
            <atom:updated>2016-01-31T14:50:39.419Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I discovered that a specific feature in <a href="http://cushionapp.com/">Cushion</a> was causing confusion for almost everyone who used it. This feature was originally called “Blocks”, then “<a href="http://cushionapp.com/journal/project-blocks">Project Blocks</a>”, then “Time Blocks”, and now finally “Workloads”. Renaming the feature is another story, but I want to talk more about the support burden caused by the confusion. Any time a user had a question about the feature, they would either email me and ask to explain it, or worse — leave without caring to learn about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jRyoFIpzyDUO53ao.png" /></figure><p>Not all features are as intuitive as ones like time-tracking or invoicing. You can mention either of those features to people and they get it. Workloads, on the other hand, are a different story. They’re a new feature that fixes a specific issue in my own freelancing life, so their not yet in the project management vocabulary. Because of this, Workloads require an explanation instead of the user learning it through context.</p><p>After answering enough of these support emails and realizing the core problem, I decided it was time to build a proper support page. This was long overdue, but somehow it ended up on the list of high priorities that feel like low priorities. This support page should alleviate any need for the user to contact support. It should explain the purpose of Workloads and run through the steps to create a Workload, including screenshots for each step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hyFfbu0cXhd3jPdl.png" /></figure><p>After finishing the <a href="http://cushionapp.com/support/workloads">Workloads support page</a>, announcing it to users, and reading the responses, I could clearly see that these support pages are valuable. Not everyone is a learn-through-experience type of user — most users rely on proper documentation. Because of this, I now need to go through the backlog of features that need support pages and tackle a few each week as part of my routine. Consider this another aspect of what makes an app a real app and less of a side project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BkxYzeESFltR_QgV.jpg" /></figure><p>These types of pages tend to change over time, along with their images and image sizes, so I decided to save each one as a Sketch file. Each image on the page is an artboard with export settings to match the size of the website design. With this setup, I’m able to retain the hi-res screenshots along with the ability to re-export everything if the design or feature ever changes.</p><p>I actually look forward to building the rest of the support pages because they really give the website more depth. I can confidently point a user to one and know that they’ll get the answers they seek. This goes a long way towards the legitimacy of the app and shaves a few minutes off my usual support load.</p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/document-your-features/"><em>cushionapp.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd5080e51e92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/document-your-features-cd5080e51e92">Document Your Features</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[300]]></title>
            <link>https://medium.com/the-cushion-journal/300-5b07fd2913a?source=rss----3323a709bc75---4</link>
            <guid isPermaLink="false">https://medium.com/p/5b07fd2913a</guid>
            <category><![CDATA[process]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jonnie Hallman]]></dc:creator>
            <pubDate>Tue, 26 Jan 2016 14:57:50 GMT</pubDate>
            <atom:updated>2016-01-26T14:57:49.766Z</atom:updated>
            <content:encoded><![CDATA[<p>Yesterday was a big milestone for <a href="http://cushionapp.com/">Cushion</a>. Roughly six months after officially launching, Cushion has reached 300 paying customers. I think it’s important to celebrate these milestones, however small, because like freelancing, running an app can be an <a href="http://cushionapp.com/journal/the-emotional-rollercoaster">emotional roller coaster</a>. You might see a dozen new subscribers one week and a dozen cancellations the following week. When something good happens, it helps to bolster that feeling and keep the positive momentum going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7fu0J7riMogflmL9.png" /></figure><p>The main goal for Cushion has always been to reach a point where I no longer need client work support myself — the bootstrapper’s dream. I’ll still take freelance gigs because I believe it’s important to be a real user of your own app. You should feel the same pains as your users if an irritating bug or cumbersome workflow exists. Once you no longer use your own app, you need to rely on others to point out its hiccups, and most users aren’t that vocal — some might leave before writing an email. I digress.</p><p>With full-time as my primary target, the 300-customer milestone represents my halfway point. This alone is exciting because it means I might actually be able to pull this off. I originally built Cushion because I simply needed it. Enough of my friends shared the same need, so I decided to build it for others, too. Now that it has a chance to become my career, I’m even more determined to get there. Getting to 300 <em>did</em> take much longer than expected, but these past six months have taught me a lot. I know what I need to do to get to 600.</p><p><em>Originally published at </em><a href="http://cushionapp.com/journal/300/"><em>cushionapp.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b07fd2913a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-cushion-journal/300-5b07fd2913a">300</a> was originally published in <a href="https://medium.com/the-cushion-journal">The Cushion Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>