<?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[Stories by Jeremy Bell on Medium]]></title>
        <description><![CDATA[Stories by Jeremy Bell on Medium]]></description>
        <link>https://medium.com/@jeremybell?source=rss-debdf0d2b8f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iBLhc80bqOJ3smGHFrhP9Q.png</url>
            <title>Stories by Jeremy Bell on Medium</title>
            <link>https://medium.com/@jeremybell?source=rss-debdf0d2b8f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:47:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeremybell/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mayday on May Day: What’s in a name?]]></title>
            <link>https://medium.com/maydaylabs/mayday-on-may-day-whats-in-a-name-15d03f798c69?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/15d03f798c69</guid>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Wed, 17 May 2023 17:59:07 GMT</pubDate>
            <atom:updated>2023-05-17T17:59:07.806Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aa_DTDm3tbfrth-K8abNqQ.png" /></figure><p>In many parts of the world, May 1st is known as May Day. And this year, I find myself reflecting on the origins of our business, the product we’re building, and the significance behind our name, Mayday. The name “Mayday” wasn’t chosen merely to evoke the first day of May; it holds a deeper meaning and speaks to the core mission of our product.</p><p>Dating back to the late 19th century, May Day bears historical importance in the labour movement, being deeply connected to the establishment of the 8-hour workday. Workers in the United States and other industrialized countries at the time were subjected to exhausting, prolonged workdays. <a href="https://en.wikipedia.org/wiki/Haymarket_affair">The Haymarket Affair</a> of 1886, which involved a series of strikes and protests advocating for an 8-hour workday as the standard for all workers, marked a turning point. May 1st was ultimately designated as <a href="https://en.wikipedia.org/wiki/International_Workers%27_Day">International Workers’ Day</a>, commemorating the accomplishments of the labour movement and promoting workers’ rights, including fair working hours and improved working conditions.</p><p>The name “Mayday” is also rooted in the internationally recognized distress signal for help. Established as a universal call for assistance in the wake of WWI, “Mayday” is derived from the French phrase “m’aider,” which translates to “help me.” This concept of providing help is central to our ethos, and our AI-assisted calendar embodies that spirit — offering support for managing time and schedules across multiple time horizons. The name playfully incorporates elements of time, with “May” signifying months, “Day” indicating days, and our URL, <a href="http://mayday.am/">mayday.am</a>, representing hours (as in AM/PM).</p><p>With its historical significance and origins as a distress signal, “Mayday” was clearly a fitting name that encapsulated the essence of what we’re building, the value we strive to deliver, and acknowledges the ongoing pursuit of a healthier balance between work and life.</p><p>Long before the name Mayday was even a consideration, the idea behind it was formed during my tenure at a health and fitness company called Precision Nutrition (PN). PN offered a year-long coaching program, and we noticed that when participants failed to complete it, it wasn’t for lack of motivation or dedication; it was often because life simply got in the way. Unexpected events, such as travel, illness, or pressing work commitments, threw their schedules off course, and the technology that supported the program wasn’t designed to adapt to these changes.</p><p>Years later, I found myself working at Facebook in Menlo Park. As I observed my team, I recognized a familiar pattern: we were all drowning in meetings, struggling to carve out time for actual work, and often needing to put in extra hours after work to get things done. Burnout wasn’t uncommon, and it seemed like everyone was juggling an impossible load, desperately trying to make time for what truly mattered each week.</p><p>That’s when it became clear that there had to be a better way, and I was certain that a smarter calendar was the way to solve this problem. And so, Mayday was born.</p><p>Mayday, as both a product and a mission, has always been about helping people regain control of their time, allowing them to focus on their priorities and strike a healthier work-life balance. And while there are plenty of calendar apps on the market, Mayday differentiates itself by leveraging AI to intelligently assist users in organizing their schedules.</p><p>It is designed to provide support across various time horizons. For example, by evaluating several data points across everyone’s schedules, our “Ideal Scheduling Engine” can determine the most suitable time to schedule events or meetings. Beyond merely looking for empty slots in calendars, Mayday weighs the urgency and importance of what you’re trying to schedule against what’s already planned, creating a more balanced and efficient calendar.</p><p>Mayday’s Scheduling Links consider everyone’s ideal time and gently nudge guests to pick a time that works best for all parties involved, rather than blindly offering up every available time slot, which could lead to interrupted focus time and unnecessary context-switching.</p><p>Calendar Shield automates time-blocking to protect your schedule from becoming overrun with meetings. It also schedules buffer time before important meetings and syncs events between calendars, ensuring that personal appointments are protected in your work calendar.</p><p>Soon, we’ll be launching auto-scheduled Tasks in Mayday, a feature that automatically blocks time in your calendar for your to-do’s. When your priorities shift, Mayday will intelligently reschedule tasks, eliminating the need for manual adjustments to your blocked time.</p><p>As May Day reminds us of our company’s namesake and the mission that fuels our endeavours, we’re committed to continually refining and improving Mayday to make it an indispensable tool for time management and prioritizing. In the spirit of May Day and championing a healthier balance between work and life, we invite you to join our journey by <a href="https://mayday.am/public-beta">downloading the public beta.</a> Your feedback will be invaluable in helping us shape the future of Mayday and ensure that it becomes the ultimate time management solution for everyone. Together, let’s take control of our schedules and reclaim our time for what truly matters.</p><p><em>[Originally posted on Mayday.am on May 1st, 2023]</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15d03f798c69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maydaylabs/mayday-on-may-day-whats-in-a-name-15d03f798c69">Mayday on May Day: What’s in a name?</a> was originally published in <a href="https://medium.com/maydaylabs">Mayday</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mayday Raises $3M to help everyone achieve Schedule/Priority Fit]]></title>
            <link>https://medium.com/maydaylabs/mayday-raises-3m-to-help-everyone-achieve-schedule-priority-fit-bf3ef9fb14f?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf3ef9fb14f</guid>
            <category><![CDATA[calendar]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[scheduling]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Mon, 07 Mar 2022 14:20:28 GMT</pubDate>
            <atom:updated>2022-03-07T14:20:28.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYGXuNG2LKihEjB0ULIFBA.jpeg" /><figcaption>Mayday Founders: Adam Day, Jeremy Bell, &amp; Brian Faber</figcaption></figure><p>We are excited to announce that <a href="http://mayday.am/">Mayday</a> has raised a USD $3 million seed round led by <a href="https://8vc.com/"><strong>8VC</strong></a> with additional participation by <a href="https://www.shasta.vc/"><strong>Shasta Ventures</strong></a>, <a href="https://www.ffvc.com/"><strong>ff Venture Capital</strong></a>, <a href="https://colle.vc/"><strong>Colle Capital</strong></a>, and others to grow our team and accelerate development towards achieving our mission of coordinating the world’s time.</p><h3>The Future of Work Needs Prioritization</h3><p>The shift to remote &amp; hybrid workplaces has dramatically changed how we spend our time. The idea of “work hours” has become blurry, with personal and work tasks demanding our attention throughout the day.</p><p>Our daily lives have become a balancing act between what’s supposed to be important and what actually is, clashing with the reality that we can’t do it all. Too many meetings. Too many distractions. Not enough time to get things done.</p><p>We need a new kind of calendar that helps us and the people we work with achieve <strong>Schedule / Priority Fit.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IaYTT_6-iilkhLFxf2U6wg.png" /></figure><h3>An Engine For Achieving Schedule/Priority Fit</h3><p>Modern calendars weren’t designed for the modern workplace. As a result, we waste a lot of time context-shifting, planning, and managing our time.</p><p>Mayday is building the world’s first truly smart calendar that learns what’s essential and plans your schedule accordingly. To accomplish this, we created the first “Priority Engine” that analyzes your calendar patterns to determine what’s important, enabling it to effectively allocate available time to support your priorities.</p><p>And when it’s time to meet with coworkers, Mayday automatically determines the ideal time that works for everyone by considering hundreds of signals from everyone’s calendar and work preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*394XEgBdWIvlGLdVdZ5ixA.png" /></figure><h3>Native Apps For All Your devices</h3><p>As our suite of APIs progresses, Mayday will be able to make more informed scheduling decisions about your entire teams’ calendar. However, as we use our calendars daily, having a fast and easy-to-use user interface is just as important.</p><p>That is why we’ve built beautiful native apps available on macOS, iOS, and iPadOS (with Android and Windows versions on the way) that are both fast and easy to use.</p><p>Our native apps also include intelligent scheduling links, which utilize Mayday’s advanced understanding of your schedule and priorities. So you may make yourself available to meet with others without sharing your entire schedule or overcommitting yourself.</p><h3>Coordinating The World’s Time</h3><p>Success at work, the strength of our relationships, and our health are tremendously affected by how we choose to spend our time every day. And we’ve completely lost our ability to manage it.</p><p>Time is our most valuable asset, but it’s been too easily lost, stolen, and misspent for too long.</p><p>To truly align people and their time, we need a smarter calendar that helps you live the life you want to live. That’s why we built Mayday — At Mayday, our mission is to coordinate the world’s time, so we can all achieve Schedule / Priority Fit.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F553424966%3Fh%3D8503bed30c%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F553424966&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1143400881-8bc2e35466f3b46a424b849159906a585f4ee3ba8d0b331cfa18f3144f4a7164-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb364e4e980941448a0249f6806888d5/href">https://medium.com/media/cb364e4e980941448a0249f6806888d5/href</a></iframe><p>Investors in this round include <a href="https://www.linkedin.com/in/alex-kolicich-b71732a/"><strong>Alex Kolicich</strong></a> and <a href="https://www.linkedin.com/in/alex-kolicich-b71732a/"><strong>Jack Moshkovich</strong></a> from <a href="https://8vc.com/">8VC</a>. <a href="https://www.linkedin.com/in/nitinchopra/"><strong>Nitin Chopra</strong></a><strong>,</strong> <a href="https://www.linkedin.com/in/jacobmullins"><strong>Jacob Mullins</strong></a>, and <a href="https://www.linkedin.com/in/joe-cashion-ab26b325"><strong>Joe Cashion</strong></a> from <a href="https://www.shasta.vc/">Shasta Ventures</a>. <a href="https://www.linkedin.com/in/johnfrankel/"><strong>John Frankel</strong></a> and <a href="https://www.linkedin.com/in/ericshu/"><strong>Eric Shu</strong></a> from <a href="https://www.ffvc.com/">ffVC</a>. <a href="https://www.linkedin.com/in/victoriakgrace"><strong>Victoria Grace</strong></a> and <a href="https://www.linkedin.com/in/douglas-benowitz"><strong>Doug Benowitz</strong></a> from <a href="https://colle.vc/">Colle Capital</a>. <a href="https://www.linkedin.com/in/alexanderlnorman/"><strong>Alex Norman</strong></a> from <a href="https://www.n49p.com/">N49P</a>. <a href="https://www.linkedin.com/in/prashantmatta"><strong>Prashant Matta</strong></a> from <a href="https://www.panache.vc/">Panache Ventures</a>. <a href="https://www.linkedin.com/in/adammcnamara/"><strong>Adam McNamara</strong></a> from <a href="https://www.ramen.vc/?utm_campaign=Investor+Update%3A+December+2021&amp;utm_content=Investor+Update%3A+December+2021&amp;utm_medium=email_action&amp;utm_source=customer.io">Ramen Ventures</a>. <a href="https://www.linkedin.com/in/christophergolda"><strong>Christopher Golda</strong></a> and <a href="https://www.linkedin.com/in/bradfordcross"><strong>Bradford Cross</strong></a> from <a href="http://rogue.capital/">Rogue Capital</a>. <a href="https://www.linkedin.com/in/brice-scheschuk-cpa-ca-095721a/"><strong>Brice Scheschuk</strong></a> from <a href="https://www.globalive.com/">Globalive</a>. Plus, angel investors <a href="https://www.linkedin.com/in/adamaflynn/"><strong>Adam Flynn</strong></a>, <a href="https://www.linkedin.com/in/rahuldkulkarni/"><strong>Rahul Kulkarni</strong></a>, <a href="https://www.linkedin.com/in/johnmaier81"><strong>John Maier</strong></a><strong>, </strong><a href="https://www.linkedin.com/in/haroonmirza"><strong>Haroon Mirza</strong></a><strong>,</strong> <a href="https://www.linkedin.com/in/john-laban/"><strong>John Laban</strong></a>, and <a href="https://www.linkedin.com/in/vigeant/"><strong>Luke Vigeant</strong></a><strong>.</strong></p><h3>Join Our Growing Team</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p2Rwub3fccTdEfhp14B-5A.png" /></figure><p>We are building a remote-first company that cares about work/life balance and have <a href="https://mayday.am/careers">open positions for several roles</a>. Our goal is to create a company (and the software) that enables everyone to have fewer meetings, more focus time, and more flexibility to work asynchronously as much as possible.</p><p><a href="https://mayday.am/careers">Apply to join the Mayday team</a> and help us make this a reality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf3ef9fb14f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maydaylabs/mayday-raises-3m-to-help-everyone-achieve-schedule-priority-fit-bf3ef9fb14f">Mayday Raises $3M to help everyone achieve Schedule/Priority Fit</a> was originally published in <a href="https://medium.com/maydaylabs">Mayday</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The World Doesn’t Need Another Calendar.]]></title>
            <link>https://medium.com/maydaylabs/the-world-doesnt-need-another-calendar-c84a09664596?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c84a09664596</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[scheduling]]></category>
            <category><![CDATA[calendar]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[time]]></category>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Wed, 21 Apr 2021 16:14:53 GMT</pubDate>
            <atom:updated>2021-05-04T20:47:30.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>The World Doesn’t Need Just Another Calendar.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TzXXs4PpWu1rq9Ndl5jow.jpeg" /></figure><p>The single most important tool we use to manage our time is the calendar. Nearly every device you own has one, and it’s likely something that you use multiple times a day, every day. We spend an excessive amount of energy monitoring, planning, and managing our time. But modern calendars were never built for the modern workplace.</p><p>Google Calendar and Microsoft Outlook are the current workplace standard, and their approach to collaboration is transparency — they make it possible for you to see your coworkers’ calendars. Beyond the obvious privacy implications, what they present is a mirage.</p><p>When viewing someone’s calendar, we’re led to believe that emptiness means availability. But what we see is an incomplete picture because we rarely record <strong>everything</strong> in our calendars. From personal events to undocumented to-dos, our calendars are not a comprehensive record of how we will be spending our time.</p><p>The scheduling back-and-forth we do over email is us struggling to reconcile this tension. Calendly, X.ai, Vimcal, Calendso, Doodle, and countless other scheduling tools were all created to address these shortcomings. But none of them are actually solving the problem.</p><p>They present an illusion of someone’s <em>true availability</em> and force you to make a scheduling decision without understanding the contextual priorities of any pre-existing event. The information asymmetry means our only option is to slot meetings between what’s already scheduled.</p><p>As a result, we manage our time on a first-come-first-served basis. Our schedules are shaped by the order in which events were added and not by the priority of the events themselves.</p><p>These challenges compound because as our calendars fill, the scheduling options decrease. Finding a time that works for all parties becomes increasingly complex, and that complexity grows exponentially with each additional attendee.</p><p>None of the current solutions truly help us become more productive, calm, or happy because they all rely on a paradigm that dates back to when we used paper calendars. We don’t need faster or prettier versions of the same old thing. What we need is a new kind of calendar that help us, and the people we’re working with, achieve <strong>Schedule / Priority Fit</strong>.</p><h3>Schedule / Priority Fit</h3><p>On the surface, Schedule / Priority Fit is a straightforward concept — determine what matters most to you, then add it to your calendar in the order of priority. But it’s really an optimization of supply and demand — the most efficient allocation of your available time put towards the most important demands for your attention.</p><p>We like to believe our calendars are a reflection of our true priorities, but they’re really an incomplete list of what we <em>intend</em> to spend time on. While some people do schedule every hour of every day, it’s incredibly uncommon.</p><p>Based on our data, the average person only has only <strong>20%</strong> of their time accounted for in their calendar. Of that scheduled time, <strong>26%</strong> goes towards solo meetings, to-dos, or reminders. Recurring meetings automatically take <strong>67%</strong>. And because it’s so easy for coworkers to book time in your schedule, <strong>54%</strong> is booked by someone else.</p><p>With the majority of our schedules booked by others, our perception of what’s essential is distorted, as our calendars become a hybrid of our priorities mixed with the priorities of many other people.</p><p>Back-to-back meetings without a break. Fragmented days that disrupt deep work. Frequent context-shifting. Working in the evening because you were in meetings all day — These are all examples of how other people have imposed <em>their </em>priorities on <em>your</em> schedule.</p><p>Solving this problem requires us to rethink how we put things into our calendars and our methods for moving them to accommodate changes in priorities.</p><h3>Adaptive Scheduling</h3><p>When we schedule something in our current calendars, what we’re doing is defining several static rules that govern when it will happen. It’s very specific; <strong>This event</strong> is happening on <strong>this day</strong>, at <strong>this time</strong>, in <strong>this location</strong>, with <strong>these people</strong>. But given the pace of change within the modern workplace, this specificity becomes a problem because our schedules quickly become filled with static entries.</p><p>Recurring meetings are particularly problematic because they reproduce, often indefinitely, without any consideration for our future priorities.</p><p>When something is scheduled, its relative importance is usually high. But as time passes, priorities often evolve — new things come up, undocumented things get remembered, demands for your time change to reflect the moment.</p><p>When this happens, we struggle to adapt our schedules to these changing priorities because it’s too complicated, if not impossible, to reschedule things on short notice. So we end up in back-to-back-to-back meetings, with a lack of focus time, working late, and increasingly stressed because we don’t have enough time to get everything done.</p><p>Adaptive Scheduling is a new technology that we’re developing at Mayday that approaches this problem differently.</p><p>Instead of setting a set of static rules for each calendar entry, you define a series of parameters. For instance, you can schedule a meeting for <strong>“this week”</strong> or <strong>“anytime after lunch.”</strong> You can book recurring events “<strong>once a month</strong>” or “<strong>three times a quarter.”</strong></p><p>Mayday will then schedule the event at a time that works best within the supplied parameters, while also considering your working hours, routines, and the software’s understanding of how you <em>want</em> to spend your time.</p><p>If you’ve invited other guests, Mayday will also consider <em>their</em> respective priorities, picking a time that achieves Schedule / Priority Fit for everyone involved. And should you need to reschedule a meeting, the software will select another time that fits within the original parameters instead of forcing you to renegotiate for another time that works for everyone.</p><p>—</p><p>Success at work, the strength of our relationships, and our health are tremendously affected by how we choose to spend our time every day. And we’ve completely lost our ability to manage it.</p><p>We’ve reached a point where the demands on our time have become increasingly demanding. And the more interconnected we’ve become, the more the needs from <em>other </em>people compete with our own individual goals and aspirations.</p><p>At Mayday, our mission is to coordinate the world’s time by reimagining the calendar as a helpful assistant. We’re building empathetic productivity software, so we can all achieve Schedule / Priority Fit.</p><p>Time is our most valuable asset, but it’s been too easily lost, stolen, and misspent for too long.</p><p>Our goal is to fix that.</p><p>Check out what we’re building and sign up for early access at <a href="http://mayday.am/">Mayday.am</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c84a09664596" width="1" height="1" alt=""><hr><p><a href="https://medium.com/maydaylabs/the-world-doesnt-need-another-calendar-c84a09664596">The World Doesn’t Need Another Calendar.</a> was originally published in <a href="https://medium.com/maydaylabs">Mayday</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talking about what I can’t talk about.]]></title>
            <link>https://medium.com/@jeremybell/talking-about-what-i-cant-talk-about-485fcda7ea7a?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/485fcda7ea7a</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 15:25:34 GMT</pubDate>
            <atom:updated>2017-10-26T16:04:07.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehh4kAQD8jus58vkdGbNCw.jpeg" /><figcaption>The Connected Lab Team (well, like half of us…)</figcaption></figure><p>I’ve been here for almost a year now, but I haven’t really spoken about what I’ve been working on at <a href="https://www.connectedlab.com/">Connected Lab</a>. And if you take a look at our site, I’m sure you’ll still have a bunch of questions.</p><p>We have a number of really exciting projects on the horizon, and I <strong>really really</strong> wish I could speak more openly about our clients and the projects we’re working on. But for a number of reasons, we can only speak openly after NDAs have been signed (and even then, it’s a bit problematic). That said, I’ll do my best to dance around the specifics so you’ll get a better idea of what we’re doing over here.</p><ul><li>We’re collaborating very closely with a major product company in Silicon Valley (whose apps are likely on your home screen) on an entirely new product. It’s the kind of career-defining product that we’ll all look back on and say “shit, can you believe we helped create that?”</li><li>We just secured a multi-year partnership with a large audio electronics company to help build their next generation of products (everything from in-home products to in-car). You likely have one of their products in your home already.</li><li>We’re in the early stages of a research &amp; design project with a large, well-known camera company. We’re helping them understand their customers better while envisioning new products.</li><li>We’re doing a number of voice-based projects for a variety of clients. We’re even working on our own voice product (which Amazon described as “absolutely phenomenal”).</li></ul><p>And those are just some of the projects we’re working on<em> right now</em>. We’ve also got opportunities to work on new AR/VR products, a huge multi-year automotive project, and an exciting opportunity with one of the world’s best tech companies.</p><p>But we can’t start any of these because we simply can’t hire fast enough.</p><p>We’re already over 100 people, and at the moment we need to hire at least another <strong>11 designers</strong> and <strong>20 engineers</strong>, not to mention Product Managers, a QA Manager, and a bunch of other roles.</p><p>So if any of this sounds interesting, give me a shout. Visit<strong> </strong><a href="http://connectedlab.com/"><strong>our website</strong></a>, <a href="https://connectedlab.workable.com/"><strong>apply for a job</strong></a>, and come work with us. And then we can <em>really</em> talk about what we’re doing over here.</p><p><em>Jeremy is VP of Design at </em><a href="https://www.connectedlab.com/"><em>Connected Lab</em></a><em>, and previously a Partner at Teehan+Lax. If you like written content like this, but a lot shorter (and honestly, usually just retweets at this point), you can</em><a href="https://twitter.com/jeremybell"><em> find him on Twitter.</em></a></p><blockquote>👋🏾 Get to know the people and ideas shaping the products we use every day. <a href="https://usejournal.typeform.com/to/YDVRgX?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_content=jeremy_bell&amp;utm_campaign=guest_post"><strong>Subscribe to Noteworthy</strong></a> — the product &amp; design newsletter written by the <a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_content=jeremy_bell&amp;utm_campaign=guest_post">Journal</a> team.</blockquote><figure><a href="https://usejournal.typeform.com/to/YDVRgX?utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_content=jeremy_bell&amp;utm_campaign=guest_post"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spegX3SQAdzTh74cW7qW8w.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=485fcda7ea7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Well, We Failed.]]></title>
            <link>https://medium.com/inside-wattage/well-we-failed-77e795e16ecf?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/77e795e16ecf</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Tue, 05 May 2015 16:32:15 GMT</pubDate>
            <atom:updated>2015-05-29T20:41:44.679Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0fEkCUZPlRh_4btBBqmUvg.png" /></figure><p><em>We set out with ambitious plans but after a year of development, we’ve run out of cash and are shutting down Wattage.</em></p><p>I hate to say it, but Wattage Inc. is no more. We were unable to secure the additional investment we needed, so we’ve decided to close up shop and call it a day. That said, we did manage to secure a deal that allows us to return our investors’ money. So while we didn’t exactly birth a unicorn, at least it wasn’t a total loss.</p><p>There are a number of reasons why we failed, and I felt there might be some value in sharing what we learned through this experience. I suppose the first thing we should talk about is our pitch deck.</p><h4>“Now That’s A Beautiful Pitch Deck”</h4><p>The one piece of consistent feedback we received throughout this entire process was how nice our pitch deck looked. We often joked that no matter what happened with Wattage, I could at least take a job building decks for others. Obviously its contents didn’t do much to help build a successful business, but I figured it might be worth sharing nonetheless. It didn’t exactly follow the <a href="http://www.forbes.com/sites/chancebarnett/2015/03/26/infographic-sec-democratizes-equity-crowdfunding-with-jobs-act-title-iv/">standard</a> pitch deck format, and it was also described as “nowhere near as crisp and focused as required.” But at least it looks nice, right? Sigh.</p><p>It went through upwards of 6o revisions I think, and you can <a href="https://drive.google.com/file/d/0B95cJ2uw4oQlSm5rSTEwU0NZLUk/view?usp=sharing">download the last version here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHc3dfvTjnbVtYMUiawoWg.png" /></figure><p>The vision for Wattage was a future where anyone could manipulate matter. Where we needn’t settle for the generic, mass-produced things that currently line store shelves. A future where we can easily upgrade our old devices instead of throwing them away. Or reprogramming them to do entirely new and useful things.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3clUHoZIU70%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3clUHoZIU70&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3clUHoZIU70%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee3cd9095c761387f7d7f1c4122eaf18/href">https://medium.com/media/ee3cd9095c761387f7d7f1c4122eaf18/href</a></iframe><p>We wanted to make it so creating and selling hardware was as easy as writing and publishing a blog post. You shouldn’t need to be an electrical engineer or an industrial designer to create electronic devices. Nor should you have to worry about supply chain or distribution if you wanted to sell them. We believed it was possible to eliminate all of that complexity, so the average person could easily create highly customized hardware without any electronics know-how, all within their browser.</p><p>Of course, things didn’t exactly play out that way. But why?</p><h4>An Absence Of Traction</h4><p>I suppose our failure can be summed up quite easily: An inability to show <a href="https://www.quora.com/How-do-you-define-traction-for-a-start-up">traction</a>. We were attempting to create an entirely new market for mass-customized electronics, which we originally viewed as something positive (as we felt we could create and own this new market). But from a fundraising standpoint, it was the opposite. Why would investors put large sums of money into a company going after an unproven market? (<em>Hint:</em> <em>they don’t.</em>)</p><p>Being a hardware company, we focused on building prototypes to validate that our vision was <em>technically</em> feasible. In retrospect, this was a mistake. Instead, we should have released something far more lightweight, and as quickly as possible. Our efforts should have been focused on validating interest in our product and generating traction. We <em>did</em> realize this, and we were moving to launch a beta as a means of validating interest. The problem is we realized too late, and ultimately didn’t want to launch a beta that we couldn’t afford to support.</p><h4>Not Enough Focus</h4><p>We had grand plans for the platform and we were only working on a small subset of features. But we should have been working on even fewer. We had decided to build the initial platform around just hardware creation. We wouldn’t offer the marketplace, or anyway to program devices, and customers would need to assemble their creations themselves. But that was still too broad a focus. Instead of trying to build a platform for hardware creation, we should have focused on selling a single but highly-customizable product. Doing so would have allowed us to prove that we could actually ship product to paying customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Zw0ApT0hQCjspRuNqVljw.png" /><figcaption>We eventually decided to focus just on the radio, but it was too late.</figcaption></figure><h4>Poorly Playing The VC Game</h4><p>While there are obviously a number of options for raising money, we chose the venture capital route. I knew this would be a difficult endeavour, but reading things like <a href="http://www.feld.com/archives/2011/07/venture-deals-be-smarter-than-your-lawyer-and-venture-capitalist.html">Venture Deals</a> or all of <a href="http://www.paulgraham.com/">Paul Graham’s essays</a> do little to actually prepare you for how challenging it really is.</p><p>Having previously raised $250,000 from friends &amp; family, we had set out to raise a $2M seed round. I spent the better part of 6 months meeting with VCs in San Francisco, Silicon Valley, New York, and Toronto. In the Valley, I was told we were raising too little. In Canada, we were raising too much. In retrospect, it looks like we attempted to raise too much, too soon. Instead of raising a large pre-launch seed round, we should have raised a smaller amount from angel investors. Raise a smaller amount, and release a smaller product. If we started generating traction, we could have then raised more.</p><p>To that end, I wish I would have taken better advantage of AngelList. There’s so much potential there. We created a profile and regularly updated it, but we never successfully used it as a fundraising platform.</p><h4>What About Crowdfunding?</h4><p>We got very close to launching a crowdfunding campaign, but ultimately decided against it because I felt it was premature for us. We didn’t have enough confidence in our product costs, so even if the campaign was successful, there was a good chance that we’d ultimately lose money on each sale. We’d always planned on crowdfunding, but I felt we needed to be further along before doing so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*smvkNTW81Z9orgXgAnSl4w.png" /></figure><h4>How Does This Scale?</h4><p>Our business model was about selling hardware. By reducing the complexity of creating hardware, our bet was that more people would create and buy. We would then wrap these creation tools in a marketplace, so creators could also sell their inventions to the masses.</p><p>In the earlier versions of our pitch deck, we focused a lot on empowerment. We were targeting software developers, as we believed we could offer them an entirely new outlet for their creative efforts. But this narrative wasn’t big enough. Investors want to hear a story about changing the world. Large ambitions, with a meaningful impact on the market, resulting in massive sales. We just didn’t tell a big enough story.</p><p>I also don’t think I properly emphasized the marketplace potential, as most investors got hung up on the number of potential <em>creators</em>. We looked at ourself as a diverse marketplace of mass-customized goods, but that potential (or at least as we articulate it) didn’t seem to resonate with investors.</p><p>We also heard concerns about the viability of scaling a bespoke hardware business. The manufacturing world is geared for mass-production, with profits coming from economies of scale. But we felt we could overcome this with standardized design &amp; manufacturing tools, in distributed factories, using modular electronics. We saw huge potential in the <a href="http://sparksheet.com/the-long-tail-of-things-qa-with-chris-anderson/">long tail of things</a>. But this was obviously unproven and we clearly didn’t do enough to reduce investor fear in our ability to pull this off.</p><h4>We Were Too Early</h4><p>1,600 people signup for our email newsletters, and each of them received a personal message from me. I gave them my email address and phone number, and invited them to chat if they had any questions. I heard from 100&#39;s of them, and many shared “the thing” they wanted to create. The problem is many of them simply weren’t feasible with the current technology. I suspect we could have eventually delivered on most of them, but not in the foreseeable future.</p><p>Furthermore, when I looked at the various prototypes we’d created, the quality simply wasn’t there yet. We were heavily using laser cutting as our means of fabrication, and while it allowed us to produce something close to our vision, it wasn’t good enough. What we really needed was a hybrid of laser cutting and 3D printing, but unfortuately 3D printing is still far too slow and expensive to be realistic. I have no doubts that 3D printing will play a huge role in the future of manufacturing, but it simply isn’t there yet.</p><h4>So That’s It.</h4><p>It’s been a fun ride to say the least. We’re still deciding what to do with everything we produced this past year. There’s a high likelihood Wattage will be reborn in another form sometime in the future, but we just don’t know yet.</p><p>I wanted to say thank you to those that supported us during this adventure:</p><p><a href="http://www.hotpopfactory.com/"><strong>Hot Pop</strong></a> for helping us design &amp; create all of our physical prototypes<br><a href="http://www.cossette.com/en/lab"><strong>Cossette Lab</strong></a> for the office space, staff, and bagel Monday’s<br><a href="http://christanner.ca/"><strong>Chris Tanner</strong></a> for the design help<br><a href="http://www.samdallyn.co.uk/"><strong>Sam Dallyn</strong></a> for designing our logo<br><a href="http://jonasnaimark.com/"><strong>Jonas Naimark</strong></a> for creating <a href="https://drive.google.com/file/d/0B95cJ2uw4oQleEpPejVNbzJsVEE/view?usp=sharing">this</a> awesome animation<br><a href="http://heistmade.com/"><strong>Heist</strong></a> for the design help<br><a href="http://www.makeworks.com/"><strong>MakeWorks</strong></a> &amp; <a href="http://www.teehanlax.com/"><strong>Teehan+Lax</strong></a> for the office space in the early days</p><p>But the most thanks goes to our supporting wives, who consistently provided encouragement through all of the up’s &amp; down’s. I wish this had turned out better than it did, but at least we’ll have actual paying jobs again! <em>&lt;cough&gt;inquires welcome&lt;/cough&gt;</em></p><p>So that’s it for now. If you’d like to reach us, you can find us on Twitter:</p><p><strong>Andy MacDonald</strong> (<a href="https://twitter.com/andymacd">@andymacd</a>)<br><strong>Brett Hagman</strong> (<a href="https://twitter.com/BrettHagman">@BrettHagman</a>)<br><strong>Peter Nitsch</strong> (@<a href="https://twitter.com/peter_nitsch">peter_nitsch</a>)<br><strong>Jeremy Bell</strong> (@<a href="https://twitter.com/jeremybell">jeremybell</a>)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-U4Pvodwm0U%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-U4Pvodwm0U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-U4Pvodwm0U%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7c5394b8347cc48874a7da03d978eae8/href">https://medium.com/media/7c5394b8347cc48874a7da03d978eae8/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77e795e16ecf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-wattage/well-we-failed-77e795e16ecf">Well, We Failed.</a> was originally published in <a href="https://medium.com/inside-wattage">Inside Wattage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wattage?]]></title>
            <link>https://medium.com/inside-wattage/wattage-85e9d5fc2769?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/85e9d5fc2769</guid>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Thu, 05 Feb 2015 16:50:43 GMT</pubDate>
            <atom:updated>2015-02-05T17:15:00.338Z</atom:updated>
            <content:encoded><![CDATA[<p><em>While we’re not quite ready to reveal everything, we are going to start sharing a lot more. Below is a copy of the first update we sent to our mailing list. If you’re interested in receiving these updates, please </em><a href="http://wattage.io/"><em>subscribe here.</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQqpYurO74c-mjjVr2tPyA.png" /></figure><p>Wattage is a few things. At its simplest, it’s an online store where people can buy electronic devices. But the interesting thing is that all those devices will be created using our online tools. The enclosures are locally made using laser cutters and 3D printers, and inside is a family of modular electronic components.</p><blockquote>What we’re trying to do is lower the barrier of entry so people can express themselves through hardware, regardless of their technical sophistication.</blockquote><p>We imagine people creating all sorts of interesting things like podcast-streaming radios, or tactile games. Home automation gadgets, and music gizmos.</p><p>But whatever they might create, they won’t need to be an electrical engineer or an industrial designer. They just need a browser and their imagination.</p><p>Think of us along the lines of NikeiD for gadgets. You create or customize your device online, we’ll then fabricate it and ship it to you.</p><p>I’ll cover various platforms features in future updates, but today I’m going to focus on the Product Builder. And to do that, I recorded a little video for your viewing pleasure.</p><p>This is obviously an early alpha, but it should give you a sense of how it works. You virtually create your device with simple drag &amp; drop, and then we’ll ship you the physical thing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FjVI7oYH11I8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DjVI7oYH11I8&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FjVI7oYH11I8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/37274a32daf3d414eda333dea9ddb061/href">https://medium.com/media/37274a32daf3d414eda333dea9ddb061/href</a></iframe><h3>Ok, sounds great. But why?</h3><p>Manufacturing is one of the biggest industries in the world. Since the first industrial revolution, the power to make things at scale has belonged to those who own the means of production. Big companies, with big factories, building mass-market goods.</p><p>But the same was true for mass media in the 20th century, and we’ve seen what the Internet has done to that.</p><p>We believe hardware is next.</p><p>Soon, we’ll all have the power to create and distribute hardware using nothing more than a browser.</p><p>That’s ultimately what we’re trying to do with Wattage. And we hope you’ll help us make it a reality.</p><p>We really want to know what you think, and I’ll happily answer any questions you have. Feel free to <a href="/service/mailto:jeremy@wattage.io?subject=Question%20about%20Wattage">email me</a>, or message me on <a href="http://www.twitter.com/jeremybell">Twitter</a>.</p><p>We’ll be releasing more info as we get closer to launch. If you’re interested in receiving these updates, please <a href="http://wattage.io/">subscribe on our website</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85e9d5fc2769" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inside-wattage/wattage-85e9d5fc2769">Wattage?</a> was originally published in <a href="https://medium.com/inside-wattage">Inside Wattage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello Senior Designer. We’d like you to come work with us at Wattage.]]></title>
            <link>https://medium.com/@jeremybell/hello-senior-designer-wed-like-you-to-come-work-with-us-at-wattage-6d46ee570d93?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d46ee570d93</guid>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Wed, 27 Aug 2014 13:44:44 GMT</pubDate>
            <atom:updated>2014-09-10T15:51:39.078Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re making it easy for anyone to build hardware, and we need your help.</p><p>I suspect you probably don’t know much about <a href="http://www.wattage.io/">Wattage</a>, which is understandable as we haven’t shared much yet. We hope to share more soon, and we’ve included a short video below, but until then I can say that we’re a small startup in Toronto that wants to make it easy for <em>anyone</em> to create beautifully designed electronics (much like the <a href="https://www.flickr.com/photos/dasprogramm/6018144247/">Braun RT20</a> above). You shouldn’t need to understand the basics of electronics, or how to solder, or how to use CAD software. All you need is a browser and your imagination.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F105671694&amp;url=http%3A%2F%2Fvimeo.com%2F105671694&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F488540357_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/7e8db85f778c64d4e5316e22d6671b94/href">https://medium.com/media/7e8db85f778c64d4e5316e22d6671b94/href</a></iframe><p>What we’re doing is a bit complex and has a number of moving pieces. Visual design, industrial design, 3D, custom electronics, parametrically created enclosures, on-demand fabrication. Sounds interesting, no?</p><p>We have a small but amazing team that is tackling most these problems, but we still have a few gaps to fill. And that’s where you come in. We need an amazing visual designer to help us design our platform. And flush out our identity. And weigh in on the industrial design. And pitch in on the million other design related things we have to do.</p><h4>What We’re Looking For</h4><ul><li>An amazing portfolio.</li><li>Experience designing complex interactive systems &amp; user flows.</li><li>Experience launching digital products across desktop and mobile platforms.</li><li>Strong concept development and graphic design ability. This mean colour theory, typography, and composition. The works.</li><li>An immense attention to detail.</li><li>A desire to experiment and a willingness to throw away work and start over.</li><li>Nimbleness.</li><li>Ability to self-manage without much oversight.</li><li>Excellent understanding of HTML &amp; CSS. If you can code, that’s even better.</li><li>An appreciation for motion and how it affects the user experience.</li><li>Experience with identity and package design is also a plus.</li><li>The position is in Toronto, so you’ve gotta be in the 416.</li></ul><h4>Get In Touch</h4><p>Does that sound like you? Are you interested in helping create something entirely new? If so, we’d love to chat. Please send us a link to your portfolio <a href="/service/mailto:work@wattage.io">here</a>.</p><p><em>Photo source: </em><a href="https://www.flickr.com/photos/dasprogramm/6018144247/"><em>das programm.</em></a><em> License: All Rights Reserved.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d46ee570d93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android over iOS]]></title>
            <link>https://medium.com/i-m-h-o/android-over-ios-d4418bd564fc?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4418bd564fc</guid>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Thu, 01 Aug 2013 02:21:33 GMT</pubDate>
            <atom:updated>2013-08-01T02:23:51.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jvx99aj4KcNuSHqN.jpeg" /><figcaption>digitaltrends</figcaption></figure><h4>I’m seeing a wave of people move from iOS to Android, and I’m curious to find out why. </h4><p>I’ve noticed that a number of people I know have recently upgraded from an old iPhone to a new Android device. Usually moving from an iPhone 3Gs or iPhone 4, to a Samsung Galaxy S4, HTC One or Nexus 4.</p><p>I’ve been incredibly curious to know why they made the switch and what they think of their new Android device… So I decided to check it out myself. I just switched from an iPhone 5 (running iOS7 b4) and will be using a Nexus 4 for the next few months.</p><p>I’m very familiar with Android and I used a Galaxy Nexus for about a month when it was originally released. This Nexus 4 is much better than that Galaxy, but overall I’m still struggling to understand why someone would buy an Android over an iPhone.</p><p>On the surface, the platforms are very similar now. Especially since iOS7 was announced. You might not like the icon styling or overall aesthetic, but there’s little doubt that iOS7 has borrowed a number of features from Android.</p><p>Hardware-wise, the features and specs are essentially at parity. You can debate the differences in screen sizes—and yes, the larger screens <em>look</em> more appealing—but I personally can’t stand the size of the Nexus 4. It’s too big and I actually find it fatiguing to use with a single hand. I find the width of the iPhone to be perfect.</p><p>From an OS standpoint, the platforms are also very similar… At least from a stock-Android standpoint. I quite like the Nexus version of Android—and am impressed how quickly it has been improved—but overall I still find it clunky.</p><p>Perhaps “clunky” isn’t the best description, but I don’t know how else to describe it. Things look like they should work well, but I continue to find something <em>off</em> about them.</p><p>The way you copy and paste is horrible on Android. The gmail app should be good, but it’s not quite there. Setting up and maintaining the home screens is a pain in the ass. And I find most apps to be a bit rough around the edges… Just not as polished as their iOS counterpart.</p><p>I do like that you can customize Android <em>much</em> more than iOS, tho I’m not sure its actually worth the tradeoff. I’ve changed the launcher and the icons and have installed widgets, but I’ve found them all to be flaky. They stall and stutter. Coincidentally, today I overheard someone complaining that Android 4.3 broke their launcher and things weren’t working correctly.</p><p>So, really, is this customization worth it? I’m not finding nearly enough value to justify it.</p><p>Yes, there are things that Android does better.</p><p>The keyboard is nice, tho I’m not sure I actually type any faster on it. I also tried the Swype keyboard, but I found myself fighting it more than enjoying it. Again, perhaps I just need to get used to it.</p><p>Yes, I like that you can install apps that can augment core OS functionality (like the I’m Sleeping app that brings Do Not Disturb functionality to the OS). You just can’t do this on iOS.</p><p>Yes, I like the <em>idea</em> of widgets, but I don’t actually find I use them much nor am I really finding that much value in them.</p><p>Yes, notifications are better (tho, I think iOS7 has addressed this).</p><p>Yes, I like that you can quickly disable WiFi or adjust the screen brightness (but iOS7 has addressed this as well).</p><p>I <em>adore</em> the idea of Google Now, but I haven’t found much use for it yet (and it’s technically available for iOS, but not nearly as integrated or convenient).</p><p>I love that Google services are so deeply integrated (email and calendar in particular because I use Google Apps for my personal and work email), but most of that is also doable in iOS now.</p><p>So, to all my Android friends. Why? What was it that made you decide to get your Android over an iPhone? Was it the screen size? The degree of control over the OS (and are you really exploiting it)? The price? Do you just hate Apple? Did you want to try something different?</p><p>I’m honestly curious.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4418bd564fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/android-over-ios-d4418bd564fc">Android over iOS</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing With Code]]></title>
            <link>https://medium.com/@jeremybell/designing-with-code-578fabbf42ba?source=rss-debdf0d2b8f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/578fabbf42ba</guid>
            <dc:creator><![CDATA[Jeremy Bell]]></dc:creator>
            <pubDate>Tue, 30 Oct 2012 18:31:44 GMT</pubDate>
            <atom:updated>2014-03-29T18:57:27.083Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*IsvMY_3_thwwOOPV.gif" /><figcaption>Tamar Levine</figcaption></figure><h4>With an increasingly complex array of platforms and screen resolutions, it’s time to embrace the creative capabilities of HTML5 + CSS3 and make development part of the design process.</h4><p>While I’ve spent most of my days in the creative department, I actually started my career as a developer. I was 16, and having discovered the WYSIWYG editor in Netscape Navigator Gold, I had taught myself the basics of HTML. I was inexperienced and couldn’t build much, but I did manage to make something that landed me a job building websites. I enjoyed those days working with code, but at night I found myself playing with Photoshop. Design seemed to come more naturally and I eventually moved into the creative department as a Graphic Designer.</p><p>That transition was a very binary move. If I was to be a designer, I couldn’t be a developer. There was never an option to do both. Instead, I’d spend hours designing static pages in Photoshop that would simply be handed to the developers for reproduction in HTML. There was rarely an opportunity to collaborate throughout the process. Hell, we barely spoke. Sometimes we weren’t even in the same timezone, let alone the same room.</p><p>That was 16 years ago, and not much has changed.</p><p>Throughout my entire career, every company I’ve worked at has separated designers and developers into separate departments, each focused exclusively on their discipline. And while this practice was understandable when HTML was <a href="http://www.textfiles.com/underconstruction/">unsophisticated</a> and we were building static websites for 640×480, things have obviously changed. HTML5 and CSS3 displayed across a spectrum of resolutions, running on desktops and laptops and tablets and smartphones. Technology is continuously reshaping the canvas on which we design, and yet these two disciplines continue to be treated as disparate.</p><p>Methodologies like <a href="http://en.wikipedia.org/wiki/Agile_software_development">Agile</a> and <a href="http://uxdesign.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/">Lean</a>, paired with tools like <a href="http://www.pivotaltracker.com/">Pivotal</a> and <a href="http://basecamp.com/">Basecamp</a> have certainly helped close the gap between the disciplines. We’ve embraced each to varying degrees at Teehan+Lax, and last year we also reorganized the company into cross-functional teams, completely eliminating our creative and development departments. We greatly improved collaboration by making dramatic changes to our process and structure, but I don’t believe we’ve gone far enough. Our designers and developers may now be physically sitting closer together, but there is still a significant chasm between the two.</p><h4>Photoshop</h4><p>The problem with Photoshop is that what’s being created is actually a fiction. It somewhat resembles what the final product might look like, but it’s not real. Layout and typography decisions are made that often don’t translate accurately to HTML. We spend hours designing for a medium that’s interactive and responsive, but we start by producing mockups that are static and inflexible. If great design is not only aesthetics but also <a href="http://quotesondesign.com/steve-jobs/">how it works</a>, then it’s time to make development part of the creative process.</p><p>Of course Photoshop still has a role, but it’s now possible to move to working code much sooner. Instead of iterating through creative concepts in Photoshop, designers should increasingly be exploring their ideas in code. They need to be intimate with the technology they’re designing for, and they need to be comfortable working within it.</p><p>Which all sounds great, but from my experience, most designers can’t code.</p><p>Yes, some are indeed quite capable and others have at least a basic understanding of HTML &amp; CSS, but I doubt many designers would describe themselves as being adept. We have an incredibly talented group of designers at Teehan+Lax, but if we’re going to have them manipulating code, we need to get them proficient with the technology, and we need to rethink our creative process.</p><h4>Education</h4><p>Starting today, all of our designers will begin a series of ongoing training courses for HTML &amp; CSS development.</p><p>We evaluated a number of solutions (<a href="http://www.lynda.com/">Lynda</a>, <a href="http://www.codecademy.com/">Codecademy</a>, etc.) but ultimately settled on <a href="http://teamtreehouse.com/">Treehouse</a>. With their group options, breadth of content and code challenges, it was the perfect fit. We’ll start with the basics and focus the presentation layer, with the goal of getting each designer as comfortable withbox-shadow as they are with <em>Save For Web</em>. Of course, I expect the vast majority of education will happen on-the-job, but this will at least ensure we’re starting on common ground.</p><p>Development also requires a proper toolset, so each designer will be equipped with the following:</p><p>A local development environment. We’ll keep it simple and install <a href="http://www.mamp.info/en/mamp-pro/index.html">MAMP PRO</a> on each of their machines.</p><p>Access to our Git repositories (and a lesson on <a href="http://git-scm.com/">Git</a> itself). I’m not expecting many will be clamouring for the <a href="http://en.wikipedia.org/wiki/Command-line_interface">CLI</a>, so everyone will get a copy of <a href="http://www.git-tower.com/">Tower</a>instead.</p><p>An IDE of their choice (but I’m going to go out on a limb and say that most will start with <a href="http://panic.com/coda/">Coda</a>).</p><p>A copy of <a href="http://csshat.com/">CSS Hat</a> to better utilize Photoshop in this new environment.</p><h4>Process</h4><p>Our current process is somewhat of a cocktail of tools and methods. Most projects begin a little like waterfall and end a little like Agile. But we always start by creating static mockups. Over the years we’ve made an effort to get to working code sooner, and today we’re going to further streamline this by having our designers &amp; developers collaborating in a shared codebase.</p><p>On day one, I’m not anticipating a dramatic change to our process. We will still create high-fidelity mockups in Photoshop and our developers will still translate those mockups into HTML. But instead of providing visual feedback in the final stages of development, our designers will modify the actual CSS themselves. They will be responsible for tweaking and polishing the final product until they feel it’s perfect in Chrome. From there, the developers will still be responsible for ensuring cross-browser consistency.</p><p>Looking into the future, the gap between the groups will continue to blur. I suspect we’ll often still need to create a set of preliminary mockups, but our teams will be increasingly working through design challenges in the code itself. This will be a highly collaborative process, with the developers being primarily responsible for JavaScript and the underlying markup for content and structure, while the designers will be increasingly responsible for the presentation markup.</p><p>We believe great design fuses form &amp; function to create things that people actually want to use, and Teehan+Lax is committed to making this philosophy a fundamental aspect of our process. It’s not going to be an easy transition, but I’m incredibly excited to see where this path takes us.</p><p>—<br><em>This post originally appeared on the</em><a href="http://www.teehanlax.com/blog/10-years-of-teehan-lax/"><em> </em></a><a href="http://www.teehanlax.com/blog/"><em>Teehan+Lax blog</em></a><em>. Learn more about us </em><a href="http://www.teehanlax.com/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=578fabbf42ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>