<?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[Chop Technologies - Medium]]></title>
        <description><![CDATA[Instant, contextual mobile commerce - Medium]]></description>
        <link>https://medium.com/chop-technologies?source=rss----ebfd2ea5ab2e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Chop Technologies - Medium</title>
            <link>https://medium.com/chop-technologies?source=rss----ebfd2ea5ab2e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:46:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/chop-technologies" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How Fast Casual Restaurants are Changing How We Eat]]></title>
            <link>https://medium.com/chop-technologies/how-fast-casual-restaurants-are-changing-how-we-eat-c9e78a461a24?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/c9e78a461a24</guid>
            <category><![CDATA[mobile-commerce]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[food]]></category>
            <category><![CDATA[commerce]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Thu, 29 Jun 2017 16:41:02 GMT</pubDate>
            <atom:updated>2017-06-29T16:41:01.508Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Katie Crowley</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SnOdPjQ5cPjV_4iE.jpg" /></figure><p>Fast casual restaurants: the mid-point between takeout and sit down dining, are facing a renaissance of sorts. Chains like <a href="https://www.chipotle.com/">Chipotle</a>, <a href="https://www.panerabread.com/en-us/home.html">Panera</a>, and<a href="https://www.eatsa.com/"> Eatsa</a> are adapting to a new kind of a patron — the kind who likes good food, on a tight schedule. So, how is this new trend in dining changing the eating game? Keep reading to find out.</p><p><strong>More Efficient Restaurants, For More Efficient Dining</strong></p><figure><img alt="How Fast Casual Restaurants are Changing How We Eat" src="https://cdn-images-1.medium.com/max/1024/0*Z1mKaCFmGru0hjz9.jpg" /></figure><p>Fast casual restaurants are proving that great food doesn’t have to be sacrificed in the name of efficiency. With fewer seats, no wait staff, and lower overhead in general, fast casual eateries are saving money on the front end so they can invest in higher quality products on the back end. That means high quality ingredients, creative recipes, and essentially gourmet food faster, and at a lower price point.</p><p>Fast casual restaurants are also more efficient on the consumer-side as well. According to a recent<a href="http://officeteam.rhi.mediaroom.com/lunchbreaks"> survey</a>, nearly half of workers have 30 minutes or less for lunch, that means they’re prioritizing fast meals that are nearby. To meet this growing need, many fast casual restaurants provide mobile pay and ordering, delivery, and pickup options.</p><p><strong>Better Customer Service</strong></p><figure><img alt="How Fast Casual Restaurants are Changing How We Eat" src="https://cdn-images-1.medium.com/max/1024/0*DUf8MpQMMcfLD65-.jpg" /></figure><p>Again, because fast casual restaurants are forgoing many of the expenses that are traditionally found with sit down restaurants, they can invest in better customer service and technology. Companies like Eatsa provide mobile platforms that allow for effortless customization, and quick pay options.</p><p>Customer service is a critical selling point for fast casual chains that hope to stand out. Because they function at a higher price point than their fast food counterparts (think McDonalds, Wendy’s etc.), customers expect a bigger bang for their buck. So, aside from mobile ordering, restaurants like Panera and Starbucks offer loyalty programs, allow for custom orders, and provide problem-solving steps if a product is sold out, or an order is filled incorrectly online.</p><p>The fast casual dining scene is dedicated to embracing technology as a way to constantly improve customer service. Now, personal preferences can be remembered, regular orders can be purchased again with a single click, and you can scout short wait times before committing to a restaurant. Technology, simply put, is transforming the way restaurants serve customers.</p><p><strong>A Change in Space</strong></p><figure><img alt="How Fast Casual Restaurants are Changing How We Eat" src="https://cdn-images-1.medium.com/max/1024/0*2pVUC9_t98XWAoq0.jpg" /></figure><p>The countrywide boom in fast casual eating has sparked a rise in small spaces zoned for restaurants. In turn, this means rents are increasing, and restaurants are competing against numerous eateries for the same space. So, instead, many fast casual restaurants are adapting by opting out of seated spaces all together.</p><p>Think food trucks, ordering windows, counter service spots, or online-only restaurants. In fact, this trend has become so popular in San Francisco alone, that you could spend a week eating out at small-space restaurants. Here’s a good <a href="https://sf.eater.com/maps/best-quick-service-quality-food-restaurants-san-francisco">list</a> of some spots you should try if you’re in the area.</p><p>Simply put, the fast casual dining scene is adapting to the eaters of today. This new chain in food service fits within the average American’s busy life, and meets higher expectations of efficiency and customer service.</p><p>What are your favorite fast casual places? Let us know by commenting below or on our <a href="https://twitter.com/chopnow">Twitter</a> or <a href="https://www.facebook.com/thechopapp/?modal=composer&amp;notif_t=page_fan_growth_drop&amp;notif_id=1498068822948912">Facebook</a>. As always, stay up to date with all Chop news by following us here or on any of the social media outlets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9e78a461a24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/how-fast-casual-restaurants-are-changing-how-we-eat-c9e78a461a24">How Fast Casual Restaurants are Changing How We Eat</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top Three Dining Trends of 2017]]></title>
            <link>https://medium.com/chop-technologies/top-three-dining-trends-of-2017-895acc0fb48b?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/895acc0fb48b</guid>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Fri, 16 Jun 2017 15:21:01 GMT</pubDate>
            <atom:updated>2017-06-16T15:21:01.210Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Katie Crowley</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o-odyEG9wdVByl1v.jpg" /></figure><p>Baum + Whiteman, the international food and restaurant consultancy just released their annual food trends <a href="http://www.baumwhiteman.com/2017TRENDS.pdf">list</a>. For 2017, Baum + Whiteman predict 13 hot food and beverage trends taking over the restaurant scene, with about 30 or so additional trends squeezed in, in the form of innocuous bullet points. So what does the famed list have in store for the international food scene? We’re giving you a basic rundown with the top five dining trends of 2017.</p><h4><strong>The Uberization of Food</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QSBvvAQWzAPNF7pW.jpg" /></figure><p>Not surprisingly, Baum + Whiteman predicts a continued deluge of tech-related food companies in 2017, but it’s more than just online ordering. Many restaurants are forgoing the standard seating arrangement all together. Indie restaurateurs and heavyweights alike are opening commercial kitchens in rough, low-rent locations staffed by professional cooks. But, these new chains have a catch: no seats. They are delivery only locations, providing high-end food to customers who want to stay in.</p><p><a href="https://momofuku.com/">Momofuko’s</a> David Chang now has two delivery-only locations in New York, and <a href="https://www.fastcompany.com/3064075/hold-the-storefront-how-delivery-only-ghost-restaurants-are-changing-take-out">Green Summit</a> in New York, has eight phantom restaurants, all fed from the same two kitchens. Meanwhile, more and more companies are partnering with delivery services like Ubereats to provide what people really want: great food without a line.</p><p>As far as tech-related food trends go, Baum + Whiteman also mention AirBnB services, where diners can enjoy a meal in a home cook’s dining room, as well as drones, and the ever present meal delivery boxes like <a href="https://www.blueapron.com/?cvosrc=search-paid.google.brand30&amp;gclid=CM_M9dnsutQCFYplfgodZmoOJg&amp;utm_campaign=brand30&amp;utm_medium=search-paid&amp;utm_source=google">Blue Apron</a> and <a href="https://greenchef.com/home">Green Chef.</a> Needless to say, tech is a trend in more ways than one.</p><h4><strong>Breakfast All Day</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dYNt8GEMemcyraNB.jpg" /></figure><p>Apparently, when <a href="https://www.mcdonalds.com/us/en-us/full-menu/breakfast.html">McDonald’s</a> started serving breakfast all day the world took notice, and their competitors upped their game. It may have started with McDonalds, but the all breakfast all day trend, can be found in more than just the fast casual chains.</p><p>Breakfast sandwiches are having a moment, as millennials are on the lookout for high-protein and portable options. Smaller chains and independents are creating heartier versions of our favorite breakfast foods that qualify as round-the-clock meals. Baum + Whiteman also noted a shift away from standard breakfast textures: fluffy eggs, creamy French toast, light pancakes, to more substantial options: fried chicken, crispy chorizo, coarse-whole-grain cereal, and of course avocado smeared on toasted baguettes of every order.</p><h4><strong>Vegetables and Bowls</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tUKe17-3pZaiw_N_.jpg" /></figure><p>In a sentence Baum + Whiteman are calling vegetables the new comfort food. For many top restaurants meat has become a garnish or side, and vegetables are taking top billing. Call it a growing consideration for the dangers of the meat packing industry, or a millennial resolution to finally heed their parent’s advice and eat their vegetables. Whatever the reasoning, there’s no doubt that vegetables are on the rise.</p><p>In fact, vegetables are so on-trend that formerly vegetable free fares, are being re-imagined to include more hearty greens. Pizza is now being made from cauliflower, chickpeas are taking the place of meat protein, beets are transformed into chorizo. And faux-meat foods are on the rise as well, with burgers made entirely from vegetables, even carrots disguised carefully as a rack-of-ribs.</p><p>Another trend to boot is an on-going adoration of any food item in a bowl: ramen, smoothies, poke, vegetables. With a dismissal of carb-heavy foods like sandwiches, this new generation of diners is looking for whole grain alternatives that just happen to be best served in bowls. Baum + Whiteman also suggest the rise of the bowl is in a large part due to our sudden obsession with ramen. In any case, vegetable bowls delivered via an app seem to be, in a nutshell, the 2017 food trend.</p><p>What food trends do you hope stick around or go away? Let us know by commenting below. As always, stay up to date with all Chop news by following us here or on any of the social media outlets. For questions, comments, or concerns feel free to reach out via our <a href="https://www.facebook.com/thechopapp">Facebook</a> or <a href="https://twitter.com/chopnow">Twitter.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=895acc0fb48b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/top-three-dining-trends-of-2017-895acc0fb48b">Top Three Dining Trends of 2017</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Mobile Commerce is Missing]]></title>
            <link>https://medium.com/chop-technologies/what-mobile-commerce-is-missing-b455ba7509d3?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/b455ba7509d3</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-commerce]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 15:13:53 GMT</pubDate>
            <atom:updated>2017-06-08T15:13:52.735Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Katie Crowley</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qF7Qaz-h5-QXgPZZ.jpg" /></figure><p>Mobile commerce is a booming industry. In fact a recent<a href="https://www.forbes.com/sites/theyec/2016/05/27/mobile-commerce-trends-for-the-second-half-of-2016/#396b15f7200a"> article </a>by Forbes predicts that mobile commerce will account for 50% of all digital commerce in the United States by the end of 2017. In our previous post, we mentioned the top five mobile commerce apps, and while they’re doing a lot right, there are still a few things missing from mobile commerce.</p><p>Take a look:</p><h4><strong>A Connection Between Mobile and Desktop</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/0*XCQ3GyMLCJZoQVGq.png" /><figcaption>Information courtesy of Business Insider</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/0*z9EXUo9yaefe4EZv.png" /><figcaption>Information courtesy of <a href="http://www.businessinsider.com/mobile-commerce-shopping-trends-stats-2016-10">Business Insider</a></figcaption></figure><p>According to a recent Business Insider<a href="http://www.businessinsider.com/mobile-commerce-shopping-trends-stats-2016-10"> article,</a> companies should be urged to provide both desktop and mobile options seeing as adults spend only 15% of their money on mobile, and a whopping 85% on desktop.</p><p>There are a few reasons why mobile commerce remains at such a low adoption rate. One is ease of payment. Consumers are still hesitant to pay with mobile due to security concerns, and setting up mobile payment will remain moderately difficult until Android and Apple Pay reach more critical iterations. But once consumers get over that hurdle, mobile commerce is a reliable, and efficient service — think Starbucks or Panera.</p><p>Second, most mobile commerce deployment is focused on mobile native apps, and is entirely separate to their desktop experience. That means for the same brand, a user could have a different login, and a different order history on mobile versus desktop. Acquiring users to download a native app is costly, it would be best to provide a more seamless mobile experience that allows users to make their first purchase without downloading the app.</p><p>For example, you can have a mobile web experience that allows users to make their first purchase without logging in, and leverage new web payment options, which are already deeply imbedded online. As the users try new mobile commerce platforms, they’re more likely to download the app, and the app is likely to stay longer on the user’s home screen. This is currently a missing piece in the mobile commerce puzzle. One possible solution is the latest web technology, Progressive Web Apps, which offer a more immersive mobile web experience with the ability to add to the home screen later.</p><h4><strong>Future-proof features</strong></h4><p>Mobile commerce is a burgeoning trend, which means to do it well, you have to anticipate what features will best accommodate the needs of users. Apps like Domino’s, which offer voice ordering, or Chop, which is integrated with Facebook Messenger, give consumers additional options that can fit easily into their day-to-day.</p><p>The key to future-proof features is being thoughtful about each page and process of the application. With Chop, during the initial launch in San Francisco, we found that the high rises in the city provided sporadic connectivity — meaning a customer could be mid-way through an order, pop onto Bart and lose their order. To solve this issue, we redesigned how far a user could get while offline — all the way to the payment page — and offered more informative error messages to better direct the users. Visit our previous post <a href="http://blog.getchop.io/2016/12/14/designing-for-accidental-disconnects-our-first-attempt-at-an-offline-approach/">here</a>, to learn more about how we redesigned for accidental disconnects.</p><h4><strong>Seamless Integration With Brick and Mortar Stores</strong></h4><p>All m-commerce requires backend diligence, whether that’s in site and app maintenance, or more importantly in the employees who fill, ship, and correct all submitted orders. The most prevalent customer complaint we found when it comes to m-commerce, is a disconnect between the physical store and the mobile platform. Customers can place special instructions, but that doesn’t necessarily mean they will be followed.</p><p>Companies are scurrying to deploy mobile commerce options, but are failing to align their new technology with their existing stores. To counteract this, it’s important to teach all employees how to use and interact with any mobile commerce platforms. This can be tricky as retail has such a high turnover rate, but mobile commerce training can be implemented in a similar way as customer service, POS, or security training.. The key is to build a workable guide for mastery over mobile commerce. Improvement should be measurable, just as it would be for any other training involved with retail.</p><p>What do you think mobile commerce is missing? Let us know by commenting below or commenting on our <a href="https://www.facebook.com/thechopapp/">Facebook</a> or <a href="https://twitter.com/chopnow">Twitter.</a> As always, stay up to date with all Chop news by following us here or on any of the social media outlets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b455ba7509d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/what-mobile-commerce-is-missing-b455ba7509d3">What Mobile Commerce is Missing</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Top Five Mobile Commerce Apps]]></title>
            <link>https://medium.com/chop-technologies/the-top-five-mobile-commerce-apps-f70e081bae9b?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f70e081bae9b</guid>
            <category><![CDATA[commerce]]></category>
            <category><![CDATA[mobile-design]]></category>
            <category><![CDATA[retail]]></category>
            <category><![CDATA[mobile-commerce]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Fri, 26 May 2017 15:31:56 GMT</pubDate>
            <atom:updated>2017-05-26T15:22:31.437Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Katie Crowley</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VEFIHYsukAy3PU3G.jpg" /></figure><p>It’s no secret that our world is becoming increasingly connected through technology — that with the swipe of a finger you can find love, order a Taco, and buy limited edition Ray Bans. But, not all apps are created equal. To help you master the world of online ordering we’ve compiled the definitive list of the top five mobile commerce apps. How does your favorite stack up?</p><p>So here they are, the top five mobile commerce apps ranked in order:</p><p><a href="https://itunes.apple.com/us/app/starbucks/id331177714?mt=8"><strong>Starbucks</strong></a><strong> | </strong><a href="https://play.google.com/store/apps/details?id=com.starbucks.mobilecard&amp;hl=en"><strong>Avg Customer Rating: 4.5</strong></a></p><figure><img alt="The Top Five Mobile Commerce Apps" src="https://cdn-images-1.medium.com/max/1024/0*Fge76K19YI2bvFBC.png" /></figure><p><strong>What they do right:</strong></p><p>As of January 2017 <a href="https://www.forbes.com/sites/maggiemcgrath/2017/01/26/starbucks-mobile-orders-grow-but-not-enough-to-lift-q1-sales-above-expectations/#449066e237a1">Forbes</a> reported that the coffee super chain increased their daily active app users to 13 million — effectively showing a 16% increase year after year. In fact the app is so popular that in 2016 mobile ordering and payments represented 7% of Starbuck’s total transactions in the United States.</p><p>Starbucks was early on the scene of mobile ordering, and they prioritize a clean design and friendly user experience. On top of that, they also offer a rewards system that incentivizes users to come back and buy more. Their app was designed for efficiency, and it delivers time saving solutions while staying on-brand.</p><p><strong>Best features:</strong></p><p>-Simplifies complex orders (can order a grande, non-fat, coconut milk, light ice mocha effortlessly).</p><p>-Good offline notifications</p><p><strong>Worst features:</strong></p><p>-Mishaps when connecting multiple gift cards to the app</p><p>-Too many notifications</p><p>-Location-aware can be finicky</p><p><a href="https://itunes.apple.com/us/app/panera-bread/id692365393?mt=8"><strong>Panera</strong></a><strong> | </strong><a href="https://play.google.com/store/apps/details?id=com.starbucks.mobilecard&amp;hl=en"><strong>Avg. Customer Rating: 4.75</strong></a></p><figure><img alt="The Top Five Mobile Commerce Apps" src="https://cdn-images-1.medium.com/max/1024/0*A-uZi2fRRLYMmBAR.png" /></figure><p>Panera recently reported to <a href="http://fortune.com/2016/02/05/panera-digital-orders-growing/">Forbes</a> that their app could exceed $1 billion in annual sales by 2017, with over 20% of orders produced and paid for digitally by the end of 2016. Aside from a remarkably clean design, this location-based app allows for effortless customization, ordering without logging in, and syncs easily to their member rewards program.</p><p>The only drawbacks seem to be an uncommonly small font, a complete freeze on the app the minute you go offline, and some issues integrating the app with their brick-and-mortar stores.</p><p><strong>Best Features:</strong></p><p>-Attached to customer care center</p><p>-Detailed nutrition for every item</p><p>-Allows you to skip the line</p><p><strong>Worst Features:</strong></p><p>-Very tiny font</p><p>-Finicky synchronization with newer iPhone models</p><p>-The app freezes the instant you go offline.</p><p><a href="https://itunes.apple.com/us/app/dominos-pizza-usa/id436491861?mt=8"><strong>Domino’s</strong></a><strong> | </strong><a href="https://play.google.com/store/apps/details?id=com.dominospizza&amp;hl=en"><strong>Avg. Customer Rating: 4.5</strong></a></p><figure><img alt="The Top Five Mobile Commerce Apps" src="https://cdn-images-1.medium.com/max/1024/0*sOMYNXORRZOMCApU.png" /></figure><p><strong>What they do right:</strong></p><p>Domino’s Pizza now identifies itself as a technology company due in large to the remarkable success of their app, and the especially shrewd inclusion of their voice ordering assistant <a href="http://shortyawards.com/7th/dom">“Dom”</a>. In 2014, Domino’s easily hit its goal of having 50% of all orders via digital platforms, and their numbers have steadily increased in the following years. Customer’s only complaints seem to be regarding their error system, which unexpectedly pushes error notifications when food is unavailable, or promotions are expired.</p><p><strong>Best Features:</strong></p><p>-Integrated with apple watch</p><p>-Voice ordering</p><p>-Can order as a guest</p><p><strong>Worst features:</strong></p><p>-Too many notifications (when the pizza is in the oven, when it’s out, when it’s driving)</p><p>-Bad error system, will offer an error code without explanation</p><p>-Very text heavy</p><p><a href="https://itunes.apple.com/us/app/walgreens-pharmacy-photo-coupons-and-shopping/id335364882?mt=8"><strong>Walgreens</strong></a><strong> | </strong><a href="https://play.google.com/store/apps/details?id=com.usablenet.mobile.walgreen&amp;hl=en"><strong>Avg. Customer Rating: 4.5</strong></a></p><figure><img alt="The Top Five Mobile Commerce Apps" src="https://cdn-images-1.medium.com/max/1024/0*YjIRWVAEe3CvaGtp.png" /></figure><p>Walgreens is using their mobile app to help alleviate some of the stress that comes with frequent visits to the pharmacy. This app is a one-stop shop for medical and prescription management. Walgreens allows you to track your medications, photograph individual pills for visual representation of what should be taken and when, notifies you when it is time to take a pill or refill an order, and even connects you with an on-call doctor. It easily snagged a spot in our list of the top five mobile commerce apps.</p><p>The drawbacks are mostly the lack of communication between the app and the actual Walgreens staff. A common customer <a href="https://itunes.apple.com/us/app/walgreens-pharmacy-photo-coupons-and-shopping/id335364882?mt=8">complaint</a> is an inability to problem solve when notified of an error with medications. An app is only as good as the back-end support, to have a fully-functional mobile system your online ordering options should be fully integrated with the rest of the company.</p><p><strong>Best Features:</strong></p><p>-Allows easy scanning of barcodes to refill prescriptions</p><p>-Set pill reminders, and add medications directly from med list</p><p>-Chat with a doctor for free via the app</p><p><strong>What they do wrong:</strong></p><p>-It’s easy to send your prescription to the wrong Walgreens, goes back to a default store</p><p>-Staff hasn’t been taught to use the app</p><p>-Notifies you of a problem with a prescription but doesn’t offer solutions</p><p><a href="https://itunes.apple.com/us/app/doordash-food-delivery/id719972451?mt=8"><strong>Doordash</strong></a><strong> | </strong><a href="https://play.google.com/store/apps/details?id=com.dd.doordash&amp;hl=en"><strong>Avg. Customer Rating: 4.4</strong></a></p><figure><img alt="The Top Five Mobile Commerce Apps" src="https://cdn-images-1.medium.com/max/1024/0*WfvIFQ05d2meGHeK.png" /></figure><p>Doordash provides your favorite foods with the click of a button. While this app does a lot of great things, its strongest selling point is probably its simplicity. There are really only four screens, five including check out, making it very easy to maneuver from sign up to payment. It’s heavily location-based, meaning the first item you plug in is your address and from there you can interact with the remainder of the app.</p><p>It offers very transparent information from the get-go, including estimated arrival times, delivery charges, and average customer ratings. You can login with Facebook for even faster ordering, and it allows you to put in a default contingency plan if what you ordered is out of stock.</p><p>Doordash’s only fault seems to be in the actual execution. Many <a href="https://itunes.apple.com/us/app/doordash-food-delivery/id719972451?mt=8">customers complain </a>of inconsistency in terms of drivers, delivery time, and even receiving placed orders.</p><p><strong>Best Features:</strong></p><p>-Delivery prices are marked clearly next to each restaurant</p><p>-Shows restaurant ratings</p><p>-Shows estimated time of arrival</p><p><strong>Worst Features:</strong></p><p>-Let’s you get to the order page for restaurants that are closed, though it does allow pre-ordering</p><p>-No notifications for when you go offline</p><p>-Colloquial communication, borderline unprofessional</p><h4><strong>The Future of Mobile Commerce:</strong></h4><p>According to a recent article by <a href="http://www.businessinsider.com/mobile-commerce-shopping-trends-stats-2016-10">Business Insider</a>, in 2014 mobile commerce made up 11.6% of the $303 billion U.S. e-commerce total, and is expected to rise as more retailers adopt m-commerce platforms. In fact, a study by <a href="http://www.businessinsider.com/mobile-commerce-shopping-trends-stats-2016-10">LexisNexis </a>polled 1,000 U.S. merchants and found that 16% already had an m-commerce channel, while 32% were thinking of adding one.</p><p>The value of m-commerce, though, lies in the execution. Like the five brands mentioned above, great features can be outweighed by poor design, or a disconnect between technology and staff. In addition to good design, m-commerce should provide a better customer experience, but many companies still struggle with seamless integration between their app, website, and physical store. Adding a platform can also be prohibitively expensive for smaller chains, and can prevent them from staying competitive in their fields.</p><p>In terms of the future of mobile commerce companies like <a href="http://getchop.co/">Chop,</a> provide an affordable branded solution to small and mid-sized chains. With the option to add features like voice ordering, <a href="https://developers.google.com/web/progressive-web-apps/">Progressive web app</a> (an app-like website that allows you to order and pay ahead), as well as a custom app, <a href="http://getchop.co/">Chop</a> eliminates back-end costs while providing a reliable solution that can rival any of the larger chains.</p><p><a href="http://getchop.co/">Chop </a>provides a future-proof solution that can grow with your company and any advancements in technology. It’s a simple solution to m-commerce.</p><p>Did your favorite make our list? Let us know by commenting below or on any of our social media outlets. As always, feel free to reach out to us on twitter <a href="http://twitter.com/chopnow">@chopnow</a> or via email at <a href="/service/mailto:support@getchop.io">support@getchop.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f70e081bae9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/the-top-five-mobile-commerce-apps-f70e081bae9b">The Top Five Mobile Commerce Apps</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your Restaurant, Powered by Chop]]></title>
            <link>https://medium.com/chop-technologies/your-restaurant-powered-by-chop-1f8b06f202cd?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f8b06f202cd</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[restaurant]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-commerce]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Wed, 17 May 2017 15:08:39 GMT</pubDate>
            <atom:updated>2017-05-17T15:08:38.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mTa6Zu49iphoj9E1.jpg" /><figcaption>(photo credit: <a href="https://unsplash.com/collections/627908/website?photo=i_xVfNtQjwI">https://unsplash.com/collections/627908/website?photo=i_xVfNtQjwI</a>)</figcaption></figure><p>We’re excited to announce the launch of Chop for Business (<a href="http://getchop.co/">getchop.co</a>), which enables restaurants to deploy their own branded solution, powered by Chop technology.</p><p>Since our initial <a href="http://blog.getchop.io/2016/10/13/why-chop/">launch</a> last October we have partnered with more than a dozen restaurants in San Francisco. We have a <strong>&gt;35% visit to registration rate</strong>, and a <strong>&gt;14% click to purchase rate</strong>, which is much higher than the standard commerce conversion rate. The reason why is simple: Chop’s main focus is user experience.</p><p>With our current business model however, which allows individual restaurants to be on the Chop platform, we have to acquire both users and merchants — making for a business model that’s difficult to scale without a large sales force.</p><p>Our users respond to our clean design, and functionality, and restaurants like the ease of deployment. It seemed a natural extension then, to provide the Chop platform to restaurants searching for an affordable, branded mobile commerce solution. For restaurants, Chop provides the front-end technology customers want, without crippling expenses or an in-house engineering team.</p><p>Chop is a future-proof mobile commerce platform, written from the ground up in <a href="https://facebook.github.io/react-native/">React Native</a>. React Native allows for easier OTA updates, theme customization and faster iteration, all of which are essential for restaurants who want to maintain their own brands, while doing quick inventory updates, and menu changes over the cloud.</p><p>In the age of mobile commerce, it’s clear that businesses have to engage customers differently. Customers want ease of ordering, pay ahead options, and faster service, and Chop allows restaurants to provide just that. Our commerce product offerings will include apps, mobile web via <a href="https://developers.google.com/web/progressive-web-apps/">Progressive Web App</a>, Facebook Messenger, and voice. While the app delivers the best user experience, the <a href="https://developers.google.com/web/progressive-web-apps/">Progreesive Web App</a> gives users instant access to the service without having to download a thing. Voice and messenger ensure Chop grows with your business, ideal for hands-free ordering, or shortcuts to service. Mix and match the services you want to offer, for a custom platform designed just for your restaurant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/228/0*M86fN8cfAigGUECF.png" /></figure><p>Our mission is to deliver the best mobile commerce experience. Feel free to reach out at (<a href="/service/mailto:support@getchop.io">support@getchop.io</a>) if you’d like to learn more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f8b06f202cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/your-restaurant-powered-by-chop-1f8b06f202cd">Your Restaurant, Powered by Chop</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for Accidental Disconnects: Our first attempt at an offline approach]]></title>
            <link>https://medium.com/chop-technologies/designing-for-accidental-disconnects-our-first-attempt-at-an-offline-approach-2ac0bdb6d170?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/2ac0bdb6d170</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[offline-first]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Wed, 14 Dec 2016 16:21:02 GMT</pubDate>
            <atom:updated>2016-12-14T16:21:02.162Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MGhVGKzCk1pOhL1VRuRr1A.jpeg" /><figcaption>(Photo credit: <a href="https://www.shutterstock.com/home">https://www.shutterstock.com/home</a>)</figcaption></figure><h4>“Frequently not having any data connection in even the wealthiest and most developed cities of the world has led us to conclude that no, the mobile connectivity/bandwidth issue isn’t just going to solve itself on a global level anywhere in the near future.”</h4><p><a href="http://hood.ie/blog/say-hello-to-offline-first.html">http://hood.ie/blog/say-hello-to-offline-first.html</a></p><h3><strong>Background</strong></h3><p><a href="http://getchop.io/">Chop</a> is a mobile commerce service for small and medium-sized businesses in San Francisco. Our initial focus was, and continues to be, SoMa and the Financial District. We assumed our customers in San Francisco would always have strong connectivity. That in the heart of the tech industry data connectivity would rarely be an issue. Then, during our private beta, we realized we had overlooked a very critical issue:</p><ul><li>Initially, we assumed Chop would be used to order ahead, or order at the store. Instead, many of our users order on the go. This results in intermittent mobile connections in an unpredictable way. While users have great connectivity in one moment, in the next they could lose connectivity while walking between two tall buildings, or entering a Bart station. We didn’t encounter this problem during internal testing, because we mostly used Chop in our offices, connected to the high speed internet.</li><li>All of our merchants receive Chop orders on a tablet. However, some of our merchants are inside office buildings with shared WiFi. This results in a perpetually weak signal, particularly during busy hours. Meaning, user orders are delayed because of a weak signal.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yVK57-qE5mp0vvPeXlynww.jpeg" /><figcaption>(credit: <a href="https://static.pexels.com/photos/160791/tomatoes-ketchup-sad-food-160791.jpeg">https://static.pexels.com/photos/160791/tomatoes-ketchup-sad-food-160791.jpeg</a>)</figcaption></figure><p>Connectivity issues on both sides of the ordering process, resulted in numerous errors. We were losing orders, duplicating orders, and some were simply not going through. It was an issue we had to address before public release.</p><h3><strong>Common Use Cases for Commerce</strong></h3><p>We’re a small startup with limited resources, so we started by examining various use cases, to help us to decide what we should focus on first.</p><p>There are two user groups with common commerce use cases:</p><ul><li>New users who are trying to make their very first purchase</li><li>Repeat customers</li></ul><p>At our current stage, our key focus is to grow the number of engaged users who can complete the core actions. I recommend reading Sarah Tavel’s excellent article on <a href="https://news.greylock.com/the-hierarchy-of-engagement-5803bf4e6cfa#.qwsqbp8n0">The Hierarchy of Engagement</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*YlLY-l6qw-CAiHNP." /><figcaption>(credit: <a href="https://news.greylock.com/the-hierarchy-of-engagement-5803bf4e6cfa#.dsitbg8ro">https://news.greylock.com/the-hierarchy-of-engagement-5803bf4e6cfa#.dsitbg8ro</a>)</figcaption></figure><p>The core action for Chop is to complete an order which involves the following steps:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/269/1*MAnNcQv6Y1Qm0_wtJfyTFQ.png" /></figure><p>Core actions:</p><ol><li>Browse catalog</li><li>Add to shopping cart</li><li>Login (for first time user)</li><li>Setup payment (for first time user)</li><li>Checkout</li><li>Notify customer when purchase is ready</li></ol><p>If you have 100 users at the first step, ideally you want to have 100 users at the last step. You do this by removing as much friction as possible. From the user’s perspective, the further along they are in the process, the more time and energy they’ve invested. The more invested a customer is, the angrier they’ll be if something goes wrong.</p><h3><strong>Case Studies</strong></h3><p>To better understand how to solve the issue of offline connectivity, I looked at similar apps to see how they were solving this problem.</p><p>Conducting offline research:</p><ul><li>First, I would open the app and click on all major screens. I would look through options like: browsing the catalog, past orders, adding an item to a shopping cart, or clicking on various items.</li><li>I would then close the app, and turn my phone onto airplane mode. Then, I would open the app again and reopen all major screens. Specifically I would: browse the catalog, browse my past orders, go to the item/subcategory I visited previously, add an item to the shopping cart, got to a new item I hadn’t previously visited, and place an order.</li></ul><p>Here’s what I discovered from my case studies:</p><h4><strong>Amazon</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwfE3a09QS_dtkD2DBY66g.png" /><figcaption>Case study: Amazon</figcaption></figure><p>Findings:</p><ul><li>Amazon for iOS only provides a very basic offline check. On every page load, Amazon checks the network status and, if poor connectivity, displays a “Network Error” message while rendering the page.</li><li>If you try to go to another page after that, it takes you to a splash page with pretty standard terminology. It is unclear what (CS1) means, it is probably an internal error code.</li></ul><p>Amazon is the number one commerce site in the world but the offline experience is unimpressive. When operating offline, users are not given any expectations as to what should and should not work.</p><h4><strong>Starbucks</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rKHrDC42XnvjYbACqP1Duw.png" /><figcaption>(Case study: Starbucks)</figcaption></figure><p>Findings:</p><p>Starbucks delivers a similar experience. Your network status is checked on every page, and when there is poor connectivity it displays a standard error message. However, if you dismiss the message, it allows you to navigate to other cached pages before showing the same error message again.</p><p>The message dialog feels like a foreign part of the UI, cold and unintuitive, but it does get the job done — which is to confirm the network error and not to let users go any further.</p><h4><strong>Doordash</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kN7vPUkT0qCQG2cet3O6fQ.png" /><figcaption>(Case study: Doordash)</figcaption></figure><p>Doordash, even as a younger startup, delivers a delightful experience:</p><ul><li>You can browse the catalog, view your order history, and even add to your shopping cart if you can access the item all the way through checkout.</li><li>That being said, the notifications alerting users they’re offline is not always consistent. For example, if a restaurant is not available and not cached, Doordash will display a red background with no text or explanation. If you try to place an order when offline, you will see a grey system dialog or, an offline splash page. Furthermore, if you reopen the app while offline, it directs you to sign in. I don’t think that’s what they intended the user to do while they’re offline.</li></ul><p>I researched a few more examples and found, in general, there are no established UX patterns for offline. Should users be able to browse the catalog? Should they be able to continue adding to their cart offline? How should network errors be displayed? Is it possible to design the offline experience, so users can continue even with poor connectivity?</p><h3><strong>Offline Design at Chop</strong></h3><p>Without much guidance from the more established commerce sites, we decided to follow our own design principles and be as thoughtful to the user as possible. That meant:</p><ul><li>Making sure the offline experience was<strong> error free for the most critical part</strong>: checkout to order completion.</li><li>Giving users a decent browsing and shopping cart experience by<strong> caching as much data as possible</strong>. If the data is available, users can go much farther on the client side.</li><li>Developing a generic splash page with a <strong>positive emotion</strong>, to alert users their connection is bad.</li></ul><p>Here is what we’ve implemented so far:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G5XsLosZ1vVGiSljJpcBOg.png" /><figcaption>Offline design at Chop</figcaption></figure><p>In general, we leverage client’s cached data as much as possible to ensure users have a seamless offline experience. We defer checking a user’s connection until they are ready to place an order. In our case, as a mobile commerce solution only available in San Francisco, most of our users have an intermittent connection rather than no access at all. We’ve taken that into consideration. We now make several attempts to connect to a network before giving up and displaying the splash page.</p><p>We designed a splash page with a restaurant and food theme, with copy that says “Gone Fishing. Your internet is off the hook mind trying again?” It’s displayed if a user is disconnected, or if they click on a page that doesn’t have any cached data. Hopefully, it functions to lighten the mood for the user, so they are distracted from the disappointment of a failed order. At this point, we also let the user take control, and give them the option to try again.</p><h3><strong>Offline Development at Chop</strong></h3><p>While this article focuses on design, I do want to bring up a few points about development.</p><h4><strong>How to ensure there are no duplicate orders</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_gdsk5UBhYCjkLmlMdXsA.png" /><figcaption>Flow chart: how to handle duplicated orders</figcaption></figure><p>When an order is first placed, the client generates a UUID for the order, and it is persisted to local storage on their iPhone, so if the app crashes, is killed, or otherwise needs to recover, an order in progress isn’t lost. After committing to local storage, the phone makes a REST call to the server to place the order and charge the consumer. If an existing order is already in the system and has been successfully charged with the same UUID, the order is rejected as a duplicate.</p><p>The transition to a successfully charged order is two-phased. First, the order is persisted into an ACID database marked as UNPAID, then it is read and charged to Stripe and marked PAID. If the consumer has another order in progress at the same merchant with a different UUID within a defined time window, it is also rejected, because we do not allow more than one order in progress at the same merchant by design.</p><p>The user cannot be charged for the same order twice because it is guarded by UUID check and a database check. The client also can’t submit the order twice if it has already been submitted.</p><h4><strong>How to ensure no lost orders</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjDYKNb2IdMQR7NLfOtN4A.png" /><figcaption>(Flow chart: lost order detection and escalation path)</figcaption></figure><p>Our merchant tablets constantly ping heartbeats to the server. We have a Quartz Scheduler process that monitors the last time tablets have pinged the server, and how long orders at each merchant have been sitting unclaimed.</p><p>When idle time exceeds a threshold, an issue is automatically created in an internal issue tracker, and eventually escalated to Slack. If the merchant responds during this time window, the issue is automatically closed and reported to Slack as resolved.</p><p>Eventually, if the downtime persists and Slack messages do not elicit a response, it will be escalated to an SMS message.</p><h3><strong>Final Thoughts</strong></h3><p>What we have implemented so far is by no means perfect, but it is a good first step to ensure our customers can successfully make orders through intermittent connections. We are interested in delivering more. For example, on the splash page, rather than saying “Try again”, can we change it to “Notify me when online”? That way, when the phone is back online, we can send a friendly notification from which the user can preview their shopping cart and place their order without even opening the app.</p><p>Through this exercise, what I have realized is that users don’t have any set expectations for offline experiences. It is in general, as shown through my case studies, a negative spectrum. There is so little information out there about offline UX best practices, whether on web apps or native apps. There are, however, some interesting technologies available now such as <a href="https://www.w3.org/TR/service-workers/">Service Workers</a> which I am hoping to explore in 2017 when we start the web app.</p><p>Through this article, I hope to see more conversations around offline design and development practices from the community, let’s make offline a positive experience.</p><p>I also found an <a href="http://offlinefirst.org/">Offline First! </a>community which is pretty awesome.</p><h3><strong>Good Reads:</strong></h3><ul><li><a href="http://alistapart.com/article/offline-first">http://alistapart.com/article/offline-first</a></li><li><a href="https://uxdesign.cc/offline-93c2f8396124#.k4qeni66a">https://uxdesign.cc/offline-93c2f8396124#.k4qeni66a</a></li><li><a href="https://medium.com/@jessebeach/my-biggest-takeaway-from-the-second-offline-camp-in-santa-margarita-ca-d0dd930cd02b#.flnqpm9un">https://medium.com/@jessebeach/my-biggest-takeaway-from-the-second-offline-camp-in-santa-margarita-ca-d0dd930cd02b#.flnqpm9un</a></li><li><a href="https://medium.com/offline-camp">https://medium.com/offline-camp</a></li><li><a href="https://pwa.rocks/">https://pwa.rocks/</a></li><li><a href="https://www.kainos.com/offline-first-approach-e-commerce/">https://www.kainos.com/offline-first-approach-e-commerce/</a></li></ul><p>Read <a href="https://blog.getchop.io/why-chop-9d6b731c8ef4#.nuxx53yhl">Why Chop</a></p><p>Visit our website at <a href="http://getchop.io/">getchop.io</a>.</p><p><a href="https://goo.gl/g9M1EW">Download iOS app</a> and share with a friend.</p><p>Follow Chop on <a href="http://twitter.com/chopnow">Twitter</a>, <a href="http://instagram.com/thechopapp">Instagram</a>, <a href="http://facebook.com/thechopapp">Facebook</a>.</p><p>Follow me on <a href="http://twitter.com/viviancromwell">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ac0bdb6d170" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/designing-for-accidental-disconnects-our-first-attempt-at-an-offline-approach-2ac0bdb6d170">Designing for Accidental Disconnects: Our first attempt at an offline approach</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Purposeful Design for User Permission]]></title>
            <link>https://medium.com/chop-technologies/purposeful-design-for-user-permission-e0ca1a86fdb4?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/e0ca1a86fdb4</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 17:54:25 GMT</pubDate>
            <atom:updated>2016-12-05T06:47:43.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ac1gAOiI6_RYiDT51VDxjg.jpeg" /><figcaption>(Credit: <a href="https://www.pexels.com/photo/iphone-checklist-hands-human-29765/">https://www.pexels.com/photo/iphone-checklist-hands-human-29765/</a>)</figcaption></figure><h3><strong>“Design is the beauty of turning constraints into advantages.”</strong></h3><h4><strong>— By Aza Raskin</strong></h4><h3><strong>Design Within the Constraints</strong></h3><p>I love mobile design because it’s full of constraints. Those constraints force us to think carefully about how and when we present information to the user, and what questions we ask, leading the user to hopefully make the selection we want.</p><p>At <a href="http://getchop.io/">Chop</a>, we went through three design iterations with a few user testings in between, before we released the first version in October. The consumer mobile app is much less forgiving compared to web apps that often have very iterative processes. This is also the first mobile design and development experience for me, and I was very keen on delivering the experience that I would want as a user.</p><p>One example is the classic notification permission. Chop needs both geolocation and notification permission. We ask for geolocation so we can prepare the right nearby stores. We need notification permission so we can notify the user when their order is ready, and prompt them when they’re close to locations they’ve ordered from previously.</p><h3><strong>The Common Approaches</strong></h3><p><a href="https://library.launchkit.io/@mulligan">Brendan Mulligan</a> from <a href="https://launchkit.io/">Launchkit</a> has a <a href="https://library.launchkit.io/the-right-way-to-ask-users-for-ios-permissions-96fa4eb54f2c#.80n085e1k">great article</a> that covers many of the design patterns for permission. The most common approaches are:</p><p><strong>Ask users bluntly without any context</strong></p><p>When you first open the app, you get the iOS system popup: “We would like to send you notifications”. This is the worst. It’s too easily ignored.</p><p><strong>Explain and ask during onboard</strong></p><p>A more widely adopted approach is to explain why the app needs notification permission during the onboard process. This approach is still suboptimal because the purpose of such permission is not always obvious during the initial steps.</p><h3><strong>The Initial Wireframe</strong></h3><p>Here is the very first wireframe for Chop. We tried to explain the benefits of geolocation and notification during the onboard. We gave a lot of information to the users upfront: we need your location so we know where you are, we will notify you when your order is ready, and notify you again if you visit the place frequently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*-Nbh0Pl59iw9AkcApEzuzA.png" /></figure><h3><strong>Design Iteration One</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gFvQqj_1aTWG24UmiDt4bg.png" /></figure><h3><strong>User Study</strong></h3><p>The above wireframe took a very typical approach, which is to ask permission upfront. I was curious as to how users actually react to those common design approaches so we recruited six users in San Francisco to test two freshly-installed apps. One was a news app, the other a commerce app. We asked them to discuss their thought processes when they saw the permission prompt.</p><p>Here’s what we found:</p><ul><li>Users accept the fact they will be asked for notification permission.</li><li>When a user is asked for notification permission, they are much much more likely to say “yes” to a transaction-based app than to a content-oriented app. It is simple, they pay money in a commerce app, so they want to receive what they paid for.</li><li>More than 50% of the users don’t want to give permission to content-oriented apps because they are unsure of the app’s value. They want to give it a try and enable notifications later.</li><li>Some of them mentioned if they are getting too many notifications, they uninstall the app.</li></ul><h3><strong>Design Iteration Two</strong></h3><p>The above user study confirms that the likelihood of a user giving us notification permission is decent because Chop is a transaction-based app. However, we wanted to push it further. We wanted to have the fewest number of screens between the user and their first order, and we wanted to be truly thoughtful for the user, and ask only what we really needed to know.</p><p>After recognizing what we wanted, we realized that we only needed to ask for notification permission after the user made their first purchase. So, we considered what would happen if we moved the notification permission to follow checkout. Some may argue that you want to get the user notification permission as soon as possible, so you can re-engage them with a popup. However, if you fail to get the user to make their first order on their first try, how likely is it that they will come back because of a notification? Perhaps you can entice them with a discount, but customers acquired this way typically have low retention. I know as a user, I would most likely ignore similar notifications.</p><p>We are betting on a clean and thoughtful user experience, where we focus on getting the user to complete their first purchase. We decided to move the notification screens to after checkout. If the user has already paid, obviously he or she would want to get notified when their order is ready, right?</p><p>Here is the design for iteration two:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwvKWDRlnrY_pvdEFrolOg.png" /></figure><p>A slight variation when we decided to omit the background image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwTsyH9ZHwZr_pf7NcT9WQ.png" /></figure><h3><strong>Design Iteration Three (the Current One)</strong></h3><p>We were pretty happy with the last design iteration — moving the notification to after the user makes their first purchase. But, we still felt there were too many screens before the user could complete their first purchase, including the onboard and login screens. We looked for opportunities to remove more, and an idea occurred to us: what if we move the notification permission ask screen inline with the order status screen? Instead of asking users to choose between “Notify me” and “Don’t notify me” as a separate screen, we will inline the ask and let the user initiate the request.</p><p>Here is the design iteration round three:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ffZm9vYe6d95uAhf1wliQ.png" /></figure><p>As you can see, we embedded, “Notify me when it’s ready” on the “Order Status” screen and the request is initiated by the user. The nice thing about this design is that if the user doesn’t initiate on their first order, the option is always there on their second or third order. While in the previous design, the user had an either/or choice to either get notified or not, they didn’t have the option to choose later.</p><p>Again, here we are betting on a clean and thoughtful design that we hope will lead users to come back on their own.</p><p>This design is currently in production, which we launched in mid October. Four weeks in, we are happy to report that 70% of the users enabled notification on their first order. Without ads and a big budget, we have a small set of users who love the service and come back regularly. It’s a wonderful feeling waking up in the morning, thinking that one of your customers might be ordering the same Acai bowl as you on their way to work, then it happens, just like that.</p><h3><strong>Next Step</strong></h3><p>So we summarized our design iteration on a simple notification permission, what’s next? There are quite a few things we want to improve.</p><p>For example, how can we increase that 70% notification permission to 90% on the first order? Can we make the UI a more intuitive “call for action”? Now that we know users’ regular ordering patterns, can we enable <a href="https://developer.apple.com/videos/play/wwdc2016/708/">rich notification</a> on the lock screen so that when a user is nearby, they can start their usual order without opening the app?</p><h3><strong>Good Reads</strong></h3><ul><li><a href="https://library.launchkit.io/the-right-way-to-ask-users-for-ios-permissions-96fa4eb54f2c#.lsoldwhnq">The right way to ask for iOS permission</a></li><li><a href="https://labs.ribot.co.uk/exploring-the-new-android-permissions-model-ba1d5d6c0610#.j6kvhjopg">Exploring the new Android permission model</a></li><li><a href="https://uxplanet.org/mobile-ux-design-the-right-ways-to-ask-users-for-permissions-6cdd9ab25c27#.tzxicqs92">The right way to ask for user permission</a></li><li><a href="https://news.dueapp.com/ios-10-notifications-one-step-forward-one-step-back-fe712469184e#.pphl14z5e">iOS 10 notification, one step forward, one step backward</a></li></ul><p>Special thanks to Andrew Littmann and Brian Benitez, who help create the thoughtful user experience for Chop and provide guidance as I learn about the mobile design .</p><p>Read <a href="https://blog.getchop.io/why-chop-9d6b731c8ef4#.nuxx53yhl">Why Chop</a></p><p>Visit our website at <a href="http://getchop.io/">getchop.io</a>.</p><p><a href="https://goo.gl/g9M1EW">Download iOS app</a> and share with a friend.</p><p>Follow Chop on <a href="http://twitter.com/chopnow">Twitter</a>, <a href="http://instagram.com/thechopapp">Instagram</a>, <a href="http://facebook.com/thechopapp">Facebook</a>.</p><p>Follow me on <a href="http://twitter.com/viviancromwell">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0ca1a86fdb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/purposeful-design-for-user-permission-e0ca1a86fdb4">Purposeful Design for User Permission</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Chop]]></title>
            <link>https://medium.com/chop-technologies/why-chop-9d6b731c8ef4?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/9d6b731c8ef4</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[retail]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Thu, 13 Oct 2016 15:22:37 GMT</pubDate>
            <atom:updated>2016-12-05T06:47:25.524Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGKEtYgDgI1zcCJRBGU2Lg.png" /><figcaption>Credit: Andrew Littmann</figcaption></figure><p>As the mother of two small children, and the founding engineering manager of the Chrome Developer Relations team at Google, I’ve led a busy life. When your day-to-day is an unending balancing act, you learn to prioritize the important things, and cut back on unnecessary time constraints. With my lack of time, came an appreciation for timesaving options. I stopped going to my local coffee shops, and instead chose Starbucks because of their mobile app. I didn’t want to wait in line and be asked everyday the same series of questions: what’s your name, your order, would you like your receipt?</p><p>I wished more places offered the Starbucks commerce experience, and I marveled at how e-commerce and the cloud had transformed the way we did almost everything. From shopping to traveling, the internet eliminated single points of failure, and streamlined clunky processes. But there was one place where it still fell short: retail.</p><p>We are all carrying around pocket supercomputers that are more powerful than the servers that used to run e-commerce sites. Why then, can’t we use our phones to have an Amazon-like experience at our favorite cafés or stores, without waiting?</p><p>I started <a href="http://getchop.io/">Chop Technologies</a> to answer that question.</p><h4><strong>Our mission is to make a mobile commerce solution that will grow with merchant and consumer needs, available and affordable to </strong>local businesses<strong>. Customers can then have the Starbucks experience at any shop, and the merchant avoids astronomical upfront costs.</strong></h4><h3>Chop, autocomplete for the real world</h3><p>Chop streamlines your retail experience with the following principles in mind:</p><p><strong>Allow Consumers To Choose How They Engage</strong></p><p>Consumers today have the freedom to interact with services in a multitude of ways, and our goal is to enable users to use the mobile interface they want, including: app, messenger, voice, and web.</p><p><strong>Contextual Experience, Don’t Repeat Yourself</strong></p><p>When your Web browser visits a site you’ve already been to, it doesn’t prompt you for information you’ve already entered. Similarly, Chop senses when you’re nearby retailers you’ve visited, and makes your experience personalized based on previous orders. Over time, Chop learns your habits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*8C4j_L4Lc35Xw8jxKR5MUQ.png" /></figure><p><strong>Don’t Ask For Information You Don’t Need</strong></p><p>Chop only asks for information when it needs it. Your login is your phone number and your default payment is Apple Pay when available. You won’t be asked to login until you are ready to buy. The app won’t even ask for notification permission until your first order is complete.</p><p><strong>Keep It Simple and Be Helpful</strong></p><p>We are creatures of habit and we often return to what is familiar. Chop provides users with easy access to usual orders with a simple tap.</p><p>Chop also eases the pain of waiting. The app tracks estimated wait times at retail locations and notifies you of the status of orders in progress, and when your order is up.</p><h3>Merchants Need Help Too</h3><p>At the end of 2015, Starbucks announced that<a href="http://www.businessinsider.com/starbucks-mobile-app-proves-successful-marketing-strategy-2016-4"> 21%</a> of all orders were placed through their mobile app, proving that mobile commerce is a necessary step for retailers.</p><p><a href="http://inside.chick-fil-a.com/how-the-chick-fil-a-one-app-came-to-be/">Chick-Fil-A,</a> another corporate heavyweight, recently released a mobile app that received over a million downloads within the first three days. But the phenomenal success was no small job. The app was developed over three years, by a core team of more than 30 developers, designers, web architects, and others.</p><p>While this proves that retail is headed in the direction of mobile commerce, most small to medium sized business can’t afford a mobile solution — let alone keep up with the changing landscape of mobile commerce. Merchants should worry about making money, not updating their technology.</p><p>That’s where Chop comes in. Chop offers a solution that will grow with merchant and consumer needs. Customers can then have the Starbucks experience at any shop, and the merchant avoids astronomical upfront costs.</p><h3>One Small Step, One Giant Leap</h3><p>Today, we’re taking the first small step. The Chop App is now available at twelve locations in San Francisco’s Financial District and SoMa. <a href="https://itunes.apple.com/app/apple-store/id1014701156?pt=117822809&amp;ct=medium&amp;mt=8">Download it now</a> on iOS, or stay tuned for an upcoming Android version. We’re also working tirelessly to make Chop more customizable for brands and chains.</p><p>Feel free to test out Chop, and offer <a href="/service/mailto:support@getchop.io">feedback</a>. We’re passionate about this project and are always working to improve the user experience.</p><p>Thanks to Ben Lisbakken, Saul Devitt, Jacky Nguyen, Andrew Littmann, Brian Benitez, and Katie Crowley who helped make this happen. And to Peter Hazlehurst and Ray Cromwell for being great advisors.</p><p>For those who are interested in the tech bits, here is an <a href="https://blog.getchop.io/how-we-built-chop-bae3d8acd131#.th00ab3go">article</a> that outlines our technology stack and why we chose React Native.</p><p>Vivian</p><p>Visit our website at <a href="http://getchop.io/">getchop.io</a>.</p><p><a href="https://goo.gl/g9M1EW">Download iOS app</a> and share with a friend.</p><p>Follow Chop on <a href="http://twitter.com/chopnow">Twitter</a>, <a href="http://instagram.com/thechopapp">Instagram</a>, <a href="http://facebook.com/thechopapp">Facebook</a>.</p><p>Follow me on <a href="http://twitter.com/viviancromwell">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d6b731c8ef4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/why-chop-9d6b731c8ef4">Why Chop</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Built Chop]]></title>
            <link>https://medium.com/chop-technologies/how-we-built-chop-bae3d8acd131?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/bae3d8acd131</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Thu, 13 Oct 2016 15:21:13 GMT</pubDate>
            <atom:updated>2016-12-05T06:46:51.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-h51lD09TEGmAje_q69nA.jpeg" /><figcaption><a href="https://unsplash.com/search/tool?photo=vS7LVkPyXJU">https://unsplash.com/search/tool?photo=vS7LVkPyXJU</a></figcaption></figure><h3>Background</h3><p><a href="http://getchop.io/">Chop</a> is a service for mobile commerce, designed with the following goals in mind:</p><ul><li>Beautiful and performant UI</li><li>Fast iteration</li><li>Easy to theme</li><li>Robust backend</li><li>Support many platforms</li></ul><h3>The Team</h3><p>The small team is distributed but experienced, with expert knowledge in both JavaScript and native code. A few of us worked at Google so we value good engineering practices as well as autonomy to get work done at our own pace.</p><h3>Where We Began</h3><p>We believed that native code was a requirement for achieving a smooth, fluid UI, so we began with a prototype in Objective-C on iOS. After two months of development, we had a working demo, but iterative shifts in design were not as fast as we wanted, and the UI design was changing rapidly.</p><p>It was also difficult to find and recruit great Objective-C developers, as I had spent the previous five to six years working with JavaScript developers at Google. Eventually, it was <a href="https://github.com/nktpro">Jacky Nguyen</a>, a long-time mobile web expert and friend, who suggested the switch to <a href="https://facebook.github.io/react-native/">React Native.</a> As someone who loves the Web, React Native was enticing, but at the time it was still very new (October 2015) and we had a built-in bias towards JavaScript as being slow and clunky.</p><p>However, a prototype port that Jacky built in React Native demonstrated buttery smooth 60fps scrolling and animation comparable to our Objective-C implementation. We were convinced.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-l4zygVeZMs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-l4zygVeZMs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-l4zygVeZMs%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c122fcb4d9129621b596bbe0b2edbbdc/href">https://medium.com/media/c122fcb4d9129621b596bbe0b2edbbdc/href</a></iframe><h3>iOS: React Native</h3><p>We switched to React Native three months later. It was a difficult decision for the team. It meant throwing away the money and time we had already invested, and letting go of the iOS engineer.</p><p>I was uneasy about the transition. I had left Google just six months earlier, and was already making a litany of mistakes that I, and I alone, would have to solve. But, I’d learned to trust my instinct. If something doesn’t feel right, it probably isn’t. So, we made the tough decision to switch, and we haven’t regretted it since.</p><p>Right off the bat, React Native offered great benefits:</p><ul><li>Everyone on the team could now edit code, even those who only knew CSS or JS could now tweak the UI</li><li><a href="https://facebook.github.io/react-native/blog/2016/03/24/introducing-hot-reloading.html">Hot-reload</a> was an incredible productivity tool</li><li>We could use more familiar tools to debug like Chrome Dev Tools</li><li>The entire node/npm ecosystem could be leveraged</li></ul><p>Aside from a few custom native modules used to access iOS APIs, 90% of the code is written in Javascript, which makes code reuse on Android and the Web a much easier task. React Native is still a fairly young framework, so it does require more frequent upgrading, and right now we’re a bit behind the latest version.</p><p>We’ve had a great experience using React Native as a team so far, and expect it to pay larger dividends in the future as we expand to a B2B model. React Native makes it simple to skin and customize for a brand and chain’s needs, without repetively building and deploying the app — think of it as web development practice in native apps.</p><h3>Server</h3><p>Our Java8 backend is based on <a href="http://www.dropwizard.io/">Dropwizard/JAX-RS</a>. Originally, we tried to use <a href="http://swagger.io/writing-apis-with-the-swagger-inflector/">Swagger Inflector</a> with our <a href="http://swagger.io/">Swagger</a> REST definition specs to get a similar live reloading experience on the server, but its functionality was incomplete and buggy, and led to quite a few production issues. Switching to Dropwizard cleared up most of those issues, and also had a much cleaner, and sustainable structure with superior documentation.</p><p>Our server is built by using a custom Swagger generator that outputs <a href="https://github.com/google/auto/tree/master/value">Google AutoValue</a> immutable object models, along with <a href="https://github.com/google/gson">GSON</a> based serialization and JPA based persistence helpers.</p><p>The server uses <a href="https://github.com/google/guice">Guice</a> for dependency injection, <a href="https://blog.jooq.org/2015/08/13/common-sql-clauses-and-their-equivalents-in-java-8-streams/">Java8 streams APIs</a> for much of the data processing, <a href="http://square.github.io/retrofit/">Retrofit2/OkHttp3</a> for any outbound HTTP, and sits on top of Google Cloud APIs at the lowest level.</p><h3>REST API</h3><p>We specify our REST interfaces in <a href="http://swagger.io/">Swagger</a>, and test / document / share them with <a href="https://www.getpostman.com/">Postman</a>. Once a specification is produced, it is implemented in JS for React, and implemented in Java for the backend. This worked really well for our distributed team as Ben, our iOS engineer could take a shared Postman collection that tested a REST interface, and use it as documentation and implementation guide for the JS version.</p><p>Swagger specifications are a readable cross-platform way to document REST interfaces and generate code, however, the Swagger spec’s type system is not powerful enough to represent all of our use cases, and the Mustache-based Swagger code-generator system is difficult to extend without cut-and-paste.</p><h3>Database</h3><p>Our data storage needs break down into three categories: order transactions, accounting ledgers, and monetary information. We’re paranoid about having to handle money, and so we chose to use a datastore with ACID properties like Google Cloud SQL. This is relatively painless to use, scales easily, and offers built-in backups.</p><p>We store mostly-static configuration and merchant data in <a href="https://cloud.google.com/storage/docs/json_api/v1/buckets">Google Bucket Storage</a> as JSON. This data is managed by a GitHub repository, and is pushed on commit by CircleCI to bucket storage hosting.</p><p>Finally, we use <a href="https://cloud.google.com/storage/">Google Cloud Storage</a> for dynamic assets as well, such as logs, and user profile photo uploads.</p><h3>Production Environment</h3><p>We knew we needed to have high availability and reliability for a consumer commerce application, which meant avoiding a single point of failure and having robust health checks. We decided early on to use <a href="http://kubernetes.io/">Kubernetes</a> as a cluster management solution. <a href="https://cloud.google.com/container-engine/">Container Engine</a> supports Kubernetes very well and it’s cost effective, making it an easy decision to go with Google’s Cloud.</p><h3>Configuration Management DevOps</h3><p>Setting up and configuring clusters, VMs, networking, and load balancing within Google Cloud’s console is still a process that takes many steps, and it is easy to make mistakes. Our entire GCloud configuration is checked into a GitHub repository, ensuring that the configuration state of our Cloud setup can be completely replicated and restored without a human being using the UI to do it.</p><h3>Security</h3><p>All of our server-side REST endpoints are protected by declarative security. We use a custom HTTP Authentication scheme based on <a href="https://jwt.io/">JWT</a> (JSON Web Tokens) combined with declarative Java annotations. JAX-RS interceptors are used to enforce this restriction by inspecting and verifying incoming HTTP requests, and then injecting decoded JWT tokens as Principals into JAX-RS resource methods. Our database doesn’t store any passwords, as the JWT tokens are ephemeral and based on SMS code authentication.</p><h3>Monitoring</h3><p>We use <a href="https://cloud.google.com/stackdriver/">StackDriver</a> to monitor most of the production systems, but it only tracks failures in a coarse grained way, like a service becoming unresponsive. As we have customers waiting in real time for orders, we needed to be able to track failures at both the merchant and transaction levels.</p><p>We run <a href="http://www.quartz-scheduler.org/">Quartz Scheduler</a> services which continuously monitor the health of deployed merchant tablets as well as the state of orders in flight. Whenever a service is late meeting a deadline, we notify internal Slack support channels, and escalate to SMS via Twilio if need be.</p><h3>MOMS (Merchant Order Management Systems)</h3><p>Our business customers have an Android client they use to manage orders and inventory. This client is built using Java8 with <a href="https://github.com/evant/gradle-retrolambda">Retrolambda</a> for Android Lollipop, and utilizes <a href="https://github.com/ReactiveX/RxJava">ReactiveX/RxJava</a> + <a href="https://github.com/JakeWharton/retrofit2-rxjava2-adapter">Retrofit2</a> to communicate with the Server. RxJava <em>Observable</em>s returned from Retrofit2 REST calls then push immutable data models into Android UI. To see how cool this is, read <a href="https://www.vokal.io/labs/reactive-forms-with-rxandroid">Reactive Forms with RxAndroid</a>.</p><p>Our Android client uses <a href="http://square.github.io/dagger/">Dagger</a> and <a href="http://jakewharton.github.io/butterknife/">BufferKnife</a> for dependency injection which we’ve found quite useful for reducing boilerplate in the UI fragments.</p><h3>Build, Test and Deploy</h3><p>We try to use a Continuous Deployment model as much as possible. Our iOS client is built with <a href="http://fastlane.tools/">Fastlane</a> which drives React’s bundler, gulp tasks, and XCode. <a href="http://fastlane.tools/">FastLane</a> is an awesome toolset for iOS created by <a href="https://twitter.com/KrauseFx">Felix Krause</a>. We use it to not only deploy new builds to iTunesConnect from the command line, but also to sync certificates and profiles across the team.</p><p>Our server is built by <a href="https://maven.apache.org/what-is-maven.html">Maven</a>, and our Android client is built using <a href="https://gradle.org/">Gradle</a>.</p><p>The builds are triggered on GitHub commit and run on <a href="https://circleci.com/">CircleCI</a>. After passing the unit and integration tests, our server is built into a Docker image and pushed to Kubernetes. Our clients are additionally tested by a manual Q/A process and released via TestFlight and Google Play beta channel before being published.</p><h3>Design</h3><p>In the initial few months, we tried out various tools: <a href="https://popapp.in/">Pop</a> for paper prototype, <a href="https://www.flinto.com/">Flinto</a> before we had any code, <a href="https://www.sketchapp.com/">Sketch</a> for wireframe and interaction, <a href="https://www.invisionapp.com/">inVision</a>, <a href="https://www.uxpin.com/">UXPin</a> for collaboration and feedback.</p><p>Nowadays, as we’re more settled in a design direction, we just use Sketch. Sketch is responsive and simple to learn. While it lacks collaboration and versioning, it seems <a href="https://www.figma.com/">Figma</a> helps fill in the gaps. I’m interested in testing out a small project on Figma.</p><h3>Analytics</h3><p>We have some custom built analytics for beacon heuristics, which include real-time logging of Beacon Manager event streams. We used Firebase as the storage backend.</p><p>We use <a href="https://www.google.com/analytics/mobile/">Google Analytics for mobile</a> for our iOS app. I actually found that setting up the right segmentations to measure the correct things was harder and more critical than using any specific analytic tool.</p><h3>Other Developer Products</h3><p>We use <a href="https://stripe.com/">Stripe</a> to process payments, though I wish the dashboard was more intuitive to use.</p><p>We use <a href="https://www.twilio.com/">Twillo</a> for telephony integration for tasks like user onboarding, order notification, and operations support.</p><p>We use <a href="https://instabug.com/">Instabug</a> for bug and crash reports as well as user feedback.</p><p>We use the <a href="http://estimote.com/">Estimote</a> beacon to offer users an opt-in contextual experience when they visit the stores they have ordered from previously. I am super impressed with the quality of the Estimote product and the spirit of a highly innovative startup.</p><p>We are experimenting with <a href="https://api.ai/">Api.ai</a> for bots.</p><p>We are pretty excited about <a href="https://firebase.google.com/">Firebase</a> but it didn’t have a JS API at the launch. We hope to consolidate the various tools we are using to Firebase in the near future, like analytics and bug reports, as well as use features like push message and dynamic invites.</p><h3>What’s Next</h3><p>Lots! One benefit of a young startup is the luxury to experimentation and iterations. Now that we have a solid foundation and infrastructure in place, we hope to iterate based on users’ need as we continue to develop the various mobile interfaces.</p><p>That’s about all of the software and tools we used to build Chop over the past year. Building a product from scratch is hard but rewarding. As we continue this journey, we’ll share more of what we’ve learned, so stay tuned!</p><p>I also want to give a very heartfelt shoutout to Ben Lisbakken, Jacky Nguyen, and Ray Cromwell who helped build Chop into what it is today.</p><p>Vivian</p><p>Read <a href="https://blog.getchop.io/why-chop-9d6b731c8ef4#.nuxx53yhl">Why Chop</a></p><p>Visit our website at <a href="http://getchop.io/">getchop.io</a>.</p><p><a href="https://goo.gl/g9M1EW">Download iOS app</a> and share with a friend.</p><p>Follow Chop on <a href="http://twitter.com/chopnow">Twitter</a>, <a href="http://instagram.com/thechopapp">Instagram</a>, <a href="http://facebook.com/thechopapp">Facebook</a>.</p><p>Follow me on <a href="http://twitter.com/viviancromwell">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae3d8acd131" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/how-we-built-chop-bae3d8acd131">How We Built Chop</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast and Fluid Infinite List with React Native]]></title>
            <link>https://medium.com/chop-technologies/fast-and-fluid-infinite-list-with-react-native-336d010e51f2?source=rss----ebfd2ea5ab2e---4</link>
            <guid isPermaLink="false">https://medium.com/p/336d010e51f2</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Vivian Cromwell]]></dc:creator>
            <pubDate>Tue, 29 Mar 2016 15:26:58 GMT</pubDate>
            <atom:updated>2017-02-02T05:58:05.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nWYQhxGOrVjPfhhcL9C0Nw.jpeg" /><figcaption>Infinite Mirrors</figcaption></figure><h3>Background</h3><p>Infinite List, Windowed List, and RecyclerView are not new. In fact, their ideas are rather simple: render only what’s visible from the user’s viewport, recycle all item view instances with a smart backing data store, and progressively re-render dirtied items based on the scroll position delta. But details matter, and it’s not often done efficiently, regardless of platforms.</p><h3>Our Use Case</h3><p><a href="http://getchop.io/">Chop</a> is a mobile commerce startup in the pre-launch stage. Since our inception we chose React Native to develop our iOS prototype both for technical and business reasons:</p><ul><li>We need Native features like Bluetooth, background tasks, notifications, and payment options on iOS. With the <a href="https://infrequently.org/2015/06/progressive-apps-escaping-tabs-without-losing-our-soul/">Progressive Web App</a> the Web is getting there, it just isn’t universally available yet.</li><li>Prior to building Chop, I worked at Google and founded the Chrome Developer Relations team back in 2009, and remained there for over four years. During that time, I got to know the JavaScript developer community rather well. While the language has its own shortcomings, what I love most about JavaScript are the people behind it. Their creativity, passion, and eagerness to share are unrivaled. The system can be fragile from time to time, but the community reacts and responds quickly to any issues. It’s similar to a human body, with the right antibodies and the ability to self-correct it’s always strong.</li><li>We hope to develop on Android platform later and possibly a web version of Chop in the future. React Native allows us to to maximize code reuse across all platforms.</li><li>The ability to quickly change the styling of the app, and move components based on customer input is critical. React Native allows faster iterations than any other platform.</li></ul><p>React Native combines fast execution with the best use of today’s developer ecosystem — making it a perfect platform for startups.</p><p>One feature of the very early Chop prototypes is an infinite scrolling list of cafes and restaurants, with estimated wait times at each location. It has a few characteristics:</p><ul><li>Our list item is a fixed width and height</li><li>We know the size of the list ahead of time</li><li>The list should scroll fast without jank or high memory use</li><li>The estimated wait time circle needs to be self-contained so it doesn’t dirty the entire list when there is a change</li></ul><p>Here is the demo of our infinite list implementation:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-l4zygVeZMs%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-l4zygVeZMs%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-l4zygVeZMs%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/119826f6e33e1bf996cd366bb1b6d5ae/href">https://medium.com/media/119826f6e33e1bf996cd366bb1b6d5ae/href</a></iframe><p>Here is the snapshot of CPU and memory usage through Xcode, both are pretty decent and more importantly the memory size stays consistent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*Esgh-ei6aXqeF47e." /><figcaption>CPU usage for non-stop 2 minute scrolling</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/0*uFYhbLrD-AaL9-3E." /><figcaption>Memory usage for non-stop 2 minute scrolling, via xCode</figcaption></figure><h3>iOS Infinite List Overview</h3><p>Let’s first take a quick look how this is done on iOS natively:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NWrrlbii3XJt4dFD." /><figcaption>iOS Infinite List Implementation</figcaption></figure><p>We are going to use a simplified version of the Chop ‘Explore List’ by holding five rows in memory, through <a href="https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/TableView_iPhone/AboutTableViewsiPhone/AboutTableViewsiPhone.html">UITableView</a>, in a single column list. ContentOffset is a point within the entire content space that defines where visible rendering starts. Here it says rows five, six, and seven are visible on the viewport.</p><p>Typically, if the user scrolls down, row seven will scroll off the screen, while row four will scroll in. UITableView accomplishes this by adjusting the contentOffset range. Soon, however, if you keep scrolling you will reach the edge of the content.</p><p>A few years ago, Apple introduced a technique to achieve infinite scrolling. You can watch their video describing it here: <a href="http://devstreaming.apple.com/videos/wwdc/2011/104/refmovie.mov">http://devstreaming.apple.com/videos/wwdc/2011/104/refmovie.mov</a> ( Safari only, at 4:26 mark).</p><p>Simplified, the first step is to re-adjust contentOffset to its original center state so the user won’t hit the edge. However, now row four is off the screen. To bring row four back to the screen you have to move all the rows down by one. If you do both operations in the same event loop it will be transparent to the user, and allow for infinite scrolling.</p><h3>React Native Implementation</h3><p>React Native is using a different optimization strategy, which Christopher Chedeau, explains well in this<a href="https://github.com/facebook/react-native/issues/499#issuecomment-87821298"> article</a>.</p><p>Essentially, React Native uses <a href="https://facebook.github.io/react-native/docs/listview.html">ListView</a> for infinite list but it has a number of drawbacks. The most important of which is that React cannot assume elements of the list are immutable, and therefore it has to keep a reference to every new element that is scrolled into view in order to perform change detection. Regardless of whether it does detach views when their offsets are out of the visible area, its memory representation of the list items remains in memory. Diffing gets more and more expensive over time as the list grows.</p><p>Let’s take a look at its implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXVppJ4w4iUY679I_bZZAA.png" /><figcaption>React Native Infinite List</figcaption></figure><p>If a user beings to scroll, row four becomes visible and row seven falls off the screen. React Native keeps both rows seven and eight in its memory in order to do the diff and change detection later. The list is essentially stateful. As the user continues to scroll, the component tree grows in size and doesn’t shrink. There’s a greater potential for memory loss depending on the quantity of rows in the list. ListView now includes an option to removeClippedSubviews, so what that does is keep native views in memory, but detached from the view hierarchy, which cuts down on unnecessary native views. However, this still retains references to all previously rendered rows.</p><p>Currently, <a href="https://medium.com/u/d5a707474bd2">Brent Vatne</a> also has an experimental windowed ListView for fixed height list: <a href="https://github.com/brentvatne/fixed-height-windowed-list-view-experiment">https://github.com/brentvatne/fixed-height-windowed-list-view-experiment</a></p><h3>Chop: Fixed Height Infinite List</h3><p>We took a slightly different approach to better suit Chop’s functionality.</p><p>Since our application uses fixed-height rows that all follow the same template, and we know the height of our viewable area, we settled on a design that treats the ScrollView’s child elements as immutable, except for the top-level elements in the array, and the height of the ScrollView’s interior. All other attributes of the list and its items will remain constant once created.</p><p>Here’s a look at Chop’s specific implementation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sjrMxGTrPRJUn1gjIbiy4g.png" /><figcaption>Chop’s Implementation — Fixed Postions</figcaption></figure><p>Chop’s infinite list can be thought of as a list of items with fixed positions. We designed it to use a sliding window to maintain a visible section of rows. When the user scrolls, the sliding window will move throughout the giant space the list is situated in, but the items will remain in their fixed absolute positions.</p><p>Because everything on the list is fixed in size, height and position, from React Native’s perspective there is no apparent diff. This means there is no need to hold more rows in the tree so there is no increase of the memory usage.</p><p>When the size of each item is known, you can compute the y-position of any element with a formula such as y-position = itemIndex * itemHeight. The body height of the ScrollView is always the highest y-position item plus its height.</p><h3>Example</h3><h4>Pseudo-code</h4><p><strong>OnScroll: How to update the renderModel</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5c039d14fdb369f54947fa854e2684c9/href">https://medium.com/media/5c039d14fdb369f54947fa854e2684c9/href</a></iframe><p><strong>OnRender: How to rerender the Infinite Scroll Widget</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e0823f06565b53d79988df7a7f6cabaf/href">https://medium.com/media/e0823f06565b53d79988df7a7f6cabaf/href</a></iframe><p>If you examine the demo video of the infinite list, you can see that it does render mutated data, namely the Wait Time bubble. However, we are not relying on React to do change detection in this case. Instead, we use an observable view model to detect changes to our data items, and force the Wait Time bubbles to become dirty and re-render. This scopes down the amount of state that has to be retained and diff’ed in the infinite list.</p><h3>The Need for a Fixed Height List</h3><p>The majority of the practical use cases out there simply deal with fixed-size items. (App Store app list, iTunes music list, Yelp restaurant list, Netflix movie list, Amazon product list, YouTube video list, or a geographical map with infinite bi-directional scrolling via fixed-size tiling, etc.). A variable-size list is often needed for user generated posts, typically in social network apps such as Facebook and Twitter. However it’s not the most common use case, and the implementation should not solely account for the worst case scenario.</p><p>Hopefully, a high performance fixed-height list can be standardized in the React Native platform to handle these use cases.</p><p><em>Special thanks to </em><a href="https://github.com/nktpro"><strong><em>Jacky Nguyen</em></strong></a><em> who was the architect of this design.</em></p><p>Try out Chop: <a href="https://goo.gl/g9M1EW">https://goo.gl/g9M1EW</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=336d010e51f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chop-technologies/fast-and-fluid-infinite-list-with-react-native-336d010e51f2">Fast and Fluid Infinite List with React Native</a> was originally published in <a href="https://medium.com/chop-technologies">Chop Technologies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>