<?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 Jackrabbit Mobile on Medium]]></title>
        <description><![CDATA[Stories by Jackrabbit Mobile on Medium]]></description>
        <link>https://medium.com/@teamjackrabbit?source=rss-19f956058d96------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wIqPoAUTTNDoIVSk.jpg</url>
            <title>Stories by Jackrabbit Mobile on Medium</title>
            <link>https://medium.com/@teamjackrabbit?source=rss-19f956058d96------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:15:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@teamjackrabbit/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[9 Reasons to Build Your Career at Jackrabbit Mobile]]></title>
            <link>https://medium.com/@teamjackrabbit/9-reasons-to-build-your-career-at-jackrabbit-mobile-9dc271934d06?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dc271934d06</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 23:14:56 GMT</pubDate>
            <atom:updated>2017-10-23T23:14:56.965Z</atom:updated>
            <content:encoded><![CDATA[<h3>1. Flat Company Culture &amp; Awesome Teammates</h3><p>We really value team culture. And no, that doesn’t mean a fancy office. It means working with people who are experts in mobile technology, have a wide spanning range of abilities (from design to research to coding), and passionate about what they’re working on and eager to help one another out. Every project team is cross-disciplinary and is composed of researchers, designers, engineers, and mobile strategists — so expect to be immediately exposed a diverse team with different skill sets.</p><p><em>This article originally published at </em><a href="http://www.jackrabbitmobile.com/lean-startup/9-reasons-to-build-your-career-at-jackrabbit-mobile/"><em>www.jackrabbitmobile.com</em></a></p><h3>2. Work on the Newest Technologies</h3><p>As a new employee at Jackrabbit Mobile you, along with any other new hires, will be added to our Jackrabbit Labs team. The goal of Jackrabbit Labs is to experiment with emerging technologies and find ways that they may help solve the issues. The experiments you work on will largely be driven by the interests of you and your peers — this is a chance for you to start contributing right away and start to gel with your teammates. Recently we’ve been hacking together experiments using drones, beacons, and virtual reality.</p><p><a href="https://www.youtube.com/watch?v=FXrrBEhcEbc">Learn more about some of our latest Labs projects here</a></p><h3>3. Work Where and When YOU are Most Productive</h3><p>We don’t have a dress code or standard working hours. In fact, on any given day of the week only about 50% of the team may be in our downtown Austin office. This is because we value productivity, and realize that each person has a different setting or time where they’re more productive. Anthony is a morning person. Dan isn’t. And that’s okay! We require a certain amount of “overlap hours” that everyone is working to encourage communication and team problem solving, but otherwise we have a results only work environment. We’re more concerned about delivering high quality products than having everyone in the office from 9–5.</p><p><a href="https://medium.com/u/5e361eee15b1">Matt Wanninger</a> would rather not waste his time fighting traffic, so he comes to the office around 10. <a href="https://medium.com/u/1abbb1ed3a4e">David Olesch</a> won a free flight to London, so he worked from there for a week last year. One of our Project Managers wanted to experience life in California for a few months, so he found a sublease and headed off to San Francisco.</p><h3>4. Ownership Over Projects</h3><p>We’re a small team, so you’re getting hired to work on client projects. You’ll have a mentor to help you out in the beginning and learn our process, but within the first month of working at Jackrabbit you’ll find yourself as a key asset in a client project, and the sole voice within your area of specialty (user experience, engineering, operations, or strategy).</p><h3>5. Unlimited Vacation Days</h3><p>Counting vacation days isn’t something we really see the need for. Since we hire high performing, responsible individuals we leave it up to them to make the decision when they need to take vacation, whether that’s for a day, a week, or more. Decisions as to when to take vacation are often team-driven as opposed to decided by any manager.</p><h3>6. Ongoing Learning</h3><p>We want to make sure our employees are always learning new things and not stagnating in their careers. One way we do this is through Jackrabbit Labs, and SXSW, but another is by encouraging people to attend conferences and workshops to further their skill set. We recently sponsored Sam to go to Atlanta and do an intensive 1 week Android development workshop. We also sponsored all of our designers and project managers to go to an intensive Lean UX workshop by Jeff Gothelf (<a href="http://www.jeffgothelf.com/blog/lean-ux-book/#sthash.J29RDFr5.dpbs">he literally wrote the book on lean user experience design</a>).</p><h3>7. Live in Austin</h3><p>The best city in the USA y’all. Incredible food culture, live music every day, and way more affordable that New York or San Francisco. It’s the place to be.</p><h3>8. Attend SXSW on the Company Dime</h3><p>Every year the team takes off normal work and spends the entirety of SXSW Interactive around downtown Austin networking, going to workshops, and learning from some of technologies’ modern day luminaries. Last year we saw talks by Jimmy Wales and Barack Obama, went to design thinking workshops facilitated by the Stanford D School, experimented the HTC Vive pre-release, partied on Rainey Street, and saw awesome bands like Santigold.</p><h3>9. Make an Impact in the Community</h3><p>Everyone on the team is heavily involved in being part of the Austin community and giving back to city we know and love. We are the organizers of <a href="http://www.meetup.com/Austin-iPhone-Developer-Group/">Austin’s iPhone Developer Meetup</a> as well as the city’s Android meet up. We also help mentor engineering students at University of Texas and volunteer our time at Austin Pets Alive.</p><p>We’re involved in <a href="https://www.youtube.com/watch?v=40SA0_qGyhk">TEDx Youth Austin</a>, 3 Day Startup, and teach <a href="https://www.youtube.com/watch?v=_rJWEhPlqbk">Lunch &amp; Learn Workshops at Capital Factory</a>.</p><p>Lately we’ve also partnered with the Human Rights Foundation and are working on an app for their world renowned human right conference, the Oslo Freedom Forum.</p><p>“It’s like Comic Con except the heroes are real” -Jimmy Wales</p><h4>Interested in working with us?</h4><p><a href="http://www.jackrabbitmobile.com/jobs">Work with us</a></p><p><em>Originally published at </em><a href="http://www.jackrabbitmobile.com/lean-startup/9-reasons-to-build-your-career-at-jackrabbit-mobile/"><em>www.jackrabbitmobile.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dc271934d06" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Jackrabbit Playbook!]]></title>
            <link>https://medium.com/@teamjackrabbit/new-jackrabbit-playbook-c2845580fa8a?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2845580fa8a</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Thu, 18 Aug 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-10-23T23:23:31.031Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*86WFgBA8eJ9JpT06HZo6yw.png" /></figure><p>We’re very excited to share our Jackrabbit Playbook!</p><p>At <a href="https://medium.com/u/19f956058d96">Jackrabbit Mobile</a>, we help our amazing clients build impactful products. We get to work with cutting edge new technologies and design effective interfaces.</p><p>Our team has processes and best practices to reliably produce great results for each step from start to finish. We believe it’s valuable to share those best practices with our colleagues and our clients, so that we can best work together. That’s where this Playbook comes in.</p><p>We encourage you to read through and understand how we work, and the value and expertise we can bring to your product to make it real.</p><h3>Downloadable PDF:</h3><h4><a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></h4><h3>Read it on Medium:</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf</a></h4><p>As we work together, we’ll refer to many of these sections in the Playbook. Don’t hesitate to <a href="http://www.jackrabbitmobile.com/contact/">contact us</a> if you have any questions!</p><p><em>Originally published at </em><a href="http://www.jackrabbitmobile.com/app-development/new-jackrabbit-playbook/"><em>www.jackrabbitmobile.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2845580fa8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coolest Companies Finalist — Vote for us!]]></title>
            <link>https://medium.com/@teamjackrabbit/coolest-companies-finalist-vote-for-us-91128d3fe6b2?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/91128d3fe6b2</guid>
            <category><![CDATA[austin]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Tue, 16 Aug 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-10-23T23:11:55.558Z</atom:updated>
            <content:encoded><![CDATA[<h4>Thanks to <a href="http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/">Austin Inno</a> for noticing that we’re one of the <a href="http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/">Coolest Companies in Austin</a>!</h4><figure><a href="http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/"><img alt="" src="https://cdn-images-1.medium.com/max/321/1*jlHOt1zIRgQ2--Dwjwjozw.png" /></a></figure><h4>Vote for us here: <a href="http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/">http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/</a></h4><h3>Heck yea we are! …Why?</h3><h3>Well, we have Team Love.</h3><p>No, really, it’s a thing. Every Monday at team meeting everyone has an opportunity to recognize and appreciate another Rabbit from the past week. Sometimes it’s funny and sometimes it’s a tear-jerker, but it’s always our favorite way to start the week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7EMtON69gWEwm08xMgl2ww.png" /></figure><h3>We build awesome tech with awesome people!</h3><p>We love what we do and who we work with. We’re incredibly lucky that we get to work with and help some of the coolest and most impactful projects going. From healthcare tech to dating apps, and everything in-between. We developed <a href="https://play.google.com/store/apps/details?id=com.AlertSense.AlertSense&amp;hl=en">AlertSense</a>, a mass notification system for emergency responders. We love building the <a href="https://itunes.apple.com/us/app/atx-startup-crawl/id566309218?mt=8">Austin Startup Crawl apps</a>. We <a href="http://www.jackrabbitmobile.com/portfolio/society-wine-educators/">teach people about wine</a>. And that’s just a few of our recent projects.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F40SA0_qGyhk%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D40SA0_qGyhk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F40SA0_qGyhk%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/ade69a83ece1cd2e73f0bb890b0d61fd/href">https://medium.com/media/ade69a83ece1cd2e73f0bb890b0d61fd/href</a></iframe><h3>We have a beautifully hip new office</h3><p>We just renovated an awesome space in East Austin, our <a href="https://medium.com/@anthonyblatner/a-beautiful-new-rabbit-den-4b3f807a0ccd">Beautiful New Rabbit Den</a>. It’s been a project of sledgehammers and creativity as we renovated an old bike shop into a beautifully inspiring space. We uninstalled the sales shelves and cash register, but of course we kept the gnarly bike racks, eclectic art murals, and turf grass. We squeezed in a couple phone booths, wired up Wi-Fi and installed a dozen more power outlets. We maintained the creative East Austin vibe with a hipster bike shop twist, and infused it with some startup spirit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eeysa2q--JjRFb8oJL-asw.png" /></figure><p>We play Pokemon Go together. <a href="https://austinstartups.com/ios-bubble-animation-tutorial-4d3a4d0fe20c">We love bubbles</a>. And there’s enough LaCroix in the fridge to survive a Texas summer.</p><p>…<a href="http://www.jackrabbitmobile.com/lean-startup/9-reasons-to-build-your-career-at-jackrabbit-mobile/">And here’s a few more reasons why</a> =)</p><h4>Vote for us here! <a href="http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/">http://austininno.streetwise.co/our-events/austin-fest/coolest-companies/</a></h4><p><em>Originally published at </em><a href="http://www.jackrabbitmobile.com/lean-startup/coolest-companies-finalist-vote-for-us/"><em>www.jackrabbitmobile.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91128d3fe6b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beautiful New Rabbit Den ]]></title>
            <link>https://medium.com/@teamjackrabbit/a-beautiful-new-rabbit-den-bfd214111bc2?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd214111bc2</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Wed, 03 Aug 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-10-23T23:16:23.077Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/u/19f956058d96">Jackrabbit Mobile</a>’s brand new office!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzG95to0Ooz68npU8wB6aA.jpeg" /><figcaption><a href="https://medium.com/u/19f956058d96">Jackrabbit Mobile</a> HQ on East 7th</figcaption></figure><p>This week <a href="http://www.jackrabbitmobile.com/">Jackrabbit Mobile</a> moved into our brand new office on East 7th St. in downtown Austin and we are incredibly excited!</p><p>It’s been a project of sledgehammers and creativity as we renovated an old bike shop into a beautifully inspiring space. We uninstalled the sales shelves and cash register, but of course we kept the <strong>gnarly bike racks</strong>, <strong>eclectic art murals</strong>, and <strong>turf grass</strong>. We squeezed in a couple phone booths, wired up Wi-Fi and installed a dozen more power outlets⚡.️</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrkRwxJF3BcKEJp1EVYBAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fTvSVPbT6-CQZB_gCznriw.jpeg" /><figcaption>Hard hat zone 👷</figcaption></figure><p>Our goals for the space was to make it fun, open, and effective. We needed a larger space for our growing team, more conference and phone rooms for all of our meetings, and lots of natural light, for our sanity ☀️</p><p>The mastermind (and General Contractor Extraordinaire 🔨) of this project was <a href="https://medium.com/u/239e17ed3d91">JoJo Marion</a>, Partner and Chief Creative Officer at Jackrabbit. He’s earned every bit of that title. Huge thanks to the whole team and all the friends and family that helped out. During demolition we saw <a href="https://medium.com/u/44eeec222701">Jonathan Rosenberg</a>, Partner and CEO, knock down a wall with a sledgehammer, and I got some solid practice with the power tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NYiVX0GnU-qbk4Zyg-8k6w.jpeg" /></figure><p>The finished space turned out even better than expected. We maintained the creative East Austin vibe with a hipster bike shop twist, and infused it with some startup spirit.</p><p>Typically there’s a couple people who wander in each day looking for the bike shop. Instead, we show them some <a href="http://www.jackrabbitmobile.com/portfolio/">awesome mobile apps</a> and give them a cup of coffee for visiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6OwftLdDPxRGNDaUyn-AlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qFwdmG82oZeV89ARz5JpRQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*99dRqXJWlwWlUAoCIMXOxw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Ralt2Q-ynsHk8XuInCxlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*QdpyynjBNFPA2WnAbF8dRA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eE5UtPhjQIZIlLs69g8whw.jpeg" /><figcaption>Pictures of the new <a href="https://medium.com/u/19f956058d96">Jackrabbit Mobile</a> office!</figcaption></figure><p>It’s fun to think about our journey to this point. Our first start years ago was in an unfinished one-room office on San Antonio St. We then moved to <a href="https://medium.com/u/2a4ca6f3d8d9">Capital Factory </a>in the heart of downtown Austin, where we enjoyed the view, the snacks, and the incredible community. Then we spent a short time on West 6th (and ate every single item at Whole Foods), and are now settled on the East Side. We’ve covered the Austin geography pretty well.</p><p>Thanks to the Jackrabbit Team for all the extra hands, trucks, and sweat with the move, especially Jesse, <a href="https://medium.com/u/5147dbc266f6">Caroline</a>, <a href="https://medium.com/u/5f84d484d232">Gibrán</a>, and John!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOJVetai4uheg3g9svb5IA.jpeg" /><figcaption>Rabbits in the new Den!</figcaption></figure><p>We have a few more exciting plans up our sleeve for this new space, but we’re not giving away any secrets yet — you’ll have to wait and see!</p><p><a href="http://www.jackrabbitmobile.com/"><em>Jackrabbit Mobile</em></a><em> is a mobile-first creative agency in downtown Austin. We build awesome tech with awesome people. Say hi, </em><a href="/service/mailto:hello@jackrabbitmobile.com"><em>hello@jackrabbitmobile.com</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd214111bc2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Drones , Apple Watches⌚️, and Culture ‍‍‍]]></title>
            <link>https://medium.com/@teamjackrabbit/drones-apple-watches-%EF%B8%8F-and-culture-b6133f5aea1e?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6133f5aea1e</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Thu, 28 Jul 2016 07:00:00 GMT</pubDate>
            <atom:updated>2017-10-23T23:18:51.331Z</atom:updated>
            <content:encoded><![CDATA[<h4><a href="https://medium.com/u/19f956058d96">Jackrabbit Mobile</a>, <a href="https://medium.com/u/d6b3cc6153a3">NewCo</a> Austin 2016</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*alHw9GxtwIDU0DIikxpoEw.png" /></figure><p>Thanks to NewCo for inviting us to present at the event and creating the space to share some fun and some very important parts of what it is we do here at <a href="http://www.jackrabbitmobile.com/">Jackrabbit Mobile</a>(more than just apps).</p><p>Also thanks to the weather for clearing up before our time slot. We had a packed house at our office on West 6th (and tomorrow we move into our awesome new office on East 7th!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yGE2ijeLRgO0ixHDL59odg.jpeg" /></figure><h3>Culture</h3><p><a href="https://medium.com/u/44eeec222701">Jonathan Rosenberg </a>shared about our Culture &amp; Strategy, specifically about our employee Growth Plans which we are really excited for (and that he and Kyle Zamcheck put a lot of work into!).</p><p>He shared that, to build a great company, you must build a great team. And that effective leadership isn’t always one person with all the responsibility and all the power. More effective is collaborative leadership, where individuals are enabled to take initiative and lead in their own way.</p><p>As a startup, things get done when people step up, champion an idea, and drive an initiative to success. People also do their best work when they have the opportunity to work on things they’re most passionate about.</p><p>Jon explained that in the beginning, everyone did everything, and as we grew, there were growing pains where it wasn’t always clear to everyone where or how they should contribute, or what were the steps to their personal growth.</p><p>As a company, it’s important that we enable those steps. These Growth Plans are a tool for facilitating that path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ehJUJC9TBDxtD5HVRfLteg.jpeg" /><figcaption>Jonathan presenting growth plans!</figcaption></figure><h3>Labs</h3><p><a href="https://medium.com/u/239e17ed3d91">JoJo Marion </a>shared information about <a href="http://www.jackrabbitmobile.com/smart-toys-labs/">Jackrabbit Labs</a>.</p><p>He explained how that, as a company, we’ve always aspired to be innovative, and we’ve tried many different paths, from hackathons to 20% time.</p><p>Last year we started our Labs division to make innovation a core focus of our company. Labs are experiments that we chose, with ideas, technology, and solutions developed by our team.</p><p>They’re an exciting opportunity to explore brand new ideas, new technology, and new industries. Labs are fun, challenging, and an outlet for creativity.</p><p>A few of our labs that we displayed were Smart Toys (developed by Sam Harris), James Bond Watch Drone (<a href="https://medium.com/u/5e361eee15b1">Matt Wanninger</a>, pictured, and <a href="https://medium.com/u/1abbb1ed3a4e">David Olesch</a>), Arduino music sensors (<a href="https://medium.com/u/5147dbc266f6">Caroline Harrison</a>), and Facial Recognition (<a href="https://medium.com/u/5f84d484d232">Gibrán Gaytán Silva</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*UWz1KzZ2e1Ne1zKU5QhHAg.jpeg" /><figcaption>JoJo presenting Labs!</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y6oPR_mKdnCrHrXEWnA6OA.jpeg" /><figcaption>Flying drones with an Apple Watch!</figcaption></figure><p>Thanks to <a href="https://medium.com/u/2a4ca6f3d8d9">Capital Factory </a>and all the other sponsors and participants. Thanks to the great Austin community. Thanks to NewCo for inviting us and giving us the space to share.</p><p><a href="http://www.jackrabbitmobile.com/">Jackrabbit Mobile</a> is a mobile-first creative agency in downtown Austin. We build awesome tech with awesome people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMgC-Ym5TbSiMMBlTquRsQ.png" /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below or contact us at </em><a href="/service/mailto:hello@jackrabbitmobile.com"><em>hello@jackrabbitmobile.com</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6133f5aea1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook: Operations, Administration, HR]]></title>
            <link>https://medium.com/42hire-don-t-panic-just-hire/playbook-operations-administration-hr-83c66d1781f0?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c66d1781f0</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[administration]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 13:54:51 GMT</pubDate>
            <atom:updated>2016-08-01T23:54:37.944Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jackrabbit Mobile Playbook: Operations, Administration, Finance, HR</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O6VzyYgvFW83Iha3." /></figure><h3>Operations, Administration, HR</h3><p>We strive to find an effective balance between process and practicality. We strive to eliminate bureaucracy, politics, red tape, and redundancy. When in doubt: keep things simple, do what works, and work with your team.</p><h4>Remote Meetings</h4><p>Remote meetings are usually held over <a href="https://www.google.com/url?q=https://hangouts.google.com/&amp;sa=D&amp;ust=1468683122111000&amp;usg=AFQjCNGIlMD7U7JMdYmlooUmYI5pyllxBA">Google Hangouts</a>, where we can video conference with multiple people, chat, and screen share when needed.</p><p>You can create a new Google Hangout in a Slack channel or message by typing “/hangout”. On a Google calendar invite, you can select to include a link for a Google Hangout. Hangout links can also be shared by URL.</p><p>Phone meetings are usually held with <a href="https://www.google.com/url?q=http://uberconference.com/&amp;sa=D&amp;ust=1468683122113000&amp;usg=AFQjCNEMwf8UpfqCOQb-GJdKX8amRh0PiA">Uberconference</a>. It creates a dedicated conference line for your account. It also integrates with Google Hangouts, and you can create a conference number for others to call into a Hangout.</p><h4>Chat</h4><p>We use <a href="https://www.google.com/url?q=http://slack.com/&amp;sa=D&amp;ust=1468683122114000&amp;usg=AFQjCNGRiofOONR-HjXph1XnwzNuI6Htfg">Slack</a> for company chat.</p><h4>Email</h4><p>We use Gmail for company email.</p><h4>Wiki</h4><p>We have an <a href="https://www.google.com/url?q=https://sites.google.com/site/jackrabbitinternal/&amp;sa=D&amp;ust=1468683122116000&amp;usg=AFQjCNFdkKcpSf_ckWYMdOdrh3qQIrt4DA">internal Wiki</a> for company information.</p><h4>Documents</h4><p>We use <a href="https://www.google.com/url?q=https://www.google.com/docs/about/&amp;sa=D&amp;ust=1468683122117000&amp;usg=AFQjCNG7G0y2s0v4Sga4-PSoP6xP_X8Rjw">Google Docs</a> for our documents, spreadsheets, presentations, and more.</p><p>They are great for real-time collaboration with others on a document. They have comments and suggestions features, manage edits and revision history, and automatically save. They are easy to share by URL. They can be exported and downloaded into different formats, such as PDF or Microsoft Office formats. Those formats can also be uploaded to Google Drive and converted to Google Doc format.</p><p>We store everything in <a href="https://www.google.com/url?q=http://drive.google.com&amp;sa=D&amp;ust=1468683122119000&amp;usg=AFQjCNEMu_CovDM0d1h2RK99OvgSgd3M-w">Google Drive</a>.</p><h4>Calendars, Scheduling, and Meetings</h4><p>We use Google Calendar for company calendars. The “Find a Time” feature is handy for finding a common available time.</p><p>Team members have access to coworkers calendars by default. There are also Jackrabbit calendars for Vacation Days and Holidays.</p><p>Team members are generally available between 9am-5pm, but we allow flexible schedules that enable our people to choose the times that they do their best work. Set your normal working hours in Google Calendar. Mondays and Thursdays are typically meeting days, while Tuesdays, Wednesdays, and Fridays are typically workdays (<a href="https://www.google.com/url?q=http://www.paulgraham.com/makersschedule.html&amp;sa=D&amp;ust=1468683122122000&amp;usg=AFQjCNF4AFNFsMRIQp7MGSlYl0slrAPONQ">also known as maker days</a>). If a time slot is available, it is safe to assume that the person is free and available for a meeting, although be very respectful of each other’s time.</p><p><a href="https://www.google.com/url?q=https://gettingreal.37signals.com/ch07_Meetings_Are_Toxic.php&amp;sa=D&amp;ust=1468683122122000&amp;usg=AFQjCNEz5-c-jWTV4rAPdDE8VpQwUpeFcg">We don’t hold meetings for the sake of holding meetings</a>, and most work can happen remotely and asynchronously. We encourage few meetings in favor of better work.</p><p>Each conference room has an associated calendar for reserving it. The way to reserve them is explained on the <a href="https://www.google.com/url?q=https://sites.google.com/site/jackrabbitinternal/5-administration/office&amp;sa=D&amp;ust=1468683122123000&amp;usg=AFQjCNHU8Z246HUc3RU5hn4tqqTfhtSnYQ">Office page</a>.</p><h4>Holidays</h4><p>Jackrabbit observes the following holidays every year. If a holiday lands on a weekend, then we will be closed on the next closest day. For example, if on a Saturday we will be closed Friday, and if on a Sunday we will be closed Monday.</p><ul><li>Good Friday</li><li>Memorial Day</li><li>Independence Day</li><li>Labor Day</li><li>Thanksgiving Day</li><li>Day after Thanksgiving</li><li>Christmas Day</li><li>New Year’s Eve</li><li>New Year’s Day</li></ul><p>The Jackrabbit Office is also closed for <a href="https://www.google.com/url?q=http://sxsw.com/&amp;sa=D&amp;ust=1468683122128000&amp;usg=AFQjCNGUgoTmEJKGcLEvjGvoFra0LtIEUg">SXSW</a>! We’ll be running around downtown Austin, presenting and attending awesome conference sessions with thought leaders, learning about cutting edge trends in the industry, meeting incredible people from all around the world, and having an amazing time!</p><h4>All-Hands Meetings</h4><p>All-Hands meetings are informative meetings held twice per week on Mondays and Thursday, from 10–11am and attended by everyone in the company. The agenda is found in the <a href="https://www.google.com/url?q=https://app.asana.com/0/9530019430774/list&amp;sa=D&amp;ust=1468683122130000&amp;usg=AFQjCNHORdxP-_X0UsoNApYKbNyHc_1ptQ">Team Meeting Agenda</a> in Asana and there is a Google Hangout link in the Calendar Invite. On Mondays team members demo work to the rest of the company, such as a new feature or design that was implemented, and on Thursdays we share status updates and company reports, such as sales and recruiting.</p><h4>Time Tracking</h4><p>We track our time in <a href="https://www.google.com/url?q=https://jackrabbitmobile.harvestapp.com&amp;sa=D&amp;ust=1468683122132000&amp;usg=AFQjCNEF7_vz6wcjVN8ylkqCaXaSaoILjg">Harvest</a>.</p><p>All work time should be tracked in a Harvest category. Customer work should be tagged to that customer. Non-customer work should be tagged to Jackrabbit Internal. Jackrabbit Extracurricular is used to tag time that is not part of your core responsibilities, but contributes to your growth and expertise in the industry, such as organizing our <a href="https://www.google.com/url?q=http://www.meetup.com/Austin-iPhone-Developer-Group/&amp;sa=D&amp;ust=1468683122133000&amp;usg=AFQjCNFk2Z8dS3xpUiwin8UqW14x7SYn4A">Austin iOS Developer</a> or <a href="https://www.google.com/url?q=http://www.meetup.com/Austin-Android/&amp;sa=D&amp;ust=1468683122133000&amp;usg=AFQjCNGe8G8hF1gPQvb-l3gBduYdwT98SQ">Austin Android Developer</a> Meetups.</p><p>Project managers are responsible for creating, managing, and monitoring the Harvest projects. They will set the appropriate project settings according to the terms of the Statement of Work, such as dates, budget, and invoicing schedule.</p><p>It’s very important to keep accurate track of time, including all billable and nonbillable, internal and external. These are used to track company operations and forecast future plans. Time records are used in legal and financial reporting.</p><p>Weekly timesheets should be submitted by Monday at Noon for the previous week. Project Managers should approve, deny, or respond to submitted timesheets for their projects by Monday end of day.</p><h4>Finances</h4><p>We have a bookkeeper and CPA that manages our finances and accounting, who can be reached at our finance email address.</p><p>We manage our finances with <a href="https://www.google.com/url?q=https://qbo.intuit.com/app/homepage&amp;sa=D&amp;ust=1468683122137000&amp;usg=AFQjCNH7ZdhhajILq2SozWtF_5zXBhSGtw">QuickBooks</a>, including financial reports, invoicing customers, and paying bills. We use <a href="https://www.google.com/url?q=http://harvestapp.com&amp;sa=D&amp;ust=1468683122138000&amp;usg=AFQjCNHKndNN86eGK51JiOZ8DgzDt2M7xw">Harvest</a> for project and time tracking.</p><p><strong>Invoicing</strong></p><p>We invoice our customers every sprint for the work completed over the past sprint.</p><p>Our invoicing terms are Net-21. Late payments are subject to a late fee.</p><p>Invoices can be paid via Bank Transfer or Check for no fee, or through Credit Card or PayPal for a processing fee.</p><p>Invoice reminders are automatically sent to customers one week, and one day, before the due date.</p><p><strong>Payments</strong></p><p>Vendors and contractors should email invoices to Finance. Invoices should be formatted and include an invoice number, date range, work details, rate, and total. Here’s an <a href="https://www.getharvest.com/resources/invoice-template-pdf">invoice template PDF</a>.</p><p>We process bills and payments twice per month, on the 1st and 15th. Payments can be sent through PayPal (for a processing fee), Paychex Direct Deposit (our preferred method), or Chase Bill Pay mailed check.</p><p>Direct deposit can be set up by completing the Paychex Enrollment form found on <a href="http://www.paychex.com/resources/employee-forms.aspx">this page</a> and submitting to Finance. A voided check, deposit slip, or bank specification form is required.</p><p>Payroll is processed on the 1st of each month for the previous month and is deposited within 2–3 business days.</p><p>Everyone can access their pay stubs and reports through <a href="https://www.google.com/url?q=https://myapps.paychex.com/landing_remote/login.do?TYPE%3D33554433%26REALMOID%3D06-fd3ba6b8-7a2f-1013-ba03-83af2ce30cb3%26GUID%3D%26SMAUTHREASON%3D0%26METHOD%3DGET%26SMAGENTNAME%3D09PZJoiHr8jiAF1z4DL6SopY5OyRzoKSeZ4yIhpJe7nkRdeIwtlMrg0rd7X3FRDM%26TARGET%3D-SM-https%253a%252f%252fmyapps.paychex.com%252f&amp;sa=D&amp;ust=1468683122144000&amp;usg=AFQjCNG0UxIIqo_e0cm2c18z6hrrzSCIzg">Paychex Flex</a>.</p><p><strong>Expenses</strong></p><p>Company expenses should be pre-approved by a Partner. Project expenses should be pre-approved by a project manager. Receipts should be submitted to Finance and will be reimbursed on the next payment or payroll.</p><h4>Office</h4><p>The Jackrabbit Office is located in downtown Austin, on West 6th Street. Contact us if you’d like to come visit!</p><h4>Community</h4><p>Community involvement is one of our values, and part of our mission of building awesome tech with awesome people is connecting with those people. It’s fun, it’s rewarding, and it’s something that we’d each be doing even if we weren’t working at Jackrabbit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jsyzQLc6Uy8CuqI5." /></figure><p>Communities and events that we’re involved with:</p><ul><li><a href="http://www.meetup.com/Austin-iPhone-Developer-Group/">Austin iOS Developer Meetup</a>, Organizer</li><li><a href="http://www.meetup.com/Austin-Android/">Austin Android Developer Meetup</a>, Organizer</li><li><a href="http://capitalfactory.com/">Capital Factory</a>, Member/Mentor</li><li><a href="http://austintechnologycouncil.org/">Austin Technology Council</a>, Member</li><li><a href="https://3daystartup.org/">3 Day Startup</a>, Mentor</li><li><a href="http://www.austinchamber.com/index.php">Austin Chamber of Commerce</a>, Member</li><li><a href="http://www.productcampaustin.org/">ProductCamp Austin</a>, Past Sponsor &amp; Participant</li></ul><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><h4>Thanks!</h4><p>We really hope you enjoyed this Playbook.</p><p>If you’d like to build some awesome technology with us, or have a question or comment, we’d love to hear from you at <a href="/service/mailto:hello@jackrabbitmobile.com">hello@jackrabbitmobile.com</a></p><blockquote>A downloadable PDF of the Playbook is available at: <a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></blockquote><ul><li><strong>The Jackrabbit Mobile Team</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBai0KsRlWRySH1C." /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c66d1781f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/42hire-don-t-panic-just-hire/playbook-operations-administration-hr-83c66d1781f0">Playbook: Operations, Administration, HR</a> was originally published in <a href="https://medium.com/42hire-don-t-panic-just-hire">Don&#39;t Panic, Just Hire</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook: Hiring]]></title>
            <link>https://medium.com/42hire-don-t-panic-just-hire/playbook-hiring-b4dac7ec27c5?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4dac7ec27c5</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 13:54:45 GMT</pubDate>
            <atom:updated>2016-07-17T13:54:45.334Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jackrabbit Mobile Playbook: Hiring</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O6VzyYgvFW83Iha3." /></figure><h3>Hiring</h3><h4>Recruiting</h4><p>We’re always recruiting and keeping an eye out for who we’d like to have join our team because we’re constantly meeting new people and frequently starting new projects that require an evolving set of skills. We feel that the best candidates are the ones we really get to know, so our interview process focuses on learning about each other.</p><p>We have a <a href="https://www.google.com/url?q=http://www.jackrabbitmobile.com/jobs/&amp;sa=D&amp;ust=1468683122087000&amp;usg=AFQjCNFDYkhd4EUJj7pDV7eUNqrC5YcimA">our jobs page here</a> and applications can be submitted to us via <a href="https://www.google.com/url?q=https://angel.co/jackrabbit-mobile/jobs&amp;sa=D&amp;ust=1468683122088000&amp;usg=AFQjCNHIxwtWEIDgEqZfV-G-iW6UkFxEKA">AngelList</a>.</p><p>Skillsets that we most commonly recruit:</p><ul><li>Mobile Developers</li><li>UI/UX Designers</li><li>Project Managers</li><li>Web Developers</li><li>Backend Developers</li></ul><p>Our hiring process is based on <a href="https://www.google.com/url?q=http://www.topgrading.com/&amp;sa=D&amp;ust=1468683122090000&amp;usg=AFQjCNFlDIpjasBgA-X1p2aNKxTnq3K8dQ">Topgrading</a> and we manage it using <a href="https://www.google.com/url?q=https://angel.co/jackrabbit-mobile/track&amp;sa=D&amp;ust=1468683122091000&amp;usg=AFQjCNGhjGCcSHdQLp0YO1JFUQRnPoC2lA">AngelList Track</a>.</p><h4>Interview Process</h4><p><strong>Initial Screen</strong></p><p>We receive a lot of applications from a wide range of people. The first step is to verify that we’re a potential fit to work together by understanding the candidate’s experience, skills, and goals. A potential fit is someone that has the technical skills to be successful, has experience applying them in a similar environment, and someone who would benefit and grow from working at Jackrabbit.</p><p>We first evaluate that fit with a few questions about a candidate’s experience and goals, and exercises to illustrate their abilities.</p><p><strong>Intro Call</strong></p><p>The second step is to have an intro call to get to know each other. This will be a 10 to 20-minute Google Hangout with someone at Jackrabbit where we’ll get to share more about Jackrabbit’s history and mission, and are excited to learn more about their experience and goals.</p><p>We find that video conferencing helps to get to know each other, especially if we haven’t met in-person before.</p><p>Here we’re looking to follow up and dive deeper into the initial questions we asked. We’re feeling out each other and it’s important that both parties evaluate if we could see ourselves working together.</p><p><strong>References and Work Samples</strong></p><p>Before the technical interview we’ll ask to see some more of the candidate’s previous work. For developers we like to see GitHub repositories, for designers we like to see portfolios, and for project managers we like to see case studies. Live material is the best, such as links to apps on the App Store, open source projects, or active production webapps.</p><p><strong>Technical Interview</strong></p><p>The next step is a technical interview with someone on our team. If the candidate is an iOS developer then we’ll have them sit down with one of our iOS developers to talk through the technical details of their experience, strengths, and preferences. We’ll ask technical questions to gauge familiarity with the tools, techniques, and processes we follow. We’ll also work through a short exercise together, typically either a coding problem for developers, a creative session for designers, or an agile exercise for project managers.</p><p><strong>Culture Interview</strong></p><p>The last step is to have a culture interview on-site with a few members of our team. We may include managers and people from different teams, who’ll will be given a short brief, but we want them to form their own opinions about the candidate. We want the candidate to get a feel for what it would be like to work at our company as much as we want our team to to get a feel for what it would be like to work with them.</p><h4>Offer</h4><p><strong>Contract-to-hire period</strong></p><p>Hiring starts with a three month contract-to-hire relationship. We typically like to have a specific project in mind that we’ll start working on together. This lets us both test out the relationship over an extended period of time to verify that it is a good fit and that we both enjoy working together. We have a Contractor Agreement that outlines the terms and responsibilities that we’ll sign together and get started.</p><p>During this time it’s important to join team meetings and team events, ask a lot of questions, get settled in with our tools and processes, and understand how we operate. We’ll have a monthly check-in along the way.</p><p><strong>Employment</strong></p><p>We’ll send you an offer letter, which formalizes the details of the offer and the position, and sign an employment agreement, which covers the terms and policies of working with Jackrabbit and our customers.</p><h4>Onboarding</h4><p><strong>First day</strong></p><p>Welcome! First day means breakfast tacos and introductions! You’ll typically start on a Monday or Thursday morning so that you can meet everyone at Team Meeting.</p><p>Then you’ll sit down with the Partners and your team lead for an onboarding meeting. You already know us pretty well by now, but we’ll go over some history about the company, our values, and our plans for the future. We’ll talk through day-to-day responsibilities and operations, and have lots of time for questions.</p><p>We’ll create all of your accounts, starting with your Jackrabbit email address, and help you get set up with all of the tools you’ll need, such as Slack, Harvest, Trello, and more.</p><p><strong>First month</strong></p><p>We’ll schedule a 1-month check-in to formally sit down and review how everything is going.</p><p>The first month starts with getting familiar with everyone on the team, projects and Labs that we’re working on, and comfortable with the tools and working environment. We find that’s best done by shadowing projects, all the departments at Jackrabbit, from Sales to Design, and working 1–1 with a senior member of the team.</p><h4>Quarterly Reviews</h4><p>Every quarter you’ll have a one-on-one review meeting with one of the Partners or team leads. This is a time to sit down and evaluate the past quarter, progress towards goals, and be aligned for the future. We’ll provide feedback on strengths and weaknesses, but we believe it’s even more important to hear your thoughts on your self-evaluation, so we can goal set together.</p><p>We want to make sure you’re working on what you want to work on, and growing in the direction you want to grow, so that we all enjoy what we’re doing, and do our best work together</p><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><h4>Thanks!</h4><p>We really hope you enjoyed this Playbook.</p><p>If you’d like to build some awesome technology with us, or have a question or comment, we’d love to hear from you at <a href="/service/mailto:hello@jackrabbitmobile.com">hello@jackrabbitmobile.com</a></p><blockquote>A downloadable PDF of the Playbook is available at: <a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></blockquote><ul><li><strong>The Jackrabbit Mobile Team</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBai0KsRlWRySH1C." /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4dac7ec27c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/42hire-don-t-panic-just-hire/playbook-hiring-b4dac7ec27c5">Playbook: Hiring</a> was originally published in <a href="https://medium.com/42hire-don-t-panic-just-hire">Don&#39;t Panic, Just Hire</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook: Labs]]></title>
            <link>https://blog.prototypr.io/playbook-labs-ea95199a7524?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea95199a7524</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 13:54:36 GMT</pubDate>
            <atom:updated>2016-07-20T20:34:06.368Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jackrabbit Mobile Playbook: Labs</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O6VzyYgvFW83Iha3." /></figure><h3>Labs</h3><h4>Mission</h4><p>As a company, investing time and resources into real innovation is a core value. Jackrabbit Labs strives to help enable personal and team growth, drive a culture of innovation and creativity, and to empower us to work with new technologies and spaces that we as individuals and as a company are passionate about.</p><p>Anyone can contribute to a Labs project. Some Labs projects are scheduled but it’s also a great way to use down time between Services projects.</p><p>What have we done in Labs? Here are some examples!</p><ul><li><a href="http://www.builtinaustin.com/2016/03/02/jackrabbit-mobile-bluetooth-beacons">How Jackrabbit Mobile is bringing ‘dumb toys’ to life</a></li><li><a href="https://www.youtube.com/watch?v=40SA0_qGyhk">Interactive toys and beacons at TedX Youth Austin</a></li><li><a href="https://www.youtube.com/watch?v=hFChuauEOos">Apple Watch &amp; Parrot Dones</a></li></ul><h4>Ideation</h4><p>Ideas can either start from an individual, by simply sharing, pitching or pushing the team into new directions, or from internal ideation sessions. We use a brainstorming and ideation process similar to our design sprint workshops.</p><p>Innovation, experimentation and prototyping is what we’re focused on, not products. There’s a lot of things we could design and build, but first we start by asking ourselves why. Why is this interesting, who would it help, what problem would it solve, who would read about it, and what can we learn?</p><h4>The Process</h4><p>Since we focus on new ideas and technologies, our starting point involves research into this new space we plan to focus on. This involves exploring what types of technology to use and proving feasibility, which usually lasts 2 weeks. Once we’re ready to move, we we’ll plan a project road map. We then start the build, measure and learn loop which can last between 2–6 weeks.</p><h4>Testing Viability</h4><p>The way that we decide continue Labs is by taking our experiments and innovations and getting them out there in front of future client partners and potential future candidates.</p><h4>Outcomes</h4><p>A successful Labs project is one that we learn from. Depending on the project, there’s a variety of different outcomes we may produce. Some may evolve into a presentation or blog post, some may be published or open sourced, some may be used in a future project or to help tech and client partners.</p><p>Here are some more examples of outcomes:</p><ul><li>Technical Analysis</li><li>Case Study</li><li>Infographic</li><li>Meetup Presentation</li><li>Blog Post</li><li>Networking</li><li>Social Media</li><li>Partnership</li></ul><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><h4>Thanks!</h4><p>We really hope you enjoyed this Playbook.</p><p>If you’d like to build some awesome technology with us, or have a question or comment, we’d love to hear from you at <a href="/service/mailto:hello@jackrabbitmobile.com">hello@jackrabbitmobile.com</a></p><blockquote>A downloadable PDF of the Playbook is available at: <a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></blockquote><ul><li><strong>The Jackrabbit Mobile Team</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBai0KsRlWRySH1C." /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea95199a7524" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/playbook-labs-ea95199a7524">Playbook: Labs</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook: Engineering]]></title>
            <link>https://medium.com/mobile-growth/playbook-engineering-16cd0871dbf0?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/16cd0871dbf0</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 13:54:26 GMT</pubDate>
            <atom:updated>2016-10-28T14:28:09.417Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jackrabbit Mobile Playbook: Engineering</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O6VzyYgvFW83Iha3." /></figure><h3>Engineering</h3><h4>Jackrabbit’s approach to software engineering</h4><p>Jackrabbit builds and releases native iOS and Android apps. Each app is frequently updated with new features. We plan each feature by splitting it up into functionality statements called user stories. Each project team implements a handful of user stories each week. We define the required changes and acceptance criteria for the changes at the beginning of the week and we demo the completed changes to all stakeholders at the end of the week. This process follows the principles of agile development.</p><p>Each team member is placed on the project team they feel most fit and interested in working on. This leads to highly productive teams that exceed stakeholder’s expectations most weeks. Sometimes we do run into problems that prevent features from being ready by the expected deadline. When this happens we can reprioritize remaining features, add developers or slightly push a release date. In any case we don’t rush if a feature takes longer than expected because cutting corners will lead to subpar results.</p><p>The following chapters outline the best approach we know to developing mobile-first applications for our set of clients ranging from funded startups to larger enterprise and the variety of projects we’ve delivered, from healthcare to dating apps.</p><h4>Architecture patterns</h4><p><strong>Client side architecture</strong></p><p>Our client-side architecture, regardless of platform, always follows object oriented programming principles and the Model-View-Controller, or MVC, software architecture pattern. This pattern divides the code up cleanly between the model (which holds the app’s data and business logic), the view (the user interface to show and modify the data), and the controller (an intermediary between the model and the view). This separation of responsibilities helps our developers focus on one aspect of the app at a time, as well as allowing multiple developers to work on different pieces of the code in parallel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/0*_etfZe9tsoNG9RFr." /><figcaption>Image Source: <a href="https://www.objc.io/issues/13-architecture/mvvm/">https://www.objc.io/issues/13-architecture/mvvm/</a></figcaption></figure><p>We take the MVC pattern one step further with MVVM, or <a href="https://www.google.com/url?q=https://www.objc.io/issues/13-architecture/mvvm/&amp;sa=D&amp;ust=1468683121989000&amp;usg=AFQjCNE5gOwX6YAjfsXvp6NUhcLZL7WtUg">Model-View-ViewModel</a>. In practice we find that, in MVC applications, the controller can grow to be very large and begin to have too much responsibility as it is so closely connected to the view it is controlling. MVVM formalizes this connection by combining the view and controller into the View, while the ViewModel now takes responsibility of the view presentation logic and interaction with the Model data out of the controller. This helps to make our apps have lighter and more testable views and controllers than what we tend to experience with traditional MVC.</p><p><strong>Backend services</strong></p><p>When we build a client-side app that requires interaction with backend services, such as a database or file storage, we strongly believe in using RESTful principles to guide the app’s interaction with a backend API. REST leverages existing HTTP functionality and helps separate the API endpoints into logical resources for easy consumption by client apps.</p><p>These resources should be divided into the correct GET, POST, PUT, PATCH, and DELETE actions. The resource names are plural nouns and the services should return sensible HTTP status codes. Other practices should also be followed, such as: putting the API version in the URL, filtering and sorting actions passed as parameters, and cursor-based pagination.</p><p>Likewise, we strongly prefer working with backends that serve JSON-only responses as opposed to the more verbose, difficult to parse, and less compatible XML. Whether we are building the backend ourselves or integrating with a client’s, RESTful practices, JSON responses, and a well-documented API help us to easily integrate and interact with backend services.</p><p>Lastly, we are proponents of <a href="https://www.google.com/url?q=https://letsencrypt.org/2014/11/18/announcing-lets-encrypt.html&amp;sa=D&amp;ust=1468683121992000&amp;usg=AFQjCNFolZZXd37t2aaUVdUBaWPF-WS8Ug">SSL Everywhere</a> and believe all traffic coming to and from our apps should be securely encrypted, so we also demand these expectations for our backend. Apple is pushing its mobile developers to embrace SSL/TLS (and encryption in general) with their <a href="https://www.google.com/url?q=https://developer.apple.com/library/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS9.html%23//apple_ref/doc/uid/TP40016198-SW14&amp;sa=D&amp;ust=1468683121993000&amp;usg=AFQjCNGKebsZ_LYEHWjOR_Lqmw7VY8gcAw">App Transport Security</a> introduced in iOS 9, and is likely to require it in a future version of iOS. When dealing with authentication, it should be established through an /Auth endpoint and maintained through an auth-token header field.</p><p><strong>Code re-use</strong></p><p>Throughout the course of working on many projects, we have found that many apps we build use similar architectures and coding patterns to get them up and running; especially related to commonly used pieces like networking, databases, view management, and more. When we notice a particular theme where we are writing the same code over and over for different projects, we will usually try to generalize it and turn it into a shared library that can be used on any of the apps we build going forward. For example, see our <a href="https://www.google.com/url?q=https://github.com/JackrabbitMobile/JRMSimpleGeofenceManager&amp;sa=D&amp;ust=1468683121995000&amp;usg=AFQjCNEB484J-Pis_uVQ2yNj0DXbPLz-0w">JRMSimpleGeofenceManager</a> library</p><p>This helps us to more quickly get new projects up and running as well as prevent a lot of duplicate work on basic features we’ve already built before. Features only built once for one app are generally not something we will do this with, as they are usually specific to solving the problems for that app.</p><h4>Documentation</h4><p><strong>Project documentation</strong></p><p>The bulk of project documentation is created during the Project Discovery and Strategy phases. Project documentation answers all the common questions that are required for planning and implementing a mobile app. Project documentation includes an initial list of use cases and user stories, a <a href="https://www.google.com/url?q=https://en.wikipedia.org/wiki/System_context_diagram&amp;sa=D&amp;ust=1468683121998000&amp;usg=AFQjCNERYslFHf_vD7bo_81Ow1MVg9WfTA">system diagram</a> and a <a href="https://www.google.com/url?q=https://en.wikipedia.org/wiki/Data_model&amp;sa=D&amp;ust=1468683121998000&amp;usg=AFQjCNGBgUISeEfAwvcLKRIgxR9Qy0o9wQ">data model</a>. It is also often useful to define the <a href="https://www.google.com/url?q=http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api&amp;sa=D&amp;ust=1468683121999000&amp;usg=AFQjCNFurxrv9twMxnhl43zR9aNeOSdfCw">REST contract</a> in the project documentation so that the backend team knows how their code will interface with the front end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*FPQe3YAZMjj5BXQ6." /></figure><p><strong>Code base documentation</strong></p><p>Code base documentation is a combination of reference documentation auto-generated from <a href="https://www.google.com/url?q=http://agile.csc.ncsu.edu/SEMaterials/tutorials/javadoc/&amp;sa=D&amp;ust=1468683122000000&amp;usg=AFQjCNGotZUYvZ4WSRO3Qle8Hvd4C_8E4g">javadoc</a> formatted comments in the source code and a summary of the app architecture. The tools we use to auto-generate reference documentation are explained in Chapter 4: Developer Tools. The app architecture is the tech lead’s blueprint for how all the different app components fit together to create a piece of software that fulfils the required use cases. It lists all the major components of the app and explains how the components are implemented. As such it’s a very useful thing to have when the project is moved to a new team or when a new member joins the project team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/0*I-L9kqmC-75jzwRf." /></figure><p>The app architecture lists all major objects such as the network manager, push manager or routing manager. It lists <a href="https://www.google.com/url?q=https://developer.apple.com/library/ios/documentation/iPhone/Conceptual/iPhoneOSProgrammingGuide/Inter-AppCommunication/Inter-AppCommunication.html&amp;sa=D&amp;ust=1468683122002000&amp;usg=AFQjCNFVUQc9Jb1HB8Qdd4emPqopJ8c-nQ">deep links</a> the app can handle (iOS) and <a href="https://www.google.com/url?q=http://developer.android.com/reference/android/content/Intent.html&amp;sa=D&amp;ust=1468683122003000&amp;usg=AFQjCNHX7qRqn7Ih4Edn5m23F-m8Gb4fEw">intents</a> it can handle (Android). It lists the models used by the app, including the names of model classes and the business logic <a href="https://www.google.com/url?q=http://www.oodesign.com/single-responsibility-principle.html&amp;sa=D&amp;ust=1468683122003000&amp;usg=AFQjCNHXxyJjkPNDYrlxdRCUx0rD2wpv4Q">responsibilities</a> of each model. It explains how information is shared among the app’s objects (e.g. with <a href="https://www.google.com/url?q=http://developer.android.com/reference/android/os/Parcelable.html&amp;sa=D&amp;ust=1468683122004000&amp;usg=AFQjCNEqYcsAYnJZDAiTdmsUZvj5G5tjtQ">parcelables</a> for Android and through <a href="https://www.google.com/url?q=https://developer.apple.com/library/ios/documentation/DataManagement/Devpedia-CoreData/managedObjectContext.html&amp;sa=D&amp;ust=1468683122004000&amp;usg=AFQjCNFfgaEjb2tMEALMJKbyVS9zgHh1_g">managed object contexts</a> for iOS). It lists any architecture patterns being used such as <a href="https://www.google.com/url?q=https://developer.apple.com/library/ios/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html&amp;sa=D&amp;ust=1468683122005000&amp;usg=AFQjCNEfScJMtGwXDxYOIBkljAJW4_Cd_Q">MVC</a> or <a href="https://www.google.com/url?q=https://github.com/konmik/konmik.github.io/wiki/Introduction-to-Model-View-Presenter-on-Android&amp;sa=D&amp;ust=1468683122006000&amp;usg=AFQjCNGfjdrz9NofAA-iQAAbctpvjn6w2g">MVP</a> for Android and <a href="https://www.google.com/url?q=https://www.objc.io/issues/13-architecture/mvvm/&amp;sa=D&amp;ust=1468683122006000&amp;usg=AFQjCNECOi4gEN0nLIG4Zk8VKLKWb-4paQ">MVVM</a> for iOS. It summarizes how the layouts are organized and how they are instantiated including fragments on Android and custom UIView subclasses on iOS.</p><p>The app architecture also lists all the app’s library dependencies and 3rd-party SDKs used. It explains any complex implementations that don’t follow standard patterns. On iOS it lists additional project specific configurations such as those in the Info.plist, whether it is using <a href="https://www.google.com/url?q=https://cocoapods.org&amp;sa=D&amp;ust=1468683122007000&amp;usg=AFQjCNGP388hQ4PHfOVuUr0r762XrimALQ">CocoaPods</a>, and if it is using class extensions or precompile headers. On Android it lists additional project specific configurations such as those in the <a href="https://www.google.com/url?q=http://developer.android.com/guide/topics/manifest/manifest-intro.html&amp;sa=D&amp;ust=1468683122008000&amp;usg=AFQjCNGfgp-8C46il8Ih8wcSVvQndf5LDw">app manifest</a> or build scripts.</p><h4>Developer tools</h4><p><strong>Development Tools</strong></p><p>Each app we build has a single codebase. We edit this codebase in the <a href="https://www.google.com/url?q=https://developer.apple.com/xcode/download/&amp;sa=D&amp;ust=1468683122011000&amp;usg=AFQjCNGl95dYBE62U_v5iT2Hyo9YAx8wQw">current release of Xcode</a> for iOS and in the <a href="https://www.google.com/url?q=http://tools.android.com/preview-channel&amp;sa=D&amp;ust=1468683122011000&amp;usg=AFQjCNGf1Bj7CdjLwXon9diwozGGL3V3hQ">Dev Channel release of Android Studio</a> for Android. Each codebase supports the latest versions of each operating system as well as some of the previous versions. We aim to support the operating system in use on 90+% of devices. As of early 2016 this level of operating system support requires supporting <a href="https://www.google.com/url?q=https://mixpanel.com/trends/%23report/ios_9&amp;sa=D&amp;ust=1468683122012000&amp;usg=AFQjCNFFmQwx4MPbf-OJNRE6LdQr7HTH3w">iOS</a> 8.1 and later and <a href="https://www.google.com/url?q=http://developer.android.com/about/dashboards/index.html&amp;sa=D&amp;ust=1468683122013000&amp;usg=AFQjCNG3c213tFHDhpMX7tYUz6DWckZbRQ">Android</a> API 16 and later. We write our Android code in Java and our iOS code in Objective-C or Swift.</p><p><strong>Libraries and Frameworks</strong></p><p>We make extensive use of well documented and maintained libraries and frameworks because they reduce development time by reusing code that’s already been written, while simultaneously reducing the number of potential defects that may appear because they’ve usually already been addressed by the library maintainers. Libraries and frameworks also decouple modules of functionality so that our code can focus on the app’s business logic without reimplementing common features that already exist.</p><p>Android and iOS both have very active open source communities. We use libraries shared by people in these communities and contribute back to the libraries any improvements we make. For example, some of our most used iOS libraries are <a href="https://www.google.com/url?q=https://github.com/AFNetworking/AFNetworking&amp;sa=D&amp;ust=1468683122015000&amp;usg=AFQjCNEHnFsnvd9thNN-beGulWAn0ByFhA">AFNetworking</a> which simplifies creating web service requests and parsing their responses, <a href="https://www.google.com/url?q=https://github.com/wtmoose/TLIndexPathTools&amp;sa=D&amp;ust=1468683122015000&amp;usg=AFQjCNFm4HgUL8zJsko9lHp0YB2gZU1h9Q">TLIndexPathTools</a> which simplifies managing a presentation data model for tables and collection views, and <a href="https://www.google.com/url?q=https://github.com/SVProgressHUD/SVProgressHUD&amp;sa=D&amp;ust=1468683122016000&amp;usg=AFQjCNGNkDLuA5dRAkbKZnlZ0WcSQwR0IA">SVProgressHUD</a> which is used for showing customizable modal alerts which dismiss themselves. On Android our most used libraries are <a href="https://www.google.com/url?q=https://github.com/square/picasso&amp;sa=D&amp;ust=1468683122016000&amp;usg=AFQjCNEvmFnkBRoHRoY6TtRcUQH6WWCiMA">Picasso</a> for downloading and caching images, <a href="https://www.google.com/url?q=https://github.com/square/retrofit&amp;sa=D&amp;ust=1468683122017000&amp;usg=AFQjCNE9ldopqH0fuOij1KR9gqEWl_U_zA">Retrofit</a> for networking, and <a href="https://www.google.com/url?q=https://github.com/square/dagger&amp;sa=D&amp;ust=1468683122017000&amp;usg=AFQjCNFTSaEsX1ukB8LdHQBxD2crKCGNWw">Dagger</a> for dependency injection.</p><p>We’ve also got some private libraries that we commonly use. We have JRMPushManager which can acquire and upload device tokens and show in-app alerts for received push notifications. We have <a href="https://www.google.com/url?q=https://github.com/JackrabbitMobile/JRMRestBase&amp;sa=D&amp;ust=1468683122019000&amp;usg=AFQjCNG8B4IBkZ4cpIFCKDRdD0AvXLb_Ew">JRMRestBase</a> for querying RESTful APIs and parsing JSON responses into managed objects, and we have JRMAuthManager for maintaining client side user sessions with a username stored to the system defaults and a password stored in the Keychain.</p><p>We also commonly integrate with 3rd party services using their native SDK frameworks. These 3rd party services do the heavy lifting required for things like payment processing and crash reporting. We use <a href="https://www.google.com/url?q=https://fabric.io/kits/ios/crashlytics&amp;sa=D&amp;ust=1468683122019000&amp;usg=AFQjCNGdmvFsb1Gm3313hqcxmHORrewp8g">Crashlytics</a> to upload crash reports from end user’s devices so that we can see the affected device types, OS versions and even the line numbers where crashes occur. We use <a href="https://www.google.com/url?q=https://stripe.com/checkout&amp;sa=D&amp;ust=1468683122020000&amp;usg=AFQjCNEtfIQ29Jh4bydprZrcsDbdFKUdlQ">Stripe Checkout</a> for accepting credit card payments without having to worry about maintaining a merchant account or PCI compliance rules. We use <a href="https://www.google.com/url?q=https://github.com/ParsePlatform/parse-server&amp;sa=D&amp;ust=1468683122020000&amp;usg=AFQjCNFqxYOPAx7afZtQf5AALvb6OBZedw">Parse</a> for channeling user and app data from native iOS and Android clients to a shared database server. Almost every project gets its own set of additional 3rd party integration such as <a href="https://www.google.com/url?q=https://developer.salesforce.com/page/Salesforce_APIs?d%3D70130000000lzoV%26internal%3Dtrue&amp;sa=D&amp;ust=1468683122021000&amp;usg=AFQjCNEM3DOpmGKSQXSwnVPTqxzgm9U-kA">Salesforce</a> integration for CRM data and <a href="https://www.google.com/url?q=https://www.google.com/admob/monetize.html&amp;sa=D&amp;ust=1468683122021000&amp;usg=AFQjCNG8Ljb2IIGTqAsMtmDFlLu479MOmQ">AdMob</a> integration for advertising.</p><p>Each library or framework must be configured to correctly integrate with our projects and reintegrated whenever the library or framework maintainers release a new version. We use dependency managers to automate these integrations and reintegrations. We use <a href="https://www.google.com/url?q=https://guides.cocoapods.org/using/using-cocoapods.html&amp;sa=D&amp;ust=1468683122022000&amp;usg=AFQjCNGGQKY2JFe8PP57YIDM4x0o-dG-Kg">CocoaPods</a> for iOS projects and <a href="https://www.google.com/url?q=http://gradle.org/why/robust-dependency-management/&amp;sa=D&amp;ust=1468683122023000&amp;usg=AFQjCNFqr91mrHVbzLANVuLlaqyBOEfa5g">Gradle</a> for Android projects. Both tools make it quick and simple to pull in open source or private code repositories straight into Xcode or Android Studio while keeping the dependency files isolated from the project specific files. Dependency files are pulled into a Pods subdirectory when using CocoaPods and cached in the ~/.gradle directory when using Gradle. We don’t want dependency code in our git repository so we <a href="https://www.google.com/url?q=https://guides.cocoapods.org/using/using-cocoapods.html%23should-i-check-the-pods-directory-into-source-control&amp;sa=D&amp;ust=1468683122023000&amp;usg=AFQjCNHVHaRadQFJcZc5nREIZkPw9wRZKQ">add the Pods directory to each project’s .gitignore</a> when using CocoaPods for dependency management.</p><p><strong>Open Source Licenses</strong></p><p>It’s always important to understand the licenses under which you can use each of your dependencies. We prefer using libraries that are available under <a href="https://www.google.com/url?q=https://en.wikipedia.org/wiki/Permissive_free_software_licence&amp;sa=D&amp;ust=1468683122025000&amp;usg=AFQjCNGUf-GGp9BE9G0S6qR2YP00QudSAA">permissive licenses </a>that don’t require our derivate work to be open source or non-commercial. For iOS this is usually the <a href="https://www.google.com/url?q=https://tldrlegal.com/license/mit-license%23summary&amp;sa=D&amp;ust=1468683122025000&amp;usg=AFQjCNFm6npAXx7AwyyVFi8ZBnp6LzSduw">MIT license</a> and for Android it’s the <a href="https://www.google.com/url?q=https://tldrlegal.com/license/apache-license-2.0-%2528apache-2.0%2529&amp;sa=D&amp;ust=1468683122026000&amp;usg=AFQjCNG6WGUXPbxYcJUIJYHKdGx604tKyQ">Apache License v2.0</a>.</p><p><strong>Frequently used tools</strong></p><p>There aren’t many tools necessary for native app development aside from Xcode and Android Studio. However we do use a handful of tools for debugging and finding ways to tune the performance of our apps. We use the iOS simulator and the Android <a href="https://www.google.com/url?q=https://www.genymotion.com/features/&amp;sa=D&amp;ust=1468683122028000&amp;usg=AFQjCNEbKzMBQmCoyINP4Cf4PJ5Mqg1kcw">Genymotion</a> emulator to run builds of our app as we are developing. We use Quicktime and <a href="https://www.google.com/url?q=https://chrome.google.com/webstore/detail/vysor-beta/gidgenkbbabolejbgbpnhbimgjbffefm&amp;sa=D&amp;ust=1468683122028000&amp;usg=AFQjCNHhR8nMc7_mxiVuBGdb4e-8TKIkog">Vysor</a> to mirror real devices to our Macs so that they can be recorded and shared. We use <a href="https://www.google.com/url?q=https://www.charlesproxy.com/overview/&amp;sa=D&amp;ust=1468683122029000&amp;usg=AFQjCNHzJCQ1KwSt-7h0v-ydjjtyHM9Esg">Charles Proxy</a> to record the network activity of our apps. On iOS we use <a href="https://www.google.com/url?q=https://github.com/facebook/chisel/blob/master/README.md&amp;sa=D&amp;ust=1468683122029000&amp;usg=AFQjCNGTk7FnWEmwAkKn0SX7jZC-gBjyUA">Chisel</a> for advanced UI debugging beyond what’s built into LLDB. We use a command line tool called <a href="https://www.google.com/url?q=https://github.com/jkbrzt/httpie/blob/master/README.rst&amp;sa=D&amp;ust=1468683122030000&amp;usg=AFQjCNEVa6h1_xwM6CIAhl_Y5Beumv6vAA">HTTPie</a> to run HTTP requests and understand server responses and we use the <a href="https://www.google.com/url?q=https://www.npmjs.com/package/canned-response-server&amp;sa=D&amp;ust=1468683122031000&amp;usg=AFQjCNFzotI2BdnKLliAyRIkxo19H37lfQ">canned-response-server</a> node module to stub out arbitrary JSON responses to any server request to quickly test how our apps behave when the server returns a different set of responses for a given set of requests. We also use <a href="https://www.google.com/url?q=https://github.com/square/leakcanary/blob/master/README.md&amp;sa=D&amp;ust=1468683122031000&amp;usg=AFQjCNECGSL1BQ9E-PlfCHaPC-PURroePw">Leaky Canary</a> and Xcode <a href="https://www.google.com/url?q=https://developer.apple.com/library/tvos/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/&amp;sa=D&amp;ust=1468683122032000&amp;usg=AFQjCNH5EIAOyZVwhPSKTNM8gCCaiVleig">Instruments</a> to diagnose memory leaks and performance bottlenecks in our code.</p><h4>Project organization guidelines</h4><p>Coding style patterns are the rules of formatting and code organization we expect of all code that is checked into version control. We use a single set of coding style patterns for writing native mobile apps in Objective-C, Swift and Java. This sounds like it wouldn’t be possible but it is because we allow the style patterns to defer to the language’s’ own patterns where necessary and we allow for consistency of style patterns within a project to override the “correctness” of the style patterns used.</p><p><strong>Our coding style patterns</strong></p><p>We use the IDE’s default indentation style for indenting nested levels of code. In Xcode this is a single tab for each level of indentation and in Android Studio it’s four spaces. We place the opening brace for methods on the same line as the method declaration and the closing brace on a line all by itself. In Objective-C, we include a single space at the beginning of method declaration between the — or + and the return type. This rule doesn’t apply to Java or Swift because these don’t use a — or + in method declarations. We list public methods before private methods, implementation methods before class methods and group methods involved in the same responsibility, such as presentation or networking, together. On iOS we label grouped methods using #pragma mark notation.</p><p>We document any nontrivial methods with a one sentence comment explaining the purpose of the method. These comments are later used to <a href="https://www.google.com/url?q=https://github.com/realm/jazzy&amp;sa=D&amp;ust=1468683122035000&amp;usg=AFQjCNEs3gAyyIAQbhck5lLEDRoYuMsp3Q">automatically generated documentation</a> for the project. We use the <a href="https://www.google.com/url?q=http://agile.csc.ncsu.edu/SEMaterials/tutorials/javadoc/&amp;sa=D&amp;ust=1468683122035000&amp;usg=AFQjCNEp1WzHJ3s4Wg2UxqdSoiw20VDGHQ">Javadoc format</a> to write these documentation comments on both iOS and Android. The Javadoc format places the one sentence explanation of the method within a set of multi-line comment tags (/* */) and optionally includes a description of the method’s parameters, returns and throws. We don’t use comments in many other places. Our code is written to be readable and self explanatory so we only include inline comments as a last resort when the code can’t be made self explanatory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/0*gdkPvgzp8MjzaMAi." /></figure><p>We encourage logging any errors that occur at runtime but we don’t recommend committing developmental or debug logging to the project as it needlessly clutters up the console output. Instead, we put debug<a href="https://www.google.com/url?q=http://furbo.org/2013/04/11/logging-with-xcode-breakpoints/&amp;sa=D&amp;ust=1468683122036000&amp;usg=AFQjCNFSOLFJs5gacmbGXrxMPucQDR6Z0Q"> logging in breakpoints</a> so that it’s easy to enable and disable and is <a href="https://www.google.com/url?q=http://developer.android.com/tools/debugging/debugging-studio.html%23breakPoints&amp;sa=D&amp;ust=1468683122037000&amp;usg=AFQjCNGBDh6Hq9_oSGZG_KtCtwAf-sD_hw">kept in the IDE</a> instead of in the source code. We write variable, property and method names in CamelCase with only the first letter of each word being capitalized. This even applies to acronyms. We prefer including a LICENSE.md in the project over including a copyright notice in every file because starting every file with a copyright notice wastes screen space and gets in the way of the code. We prefix project specific classes with the project’s initials but use the prefix JRM for classes that are used in multiple projects.</p><p><strong>XML layouts and image assets</strong></p><p>We keep XML layout files and image assets in our project repositories right next to the source code. On iOS these XML layout files are called Storyboards and they contain a Scene for each screen. Scenes are connected to each other by segues and sometimes embedded in other Scenes. We use <a href="https://www.google.com/url?q=https://developer.apple.com/xcode/interface-builder/&amp;sa=D&amp;ust=1468683122039000&amp;usg=AFQjCNGYyD3VWla_RtFxckKYTPpRE0F_Jg">Interface Builder</a> to add elements to Scenes and to modify the AutoLayout constraints on elements which determine their size and position. On iOS we only edit the raw XML if there is a merge conflict that Interface Builder can’t solve. XML layouts are a lot simpler on Android because they only represent a single activity or fragment in each file and use syntax which is concise and human readable. Android XML layouts can be edited using a visual “Design view” or a XML “Text view.”</p><p>iOS and Android apps are commonly deployed to devices with a wide variety of display pixel densities usually ranging from 160 dpi to 480 dpi. Presenting sharp graphics on the many device displays that exist in this range requires exporting image assets in three different pixel densities. The lower density called Non-Retina on iOS and mdpi on Android is about 160dpi. The middle density called Retina on iOS and xhdpi on Android is about 320dpi and the higher density called Retina HD on iOS and xxhdpi on Android is about 480dpi.</p><p>Assets exported at the middle pixel density have dimensions twice as large as the lower density and assets exported at the higher density have dimensions three times as large as the lower density. We use density independent dimensions in code to abstract away the pixel density of the specific device display and let the iOS and Android operating systems use the asset corresponding to the device’s display density. These density independent dimensions are called points on iOS and dp on Android.</p><p>These simple few coding style patterns and layout and asset guidelines lead us to create easy to read code, easy to reference documentation, highly adaptive UI layouts and sharp graphics.</p><h4>Version control</h4><p>Version control is a critical piece of developing code here at Jackrabbit. Due to the variability of clients, our version control protocols remain flexible in order to accommodate the level of involvement of our product owners. In general, we use a <a href="https://www.google.com/url?q=http://nvie.com/posts/a-successful-git-branching-model/&amp;sa=D&amp;ust=1468683122043000&amp;usg=AFQjCNE-Ui-BiueUqBI_YQa5ZvXhC42RSA">Gitflow</a> workflow, a branching strategy for Git repositories that is defined by a dev or develop branch that serves as an integration branch for new features. The master branch serves as the current release branch. This allows the team to finalize and fine-tune the current release branch without conflicting with development of features for the next release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nJU-iJy8TPPcl97l." /></figure><p>When starting a new feature, a developer will branch off the current dev branch, and name it under the protocols defined at the beginning of the project, often feature/&lt;short description&gt; or JRM /or/ &lt;project initials&gt;-&lt;ticket number&gt; (which correlates with a ticket in our agile roadmap or this weeks’ sprint). After it is completed, the feature will enter the peer review stage. Peer review is done in one of two ways:</p><ol><li>A pull request is created to alert team members that the feature is ready for review. A team member will then review the code, make comments directly on the pull request (in Github or Bitbucket) if needed, and then merge the branch to develop when it is ready.</li><li>The developer will alert the team it is ready for peer review inside the agile tool (Trello or Jira) by unassigning it to themselves and putting it in the peer review column. The reviewer will make comments directly in the Git repository hosting service or in the agile tool. When ready, the reviewer will assign the ticket back to the original developer, after which they will make a pull request where the project owner can review.</li></ol><p>If the reviewer recommends changes to the feature they will assign the ticket back to the original developer, which will make the necessary changes and restart the peer review process. In the case where there are multiple developers and features being worked on concurrently, the developer may wish to merge dev into their feature before making a pull request to handle conflicts themselves. After the desired features are merged into dev and thoroughly tested, the branch can then be merged into master and released.</p><h4>Code review and pair programming</h4><p><strong>Code Review</strong></p><p>Code review is the process of examining written source code with the intention of finding possible mistakes the original author might have overlooked in order to improve the quality of the software. Code review is usually performed on a different developer’s code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XeCbigN6uSxIhm11." /></figure><p>Engineers at Jackrabbit always review our teammates’ code to ensure the changes meet the acceptance criteria and that the code maintains readability and correctness. Code reviews are also the best way to share programming approaches and to learn from each other’s work. Our code reviews consist of the following steps:</p><ol><li>Verify that the implementation meets the documented requirements.</li><li>Run all automated tests to ensure they still pass.</li><li>Review code quality. Verify that code meets our coding style guidelines, check for bugs, check for unnecessary logging, check that complex code has been refactored, check that method headers are documented with parameter and return descriptions.</li><li>Review code architecture. Check that the code exposes as little as possible in public interfaces, reduces the scope of variables and declares methods as class methods if their implementation doesn’t depend on instance state.</li></ol><h4>Pair programming</h4><p>Pair programming is an approach to development and debugging that consists of two engineers discussing the functionality of a code base while both parties are looking at the same screen. Pair programing sometimes speeds up the process of code review by allowing real time feedback and discussions between engineers. It can also enable an engineer to solve their own issue just by vocalizing their assumptions and understanding of the issue.</p><p>The way we do peer programming at Jackrabbit Mobile is simply pulling in another engineer whenever we face a problem or when we are stuck on a piece of code. When teammates aren’t in the room we use <a href="https://www.google.com/url?q=https://screenhero.com/&amp;sa=D&amp;ust=1468683122054000&amp;usg=AFQjCNHPl1JmC_T0uHIbJbNUWoOXI6gNXg">Screenhero</a> which allows us to see and interact with each other’s screen remotely.</p><h4>Automated and manual testing</h4><p><strong>Unit and UI Testing on Android</strong></p><p>We use separate modules in our code structure on Android to store our unit and UI tests. This allows us to mirror our package structure in the test modules and keep all of our test specific classes separated from the main application code.</p><p>We use the 3rd party <a href="https://www.google.com/url?q=https://github.com/robolectric/robolectric&amp;sa=D&amp;ust=1468683122056000&amp;usg=AFQjCNEQXwhs4XD8Ow93q-YwkdcA8oPhxA">Robolectric</a> library to help us unit test our code on Android. Robolectric is a unit test framework that allows us to access the Android SDK without running our tests on a phone or emulator. Robolectric handles inflation of views, resource loading, and other necessary actions that are implemented in native C code on Android devices. Tests can also run on Continuous Integration environments on a regular JVM without an emulator.</p><p>Google provides the <a href="https://www.google.com/url?q=https://google.github.io/android-testing-support-library/docs/espresso/index.html&amp;sa=D&amp;ust=1468683122057000&amp;usg=AFQjCNHmWCkbO6oejwZV0_xsZjWn-a0aiQ">Espresso</a> library to help create automated UI tests on Android. With Espresso we focus on writing concise, reliable Android UI tests that mimic how a user would interact with our apps. We focus on testing state expectations, interactions, and assertions clearly without the distraction of boilerplate content or custom infrastructure. Espresso does require an emulator or device to run its tests.</p><p><strong>Unit and UI Testing on iOS</strong></p><p>The premise of unit testing is to create environments that exercise different types of behavior in the app. For iOS we use Xcode’s XCTests. A unit of code should represent a minimally testable component of code to ensure that there are no regressions as the project changes. Tests should run quickly, consume no resources, and use mock objects or responses (using OHHTTP). We ensure that all network calls, data controllers, and view models have unit tests and use Xcode’s computation to ensure we reach at least 75% coverage of a class. If it is difficult to reach that goal, we consider rewriting the class to ensure better maintainability. Testing view controllers is avoided. If something in a view controller needs to be tested, the developer should consider refactoring the code. We group our tests by file to represent the view controller that a data controller and view model target. We may also use performance testing to measure execution time for appropriate projects.</p><p>UI testing is different from functional and performance tests in that it ensures the look of the app behaves and changes how you expect it to as a user interacts with it. We use Xcode’s built in UI testing API. With Xcode 7, you can write most of the testing code by “recording” your interaction with the app. We can then edit the generated code by inserting XCTAsserts like normal unit testing to verify the app looks how you expect it to. Just like unit testing, tests should be simple, deterministic, and fail or pass consistently. They should be written as if the user is interacting with the app. Presenting and dismissing view controllers is vital to UI testing, however, the speed at which a test runner does so can often result in error messages. You can get around these errors by presenting each view controller in its own window.</p><p><strong>Test Coverage</strong></p><p>We believe that the majority of our code should be covered by tests. We do not look to hit a certain percentage level of our code to be tested, but want to make sure every area of the codebase is equally represented in our tests.</p><p><strong>Manual Acceptance and Regression Testing</strong></p><p>At Jackrabbit we believe our code should constantly be manually tested and looked at by human eyes. Each ticket requires a functional test by someone who did not work on the code. Within 24 hours of code review there will always be a functional or manual test before each ticket can be marked as done. That is typically completed by a project manager, product owner, or dedicated QA.</p><h4>Platforms, distribution and continuous integration</h4><p><strong>Client-side Platforms</strong></p><p>We develop native mobile applications for a large range of platforms including <a href="https://www.google.com/url?q=https://www.android.com/&amp;sa=D&amp;ust=1468683122063000&amp;usg=AFQjCNG-QFsI1g52zLDOKKRrK1gE4PaOGA">Android</a> for smartphones and tablets, <a href="https://www.google.com/url?q=http://www.apple.com/ios/&amp;sa=D&amp;ust=1468683122064000&amp;usg=AFQjCNG20-07tlWqPLwHKjtu6uJ0YmKmsw">iOS</a> for iPhone, iPod and iPad, <a href="https://www.google.com/url?q=https://developer.apple.com/tvos/&amp;sa=D&amp;ust=1468683122064000&amp;usg=AFQjCNGGyoinbPA_Sl4oAOXj00BtoipVuw">tvOS</a> and <a href="https://www.google.com/url?q=https://developer.apple.com/watchos/&amp;sa=D&amp;ust=1468683122065000&amp;usg=AFQjCNF32DM0JLj-GlJ0xWVrzW4x3Fq5ng">watchOS</a> for Apple TV and Apple Watch and <a href="https://www.google.com/url?q=https://angularjs.org&amp;sa=D&amp;ust=1468683122065000&amp;usg=AFQjCNExJdThNORJKeaARqdj8RG8MdEvDg">AngularJS</a> for web apps.</p><p><strong>Server and Database solutions</strong></p><p>We also develop server side solutions and work with our clients’ existing servers and databases.</p><p>For clients who want to develop an app that requires popular standard backend functionality (database, push notifications, authentication etc.) but lack a server solution of their own, we most commonly use <a href="https://www.google.com/url?q=https://github.com/ParsePlatform/parse-server&amp;sa=D&amp;ust=1468683122067000&amp;usg=AFQjCNF-I2DU9h-zc-Zvp2T5fiRf42v7YQ">Parse Server</a>. Parse Server simplifies many aspects of developing a backend for mobile apps, including the API server, push notifications and event driven business logic. We host our Parser Server instances on <a href="https://www.google.com/url?q=https://devcenter.heroku.com/articles/dynos%23dynos&amp;sa=D&amp;ust=1468683122068000&amp;usg=AFQjCNEekQJfYKCwiqlsK9pMQlhQjRklXA">Heroku Dynos</a>, and use <a href="https://www.google.com/url?q=https://aws.amazon.com/s3/&amp;sa=D&amp;ust=1468683122068000&amp;usg=AFQjCNEAHVLiEikwh2_N-907QRfyV3-DBA">S3</a> buckets for file storage and distribution.</p><p>Unlike AWS, Heroku is free for the first dyno (512MB RAM, 1GB swap space, 100MB storage space, and comparable computing power to an AWS micro/small EC2 instance). However, dynos are strictly for application purposes — many of the add-ons and third party services used to support databases and background works may require an extra cost. For larger applications AWS is less expensive in the long-run. For smaller applications, Heroku is cheaper and simpler to get up and running.</p><p><strong>Distribution and Continuous Integration</strong></p><p>We often set up a continuous integration server to automatically run automated UI and unit tests as well as automated checks at the pull request stage. We can also setup additional automations to upload test builds to HockeyApp for testing, handle code signing, take and upload screenshots and submit releases. We use <a href="https://www.google.com/url?q=https://www.bitrise.io/&amp;sa=D&amp;ust=1468683122070000&amp;usg=AFQjCNF2FUnoYrWcsyGYa-w7IQrDakK5NQ">Bitrise</a> to run continuous integration in the cloud and <a href="https://www.google.com/url?q=https://jenkins.io&amp;sa=D&amp;ust=1468683122071000&amp;usg=AFQjCNGDeYbx3bNHe4jAT4NqHjuFyvPfXg">Jenkins</a> to run it in house. We use <a href="https://www.google.com/url?q=https://www.hockeyapp.net/features&amp;sa=D&amp;ust=1468683122071000&amp;usg=AFQjCNHX-I3Uai1F8SoB_1yffvG_Tv5osQ">HockeyApp</a> or <a href="https://www.google.com/url?q=http://fabric.io/&amp;sa=D&amp;ust=1468683122072000&amp;usg=AFQjCNE79uR_a-0vmQ6b7KHCZpVNM-SVjQ">Fabric</a> for distribution as these allow us to distribute Android and iOS builds without any approval wait time.</p><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><h4>Thanks!</h4><p>We really hope you enjoyed this Playbook.</p><p>If you’d like to build some awesome technology with us, or have a question or comment, we’d love to hear from you at <a href="/service/mailto:hello@jackrabbitmobile.com">hello@jackrabbitmobile.com</a></p><blockquote>A downloadable PDF of the Playbook is available at: <a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></blockquote><ul><li><strong>The Jackrabbit Mobile Team</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBai0KsRlWRySH1C." /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16cd0871dbf0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobile-growth/playbook-engineering-16cd0871dbf0">Playbook: Engineering</a> was originally published in <a href="https://medium.com/mobile-growth">Mobile Growth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Playbook: Design]]></title>
            <link>https://medium.com/sketch-app-sources/playbook-design-86f34e964e9b?source=rss-19f956058d96------2</link>
            <guid isPermaLink="false">https://medium.com/p/86f34e964e9b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Jackrabbit Mobile]]></dc:creator>
            <pubDate>Sun, 17 Jul 2016 13:54:16 GMT</pubDate>
            <atom:updated>2016-07-27T15:07:32.029Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jackrabbit Mobile Playbook: Design</h3><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O6VzyYgvFW83Iha3." /></figure><h3>Design</h3><h4>Typical Design Projects</h4><ul><li>Product Strategy Sprints</li><li>Updating an outdated interface to modern standards, such as flat or material design.</li><li>Testing business assumptions or designs with a user session</li><li>Translating an interface from iOS to Android</li><li>Crafting the user onboarding experience</li><li>Performing a competitive analysis</li><li>Wireframes and mockups</li></ul><h4>Usability Design</h4><p>Usability is an attribute that determines a product’s ease of use. It is defined by five quality components as explained by <a href="https://www.google.com/url?q=https://www.nngroup.com/articles/author/jakob-nielsen/&amp;sa=D&amp;ust=1468683121941000&amp;usg=AFQjCNGOcWxgY9m6riXyw9F2MEknUI1-zA">Jakob Nielson</a> :</p><ul><li>Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?</li><li>Efficiency: Once users have learned the design, how quickly can they perform tasks?</li><li>Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?</li><li>Errors: How many <a href="https://www.google.com/url?q=https://www.nngroup.com/articles/slips/&amp;sa=D&amp;ust=1468683121943000&amp;usg=AFQjCNHGbyN2Ppxz0pB_WnhAkSV8tfymYw">errors</a> do users make, how severe are these errors, and how easily can they recover from the errors?</li><li>Satisfaction: How pleasant is it to use the design</li></ul><p>Although usability affects the user experience, they are not the same thing. User experience is about emotional connections to a product while usability is about removing roadblocks in order to make a product intuitive and easy to use. This is important because when users encounter a difficulty in your website or app, they tend to leave and possibly find an alternative to your product and service. On average, it’s been found that if you spend 10% of your product’s budget on usability, <a href="https://www.google.com/url?q=https://www.nngroup.com/articles/usability-roi-declining-but-still-strong/&amp;sa=D&amp;ust=1468683121945000&amp;usg=AFQjCNGPChJe89X5seu15gDFBzOW964ZpQ">the desired quality metrics tend to double.</a> This includes conversion rates, traffic numbers, user performance, and target feature usage.</p><p>So how do you improve usability? At Jackrabbit, we find that the most useful method is user testing. This involves bringing in representative users, asking them to execute certain product based tasks with your design, and observing their successes and failures with the user interface. Letting them think aloud while performing these tasks is crucial to getting productive feedback. For a more in depth look at how we conduct these tests, read our user testing section.</p><p>It is recommended that you focus on usability through every step of the design process. Start with low fidelity prototypes and keep iterating after each group of testing. Don’t put off user testing until you have a finished and fully implemented design. Doing so will limit how many usability problems you can fix before launch so start as early as you can. In fact, testing a competitor’s product before you begin designing can prove to be beneficial as it will help you understand what other products do right or wrong. This will prevent you from making any of the mistakes that competitors have made, resulting in saved time and money.</p><h4>User Research</h4><p>User research has two parts: gathering data, and synthesizing that data in order to improve usability. The data being collected varies from each project and can include something as simple as “is this button’s action clear to the users”, to more complicated as “does this features entire flow make sense to the user”. At the start of the project, design research is focused on learning about project requirements from stakeholders, and learning about the needs and goals of the end users.</p><p>We do user research because we care about not only creating apps that are visually stunning, but that are also functional and appropriately meet all of the users’ needs. Building an app is just the beginning, but in order for it to be 100% successful you actually have to test what you made and validate its features. Research is needed to analyze where your users are having difficulties and uncover new opportunities for features and conversions. This helps to ensure that we have created a product that users are actually going to want to use and that we have it designed in a way that makes them want to use it. Ultimately, doing research will save your organization valuable time and money. It removes assumptions and allows for mistakes to be caught early on. The later you discover that your assumptions are wrong, the more money it will cost you to fix it.</p><h4>User Testing</h4><p>Our user testing process consists of 6 steps:</p><p><strong>1. Planning</strong> what we’re going to test, during which we are trying to:</p><p>Define the Target Audience which are the assumed potential users and our key demographic.</p><p>Define Key Points or main use flows for us to test, by:</p><ol><li>Collecting issues and presenting them as goals</li><li>Prioritizing the goals</li><li>Rewriting the goals as user-specific questions to be answered or information to be gathered</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*peds1ds_n8Grroi0." /><figcaption>User Testing Planning Example</figcaption></figure><p><strong>2. Recruiting</strong> individuals to come and participate in the study through various ways:</p><p>Craigslist Ad when our target audience is broad enough that we can pull participants from the general public, we post an ad on Craigslist that contains a survey to be completed. The surveycontains a few open ended questions that are geared towards what we are testing.</p><p>Social Media, Google, and Lists of Pre-Qualified Users are used when the target audience is much more specific and pulling from the general public wouldn’t provide the necessary results.</p><p><strong>3. Screening Participants</strong> for the study based on the results from the survey.</p><p>The goal during the screening process is to select 5 individuals who best fit the study’s needs. The reasoning behind selecting only 5 is that it has been shown that feedback from 5 individuals will provide a range of answers that are still narrow enough for commonalities to be found, as well as being time sensitive. For more information, visit <a href="https://www.google.com/url?q=https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/&amp;sa=D&amp;ust=1468683121958000&amp;usg=AFQjCNG84i1z9oSEKFvAg55y29YqTLyodw">here</a>.</p><p><strong>4. Scheduling User Sessions</strong></p><p>User sessions are usually scheduled to all be conducted in a day and typically last 30 minutes each. Client participation is highly recommended. It cuts back on any disconnect during the presentation of findings and it keeps everyone in the loop of what is going on and what is being said by potential users.</p><p><strong>5. Running a User Session</strong> and performing the interview has numerous components to it:</p><p>The agenda may vary depending on what is being tested during, but generally consists of introduction and getting to know our participant. Then we ask a series of questions which reflect our key points and typically have the participant interact with a prototype of what we are testing.</p><p>We’ll likely record either a video, audio, or screen recording of the interview so that we can focus on performing the interview and have the data to review afterwards.</p><p>We have a <a href="https://www.google.com/url?q=https://docs.google.com/document/d/1x1nDQHMh3Lq9R6WrN_LIOVyOZClRnaoC0Lc8MJR264E/edit?usp%3Dsharing&amp;sa=D&amp;ust=1468683121962000&amp;usg=AFQjCNEyyjYEFaQWoja8xqEZiXP25PiT7g">Non Disclosure Agreement (NDA)</a> to ensure that whatever is discussed during the session will be kept confidential. We write a script in advance and it contains a series of open ended questions that were curated by the team to address the key points established during the planning phase.</p><p>Our typical roles are Moderator, Transcriber and Observer/Equipment facilitator. The moderator is in charge of conducting the interview by asking all of the questions and will be the main person engaging with the user. The transcriber isin charge of recording all of the user’s answers during the session. And the Observer/Equipment Facilitator ensure equipment is set up and running correctly and observing quietly during the session.</p><p>“Hallway” Testing is an alternative option to having in-office user sessions that bypasses recruiting and scheduling appointments with users. Typically these forms of user sessions take place out in the field at public places like coffee shops, libraries, campuses, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*00uk4w0vR8xuBqQp." /><figcaption>What a typical user session can look like</figcaption></figure><p><strong>6. Analyzing Data and Presenting Findings</strong> through various approaches:</p><p>Lean Analysis the team will briefly discuss and break down the key points that came up while testing (new opportunities, unexpected pains, confirmed predictions, etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bv6Y69SJvAenI5uJ." /><figcaption>Whiteboards! And a Lean Analysis</figcaption></figure><p><strong>Data Analysis</strong> the quotes gathered during the interviews are broken down and coded according to specific points:</p><ul><li>Doing — behaviors and actions performed</li><li>Feeling — emotional reactions and attitudes</li><li>Thinking -describes the mindset and considerations/thoughts</li><li>Pain — decision points with negative outcomes or hindrances for product</li><li>Opportunity — decision points with positive outcomes or possibilities for product</li></ul><p><strong>Experience Map</strong> using <a href="https://www.google.com/url?q=http://mural.ly&amp;sa=D&amp;ust=1468683121969000&amp;usg=AFQjCNFzmDKPwf3kkfroXpaGps-4jA27eg">mural.ly</a>, this involves taking the breakdown from the data analysis and grouping together quotes that fit within a similar theme to form a potential user flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/0*FZLJA8pRnQ3PnFzJ." /><figcaption>Experience Map</figcaption></figure><p><strong>Journey Map</strong> is used to present the findings through a narrative story of a persona created to reflect a potential user and their journey based on the data collected from the testings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S1pYjOGgbxeFDj28." /><figcaption>Journey M</figcaption></figure><h4>Prototyping</h4><p>Prototyping is a valuable tool we use to help communicate and test ideas. One of the benefits of testing with prototypes is that users can be more engaged when talking about the concept we are testing. As the value proposition is further understood through the design process, we are able to refine prototypes through fast iterations in order to avoid developing the wrong solutions early on. Learning from failures can be a valuable thing, but failing on a large scale can ultimately result in the death of your product. Prototyping enables us to learn at earlier stages to prevent large scale failure, ensuring that we build the best product from the get go.</p><p>A prototype is any simulation of the final product. It is important to keep in mind that a prototype will not always be high fidelity or look like the final product. It may be a series of paper sketches, a click-through of a series of mockups, or in some cases even a physical artifact.</p><p><strong>Paper</strong></p><p>Paper prototyping is a quick and easy method to test your initial ideas. It involves sketching your product with a pencil on paper. These sketches may display various screen states. Paper prototyping allows you to iterate at a fast rate. Based on users’ feedback and expectations, you can erase and make changes accordingly during the testing process. Paper prototyping is the most flexible way of testing ideas quickly but there is a downside. It is not as immersive as other prototypes, leaving a lot up to the users’ imaginations.</p><p><strong>Click-through</strong></p><p>Click-through prototypes are our favorite artifacts to test with. These are usually a series of static screens linked together with clickable hotspots. These are more immersive and closer to the final product than paper prototypes. Our favorite workflow for creating these involves designing mockups for each screen and/or screen state in <a href="https://www.google.com/url?q=https://www.sketchapp.com/&amp;sa=D&amp;ust=1468683121977000&amp;usg=AFQjCNEqMs15NiTK263vXkt7hui3TO5rZw">sketch</a>, exporting those, and uploading them to <a href="https://www.google.com/url?q=https://marvelapp.com/&amp;sa=D&amp;ust=1468683121978000&amp;usg=AFQjCNFgalrGWQRPPChYPqlgZQAJjXZp0g">marvelapp</a>.</p><p><strong>Physical Artifact</strong></p><p>Certain projects can sometimes call for using different methods of prototyping. Sometimes we design products that aren’t exclusive to a digital medium and we need to test how an app may affect a physical object or vice versa.</p><h4>Visual Design</h4><p>Visual design is the strategic use of imagery, color, shapes, typography, and form to improve user engagement and brand trust. Successful visual design isn’t just about making things look pretty, it’s about communicating the purpose of the product and the utility of its interface. Visual design plays an important role in boosting user confidence and satisfaction by helping them get their jobs done quickly. For example, if an interface is over styled, a lot of important information and CTA’s can become obscured. The most important aspects of visual design are those that help a user quickly scan information, take the correct actions, and know where they are in the product.</p><p>For a quick crash course on some basic visual design principles check these out:</p><ul><li><a href="http://learndesignprinciples.com/index.html">http://learndesignprinciples.com/index.html</a></li><li><a href="https://www.smashingmagazine.com/2014/03/design-principles-visual-perception-and-the-principles-of-gestalt/">https://www.smashingmagazine.com/2014/03/design-principles-visual-perception-and-the-principles-of-gestalt/</a></li></ul><p>Visual design is also about first impressions. The tone of what the product is and represents in the eyes of a user should be informed by user and market research. Once you have more insight into who your target users are, <a href="https://www.google.com/url?q=http://mur.al/YA4QAOlr&amp;sa=D&amp;ust=1468683121983000&amp;usg=AFQjCNFlBlOvcbGti568Go6Vz__7b-DpLA">moodboards</a> can be an effective tool of honing in on a visual design language. A moodboard is a collection of visual inspirations that you think are effective in communicating similar tones and themes that you are trying to. This compilation of visuals can help spark discussions on how other designers have both succeeded and failed in communicating similar themes.</p><h4><a href="https://medium.com/@teamjackrabbit/playbook-65a0d42ef9cf">← Back to the Playbook Table of Contents</a></h4><h4>Thanks!</h4><p>We really hope you enjoyed this Playbook.</p><p>If you’d like to build some awesome technology with us, or have a question or comment, we’d love to hear from you at <a href="/service/mailto:hello@jackrabbitmobile.com">hello@jackrabbitmobile.com</a></p><blockquote>A downloadable PDF of the Playbook is available at: <a href="http://www.jackrabbitmobile.com/playbook/">http://www.jackrabbitmobile.com/playbook/</a></blockquote><ul><li><strong>The Jackrabbit Mobile Team</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBai0KsRlWRySH1C." /></figure><p><em>If you found this useful and are excited by building awesome technology, please hit the recommend button below!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86f34e964e9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sketch-app-sources/playbook-design-86f34e964e9b">Playbook: Design</a> was originally published in <a href="https://medium.com/sketch-app-sources">Design + Sketch</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>