<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alex Fishman on Medium]]></title>
        <description><![CDATA[Stories by Alex Fishman on Medium]]></description>
        <link>https://medium.com/@fishman?source=rss-eb4c8ee18457------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jdwyyaKG2fXM3dIvDctgIQ.jpeg</url>
            <title>Stories by Alex Fishman on Medium</title>
            <link>https://medium.com/@fishman?source=rss-eb4c8ee18457------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:39:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fishman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Is Bugsee Any Good?]]></title>
            <link>https://medium.com/@fishman/is-bugsee-any-good-1395be190fe2?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/1395be190fe2</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 23:19:41 GMT</pubDate>
            <atom:updated>2018-03-20T22:49:46.393Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Originally posted on </em><a href="https://www.bugsee.com/blog/is-bugsee-any-good/"><em>Bugsee Blog</em></a><em>.</em></p><p>You probably wonder whether you need <a href="http://bugsee.com/">Bugsee</a> and is it any good? Well, let me try to address these here.</p><h3>Video</h3><figure><a href="http://bugsee.com/demo"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nbWdw1lah5Bf0mvaCsZGzA.png" /></a><figcaption>Bugsee Dashboard</figcaption></figure><p>Have you ever wondered how your users get to a certain state in your app? Have you ever tried to recreate an intermittent bug? As developers, we deal with these types of issues on a regular basis. That’s where Bugsee can help.</p><p>Similar to a black box on an airplane, Bugsee records a video of user’s actions (and touches) at all times, and when a problem happens, you already have a recording of everything leading up to it. So no need to recreate anything. Ever again!</p><p>Bugsee is the <strong>only</strong> solution that allows app developers to continuously record high resolution 10 frames-per-second video of usage in live apps.</p><p>Now, there <em>are</em> other solutions out there on the market that claim they have video, but details <em>do</em> matter.</p><p>Some offer one-frame-per-second and low resolution solutions. Some require you to enable the video once you see the bug and then try to recreate the issue. Others slow down the UI or use private APIs that prevents you to ship the app to the App Store.</p><p>So yes, other solutions do offer video in their bug and crash reporting solutions, but they offer is simply not enough.</p><p>So how do we do it? At Bugsee we’ve developed our own IP methodology for recording video in live apps without slowing down the UI, following all App Store rules and adhering to all thread-safe protocols.</p><h3>Console Logs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYcPFyPJnCsEvW11fMAf8A.jpeg" /><figcaption>Bugsee shows console logs synced to the video</figcaption></figure><p>Developers often put a lot of logging directly into their code. This helps with debugging the problem that might arise in the future.</p><p>Bugsee continuously records all the console logs and shows them to you, synchronized to the video. This way, you’d know what the user had been seeing, where they were clicking and what your app was doing at the same time.</p><p>By the way, did you know that Bugsee is the <strong>only</strong> solution that records console logs in production apps on iOS?</p><p>Yes, on iOS 10 and iOS 11 as well. Yes, prints from Swift are also captured! If you see it on the Xcode console while debugging, you will see it captured by Bugsee.</p><p>Again, we developed our own IP to properly handle this.</p><h3>Network Calls</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kqBbIDbNrFLl-4UtCq8Icw.jpeg" /><figcaption>Bugsee shows network calls + body synced to the video</figcaption></figure><p>Sometimes issues in the app arise from an unexpected network call response. Wouldn’t it be useful to see all the network calls, responses and their bodies?</p><p>That’s exactly what Bugsee is doing — we record all the network calls, to yours and 3rd party servers, including the body of the request. Again, everything is synchronized with the video of the user’s actions.</p><p>And if there is a problem — you get to see whether Uber’s servers indeed came back with a proper response.</p><h3>System Traces</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXI13aeXsV1ZBoZ8PmWvCg.jpeg" /><figcaption>Bugsee shows all system and custom traces synced to the video</figcaption></figure><p>What if the phone’s network was off for a moment, and that was reason for your app’s crash? Or the user turned off the bluetooth chip? Or the app crashed in the background? Trying to guess and recreate the same scenario in the lab is quite unrealistic.</p><p>Every report by Bugsee includes dozens of system traces (60 seconds prior to the issue) — so you know what had happened right before the crash.</p><h3>Crash Symbolication</h3><figure><a href="http://www.crashprobe.com/ios/"><img alt="" src="https://cdn-images-1.medium.com/max/695/1*uGsfanCBTpSAgg3h8Xt3bg.png" /></a><figcaption>Bugsee is a top crash reporter</figcaption></figure><p>When we just got into the space, we thought crash symbolication is something you just have to do. We doubted there was anything to improve there.</p><p>But over time, we were able to beat everyone in the market in properly converting the crash reports into the actual file names and line numbers of the root cause.</p><p>Our direct competitor — HockeyApp (owned by Microsoft) runs a website <a href="http://www.crashprobe.com/ios/">CrashProbe</a> that compares the quality of various solutions’ symbolication skills (there are 22 types of different crashes on iOS on 2 platforms — 32 and 64 bits, so 44 different cases).</p><p>HockeyApp built that site because they were always number one on the list. Until we’ve submitted our results in Dec/2016 and got 3 additional crashes right. See our original post <a href="https://www.bugsee.com/blog/best-ios-crash-reporting-tool/">here</a>.</p><p>Afterwards, the game escalated and everyone tried to improve their symbolication and as of today, we <a href="http://www.crashprobe.com/ios/">share the crown</a> with HockeyApp with 39 correct symbolications.</p><h3>Integrations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/1*F9Mjyu8nphMEcRZ3agyhZQ.png" /><figcaption>Bugsee integrates with all your favorite tools</figcaption></figure><p>Every issue reported in Bugsee can be automatically propagated to your preferred bug-tracking and collaboration tools. We support 24 different vendors, including Slack, Jira, Asana, GitLab, Zendesk and many more.</p><p>We’ve noticed that our customers configure their bug-tracking tools and thus a simple push of a new issue is not good enough, so we’ve added <a href="https://docs.bugsee.com/integrations/recipes/recipes/">Custom Recipes</a> support. There you can write your own glue logic in plain Javascript for each field and configuration that fits your existing workflow, exactly how you need it to fit.</p><h3>How Do I Know What I’ll Need To Debug The Next Issue?</h3><p>You don’t have to worry about it. Bugsee will automatically track everything that is happening with your app at all times. And when time comes — we will have all the crucial data for you in an easy to use dashboard.</p><h3>Is It Easy To Add Bugsee To My Project?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*RVM0BRXjhO3LewEr6iAA2g.png" /></figure><p>You bet! It is one line of code. Literarily.</p><blockquote><strong>Bugsee</strong>.launch(token:”&lt;your_app_token&gt;”)</blockquote><p>More details here — <a href="https://docs.bugsee.com/sdk/ios/configuration/">iOS</a> and <a href="https://docs.bugsee.com/sdk/android/configuration/">Android</a>.</p><h3>Not Just Crash Reporting</h3><p>What if the Beta user wants to report an issue with the app? What if the Product Manager identified an issue with the app while at lunch?</p><p>When Bugsee is installed, shake or screen-shot the phone and we will receive a report of video, network and logs leading up the problematic moment, with all system information (version, build, etc).</p><p>Or wonder what the user did to get to a certain screen? Use our APIs to trigger an upload of our video report, without crashing the app or prompting the user. Super useful in UI/UX research, as well as identifying unexpected code execution flow.</p><h3>What About Privacy?</h3><p>Privacy is crucial aspect of everything we do these days on the internet. We get it.</p><p>Bugsee will <strong>automatically</strong> remove all the passwords and credit cards from the recording, while still on the phone. So nothing is ever hitting our servers.</p><p>Plus, we offer a range of APIs to control filter other PII in <a href="https://docs.bugsee.com/sdk/ios/privacy/">video, network and logs</a>.</p><p>Also, we offer reduced resolution recording mode, where the recorded video is sufficient to understand the flow, but the text is illegible. Our customers in the medical space are using this option.</p><h3>Gartner Cool Vendor Recognition</h3><figure><a href="https://www.gartner.com/doc/3706719/cool-vendors-devops-"><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ABp1X-0IvzlHN-xbhd_VKw.png" /></a><figcaption>Bugsee was named Cool Vendor by Gartner in 2017</figcaption></figure><p>Bugsee was recognized by Gartner as a <a href="https://www.gartner.com/doc/3706719/cool-vendors-devops-">Cool Vendor</a> in 2017 in DevOps category.</p><p>We are proud to share a position on that list with our friends at LaunchDarkly and with the titan named Slack.</p><h3>What Others Are Saying About Bugsee</h3><p>Coverage by <a href="https://www.inc.com/john-rampton/how-to-fumigate-those-pesky-mobile-app-bugs.html">Inc Magazine</a>.</p><p>Best Crash Reporting by <a href="https://sdtimes.com/appsee/best-crash-bug-reporters%E2%80%8A/">SD Times</a>.</p><p>Bugsee Customer Reviews on <a href="https://www.g2crowd.com/products/bugsee/reviews">G2 Crowd</a>.</p><h3>We Do Not Use or Sell Your Data</h3><p>We do not analyze, aggregate or sell your data.</p><p>Your data is <strong>your</strong> business.</p><p>Our business is to provide you with the top notch bug and crash reporting tool. And that’s all.</p><p>We do not monetize your users’ data in any shape or form. Period.</p><h3>What Platforms Do We Support?</h3><p>All major ones:</p><p><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for OS Swift and Objective-C</a><br><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for Android</a><a href="https://docs.bugsee.com/sdk/android/installation/"> (version 5 and above)</a><br><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for Unity</a><br><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for X</a><a href="https://docs.bugsee.com/sdk/xamarin/installation/">amarin</a><br><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for C</a><a href="https://docs.bugsee.com/sdk/cordova/installation/">ordova</a><br><a href="https://docs.bugsee.com/sdk/ios/installation/">Bugsee for </a><a href="https://docs.bugsee.com/sdk/react/installation/">React Native</a></p><p>Using something else? <a href="/service/mailto:support@bugsee.com">Let us know</a> and we’ll look into it ASAP.</p><h3>We Want Your Business!</h3><figure><a href="/service/mailto:alex@bugsee.com"><img alt="" src="https://cdn-images-1.medium.com/max/320/1*QWxz8WlpsitxBTSwo-AMlA.jpeg" /></a><figcaption>Alex Fishman, Founder/CEO Bugsee</figcaption></figure><p>We are a small company and thus we will work around the clock to win your business.</p><p>Try us.</p><p><a href="/service/mailto:alex@bugsee.com">Email me</a> directly with your questions or feature requests.</p><h3>It’s Free To Try And Not Expensive To Use</h3><p>We do <strong>not</strong> charge per event, per bug, per app, per seat or team-member. We <a href="http://bugsee.com/pricing">charge</a> only by how many active devices Bugsee is deployed on. Which we believe is fair — we scale with your business.</p><p><a href="http://bugsee.com/signup">Try Bugsee free for 30 days.</a></p><h3>Still Have Questions?</h3><p>You check our demo <a href="http://bugsee.com/demo">here</a>.</p><p>OR</p><p><a href="/service/mailto:alex@bugee.com">Email me.</a></p><p>OR</p><p><a href="https://calendly.com/fishmanalex/bugsee">Schedule a meeting with me.</a></p><h3>How This Post Came About?</h3><p>I once saw GitLab’s page named <a href="https://about.gitlab.com/is-it-any-good/">“Is It Any Good?”</a>. It says:</p><blockquote>When people first hear about a new product they frequently ask if it is any good. A Hacker News user <a href="https://news.ycombinator.com/item?id=3067434">remarked</a>: ‘Note to self: Starting immediately, all raganwald projects will have a “Is it any good?” section in the readme, and the answer shall be “yes.”’.</blockquote><p>Same as GitLab, we too were inspired by that and decided to add a similar post here.</p><p><em>Thank you,<br>Alex Fishman<br>Founder/CEO Bugsee</em></p><p>PS: Oh yeah, and we’re funded by <a href="http://k9ventures.com/">K9 Ventures</a>, the same guys who brought you Twilio, Auth0, Carta (eShares) and Lyft.</p><p><em>Disclaimer: The Gartner Cool Vendor Logo is a trademark and service mark of Gartner, Inc., and/or its affiliates, and is used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1395be190fe2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customers vs. Users: Why Word Choice Matters]]></title>
            <link>https://medium.com/startup-grind/customers-vs-users-why-word-choice-matters-27e660e5db56?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/27e660e5db56</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 10:31:36 GMT</pubDate>
            <atom:updated>2017-06-20T22:48:59.130Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*Jwux5dhle0Qa_B7vYP9Q8w.jpeg" /><figcaption>Image Credit: multiz12/Shutterstock</figcaption></figure><h4>Because it does matter.</h4><p>When you’re a startup founder, you get a lot of questions. <em>What’s your traction? Are you technical? When do you expect to implode and go back to working at a bank? </em>Most of them are easy to answer. But there’s one that I get pushback on. It usually goes like this:</p><p><em>“Alex, how many customers do you have?”<br>“We have a few hundred, but most aren‘t paying yet at this point.”<br>“Those aren’t customers, Alex. Those are users.”</em></p><h4><strong>Are they? I don’t think so.</strong></h4><p>If you’ve done everything right, your product should be growing. If you’re lucky, then it’s growing well and everyone is excited about what you do and where you’re headed and you have plenty of non-paying customers. If you’re really lucky, you have hundreds of paying customers.</p><p>As a startup founder, I’ve had many conversations with my <a href="http://bugsee.com/">product’s</a> current and potential investors, friends and business partners, press and analysts, and so on. During these conversations, I’ve used the words “customers” and never used the word “users.”</p><blockquote>Why? Because users are just customers waiting for an invoice and, ultimately, the term “users” is disrespectful.</blockquote><p><strong>Here is my rationale:</strong></p><h3>Support</h3><p>Our customers rely on us to help them when they are having trouble debugging their apps. They send us <em>customer inquiries</em> and we provide them with <em>customer support</em>. We strive to maximize <em>customer satisfaction</em>. Calling them “users” is inappropriately dismissive and sends the wrong message to our team.</p><p>Everyone who walks through the (virtual) door is a customer. The only people who turn their nose up at folks who are just browsing are luxury retailers and fools.</p><p>When I send an email to my team, I don’t write “User 445545 can’t figure this out.” I write, “Our customer, Jack Smith, is struggling with our dashboard.” Again, Jack will appreciate the help. And when the time comes, we can convert him in a heartbeat.</p><h3>But some startups do have users!</h3><p>OK, I’ll accept that premise. Facebook, for example, has both users and customers. Their users (you and I) and advertisers (their customers) are two distinct groups, as they use different products that dictate different requirements.</p><p>That’s not the case for us. We offer only one product to our customers. We don’t split them down the middle. Facebook <em>sells</em> its users to its customers. We don’t sell anyone to anyone.</p><h3>Scale</h3><p>Customers are usually measured in hundreds or thousands, depending on your business. Users, on the other hand, are often measured in millions. Calling our customers, albeit non-paying ones, “users” might anchor the listener in the wrong scale.</p><p>And you <em>know</em> that those millions of users aren’t paying and probably never will. All of Twitter’s users are essentially undifferentiated strains on Twitter’s infrastructure. We don’t think of customers in that way.</p><p>That’s why I always use the word “customers” when I talk about our company’s stats.</p><p>Obviously, one might assume that having customers is equal to having revenue, and therefore it’s essential to properly qualify the answer to the question, usually by mentioning total revenue. This way I’m not misleading the listener.</p><p>But I refuse to separate the two. It doesn’t make any sense. It’s unkind, not smart, and generally bad form. Anyone using your site is a customer who deserves attention. If you truly believe that, you will never go wrong.</p><h3>Customers are friends, not food</h3><p>The bottom line? It’s simple: Even if you plan to monetize the user base directly and haven’t flipped the switch, those people using your platform are your non-paying customers.</p><p>They are an essential cohort that helps test and later monetize your product. They are not eyeballs. They are not users. They are human beings who like your product and can help you succeed. They deserve to be called customers because they deserve your respect, your attention, and your appreciation.</p><blockquote>Alex Fishman is a Founder/CEO of <a href="http://www.bugsee.com/">Bugsee</a>, a bug and crash reporting tool for mobile app developers. Follow him on Twitter: <a href="https://twitter.com/fishmanalex">@fishmanalex</a>.</blockquote><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*sg1PGrUIRQvIDH7bb2OY0A.jpeg" /></a></figure><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*vqmKsL3ve0gkGU-R39Nk-A.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N1UpkDFpA5UrRxen2NHxtw.jpeg" /></a></figure><p><em>Originally published on </em><a href="http://venturebeat.com/2017/02/19/customers-vs-users-why-word-choice-matters/"><em>VentureBeat</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27e660e5db56" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/customers-vs-users-why-word-choice-matters-27e660e5db56">Customers vs. Users: Why Word Choice Matters</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unexpected consequences of using AI meeting schedulers]]></title>
            <link>https://medium.com/startup-grind/unexpected-consequences-of-using-ai-meeting-schedulers-43bd16cb14d7?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/43bd16cb14d7</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 16:53:56 GMT</pubDate>
            <atom:updated>2017-04-21T16:56:18.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m13n-rBdC5GtBhHN9nLqRQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*GURkhCs8FM1wQEwqIieqzA.jpeg" /><figcaption>AI bots are cute, but can they pass the Turing Test?</figcaption></figure><p>True AI is great. You can use it to predict system errors, drive cars across the country, and stay healthy, wealthy, and wise. But please keep it out of my inbox.</p><p>AI assistants are all the rage and we all have seen them by now — “Hi, I’m Sally, Joe’s AI assistant. Let’s find some times when you two can meet!”</p><blockquote>These chipper bots are fun, but if you’re using them daily, then you might be missing out on some important opportunities.</blockquote><p>The bottom line: AI assistants are too dumb to trust right now and they’re too dangerous to ignore. I’ve tried a few of them and here’s my take.</p><h3>Unexpected Consequence 1: AI assistants may save you time, but they waste mine</h3><p>It’s that simple. These tools aren’t as smart as they claim. They don’t have the human ability to interpret subtleties in our conversation. For example, if you and I already agreed on having a Skype call for our meeting, your “secretary” will continue to insist on your preferred coffee shop.</p><p>I’ve seen this again and again and I’ve missed meetings this way simply because the AI didn’t get my phone number and instead told me to go to Blue Bottle in New York, when I live in Bay Area.</p><p>The takeaway? AI needs context quickly or it will fail. And when you use an AI without understanding its limitations, you will also fail.</p><h3>Unexpected Consequence 2: You miss a golden opportunity to connect</h3><p>A week ago someone introduced me to a business partner because they felt it would be mutually beneficial. When I emailed the prospect, a bot answered. Why miss out on an opportunity to connect?</p><p>I replied that AI destroys a lot of interaction, and we started chatting on Skype. If a robot had continued to interfere, we would’ve never spoken and she wouldn’t be working with Bugsee right now.</p><p>Direct interactions with humans can tell you a great deal. While scheduling the meeting, we get to see whether each of us is quick or slow with their email. We get to see who replies over the weekend. We get to figure out who is quirky, weird, or funny. We also get to see if we are brief emailers or story tellers.</p><p>In short, we get to understand each other as <strong>humans</strong>. These are some lines from our back and forth:</p><p><em>— Oh, sorry, I must reschedule, my kid is sick.<br> — No problem, mine came back from school with a nasty bug last week and shut down the entire family for a few days :) How old is your kid?</em></p><p><em>— I can’t do 9am, interviewing a digital agency then. How about 10am?<br> — That works. Would love to hear your experience interviewing there. We’re looking into that too these days.</em></p><p>These touch points are invaluable in building lasting business and human relationships. Don’t skip them!</p><h3>Unexpected Consequence 3: You’re making me talk to a box, and it’s unpleasant.</h3><p>Remember the feeling last time you got an email that said:</p><p><em>“Dear Michael from Acme, Inc.”</em></p><p>Remember how you looked at that “<em>Inc”</em> part? Without reading any further, you knew it was a sales automation email that got your company name from a database. <strong>No one likes receiving emails from machines.</strong></p><p>Similarly, no human would ever include all the junk in this line:</p><p><em>“Alvin likes Voyageur du Temps, 288 1st St, Los Altos, CA 94022, United States”</em></p><p>Why do you make me talk to a fucking robot? I get enough of that when I call Comcast, where it’s often not even obvious when you get a human. The lack of real intelligence (or compassion) on the other end of the line is usually consistent throughout the call, making it a smooth transition from an IVR to an agent. But that deserves a separate post…</p><p>Ever talked to a chat bot? Remember that feeling of banging a wall with anything that is remotely non-standard and wondering — am I not worthy of a human time of that pretentiously luxurious brand?</p><p>Oh yeah, and its pretentiously fake textbook politeness. That’s always a treat. Maybe I’m grumpy, but come on!</p><h3>Unexpected Consequence 4: Implied confidentiality breach</h3><p>After our initial email exchange, we might’ve been talking about something sensitive or confidential. And now, with this AI, you’ve added a 3rd party to our thread.</p><p>You and I, both know that AI bots are 90% human and 10% automatic. They have to be, as the technology just isn’t there yet.</p><p>The third party may or may not analyze the email thread along with my personal information. They may or may not aggregate and store it. They may or may not sell it or use for other purposes. They may or may not cover it in their terms of service and privacy policy… which I don’t have the time to review.</p><blockquote><strong>And most importantly, I’ve never given you a consent for any of this. But it’s too late, because you’ve violated the inherit trust of private communication.</strong></blockquote><h3>Bottom Line: What message are you sending?</h3><p>When you use a dumb robot, you’re telling me that your time is more valuable than mine. If you’re indeed a busy individual, hire a professional assistant that costs real money. Otherwise, don’t fake it with a $50/month pseudo-secretary.</p><p>Also, if a bot is the one that scheduled our meeting time, there is an increased chance you will actually miss it. Again, wasting my time. Nothing beats a personal commitment.</p><p>When Hotmail was born, the founders followed <a href="https://www.youtube.com/watch?v=g0EE8bslg78">Tim Draper’s suggestion</a> to add a footnote to every email “Get your free email at Hotmail”. It worked beautifully then, but it isn’t cool anymore.</p><p>Yet, you’ve decided that it’s ok to send me emails that end with a similarly spammy message, promoting a 3rd party service and tracking my clicks. I don’t need to see “Sent by Stella.ai, my digital assistant” at the bottom of every email.</p><p>Don’t get me wrong, I understand the need to improve productivity. However, when forcing a tool on your business partners and customers, think about how it may affect <strong>them</strong> and consider the message you’re sending by doing so.</p><p>Still unconvinced? I want you to try <a href="http://boomerangcalendar.com/">Boomerang Calendar</a>, which is a system that I used and is much more suitable for the scheduling function. It shares your calendar availability with your prospects.</p><p>You can set a time slot with a single click and if your schedule changes, it automatically updates your availability. There’s no chirpy AI, no weird back and forth, and your data is secure. It’s the least you can do for the people you email.</p><blockquote>Alex Fishman is a Founder/CEO of <a href="http://www.bugsee.com/">Bugsee</a>, a bug and crash reporting tool for mobile app developers. Follow him on Twitter: <a href="https://twitter.com/fishmanalex">@fishmanalex</a>.</blockquote><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*sg1PGrUIRQvIDH7bb2OY0A.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N1UpkDFpA5UrRxen2NHxtw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43bd16cb14d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/unexpected-consequences-of-using-ai-meeting-schedulers-43bd16cb14d7">Unexpected consequences of using AI meeting schedulers</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Your “Falafel Shop”?]]></title>
            <link>https://medium.com/startup-grind/whats-your-falafel-shop-efa0c7c1e541?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/efa0c7c1e541</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Fri, 24 Mar 2017 12:32:01 GMT</pubDate>
            <atom:updated>2017-03-24T16:40:09.448Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*sw3aA03v8RA59fJOZySmfA.jpeg" /></figure><h4>Make your money, but don’t get burned doing work you’ll resent</h4><p>In 1997 I joined a small, publicly traded company called Zoran. A seemingly unimportant decision for an 18 year old. However, it later defined my entire career path, through which I’ve met many of my closest friends, including my wife.</p><p>Back then, I was working on a yet unborn project named COACH — Camera On A CHip. The novel idea where you have a single chip solution to operate the entire hardware of a digital camera (<a href="https://medium.com/startup-grind/camera-killing-smartphones-and-their-killer-cameras-70ff4757b7ef#.e4hdx7byj">remember those?</a>). I even remember my very first task — write the quickest log2 function in assembler on a 16-bit microprocessor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*4lL_KGBgNIDtEL77G1DZ6g.jpeg" /><figcaption>COACH 12 by Zoran, 2009</figcaption></figure><p>Our CEO, Levy Gerzberg, believed in the idea and poured enormous amount of resources and trust into the team. He believed that COACH will eventually be used by every camera brand out there. And Levy was right — we made it into almost every brand, with the notable exception of Canon. Zoran was the Intel of digital cameras.</p><p>However, as you can imagine, the first several years were painful and slow in terms of customer acquisition, revenue and profits. So one day, circa 2000, our COO sent an email to the team, asking for ideas, where else COACH can be used.</p><p>Remember, this was before smartphones, before Skype, before backup cameras in cars, it was webcams early days and the security world was still entirely prewired in analog.</p><p>So I thought through a few ideas and potential revenue streams, put myself together and went to knock on the COO’s door.</p><h3>The Big Day</h3><p>He smiled and welcomed me to his office. I sat down and outlined my best idea. I honestly don’t remember what it was now, but I do remember his verbatim response. With a perplexingly innate Israeli frankness, he said:</p><blockquote>— Alex, that’s a stupid idea. Zoran also can make falafel and make money, but we don’t!</blockquote><p>His swift response was as effective as stubbing my toe against the bed — painful at first, but quickly teaches a valuable lesson:</p><blockquote>Is whatever you’re considering more satisfying than running a falafel shop?</blockquote><p>If not, then it’s a stupid idea.</p><p>Don’t get me wrong. Not that there is anything wrong with running a falafel shop. If that’s what you want to do and enjoy doing — running a falafel shop will be very satisfying. So it’s not an absolute measurement everyone needs to compare all their ideas against.</p><p>The point is that each one should have their own “falafel shop” to compare to. There’re many legitimate ways to make money, some are less and some are more efficient when it comes to ROI. Yet passion, experience, core competency and overall goals should be always considered when deciding to embark on a new venture.</p><blockquote>As for running a falafel shop, it’s actually easier than you think. All you need to have a packed falafel shop is a solid recipe and more importantly, to remember to change the cooking oil <em>every day</em>. As proof for it, go stand in a long line at <a href="http://www.falafelstop.com/">Falafel Stop in Sunnyvale</a>. (I’m not getting paid for this, I’m just a fan.)</blockquote><blockquote>Alex Fishman is Founder/CEO of <a href="https://www.bugsee.com/">Bugsee</a>, a bug and crash reporting tool for mobile app developers. Follow him on Twitter: <a href="https://twitter.com/fishmanalex">@fishmanalex</a>.</blockquote><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*iq0EKuOUS52AtOW_RSKNxA.jpeg" /></a></figure><figure><a href="https://europe2017.eventbrite.com/?aff=mediumfooter"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*sg1PGrUIRQvIDH7bb2OY0A.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/325/1*N1UpkDFpA5UrRxen2NHxtw.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efa0c7c1e541" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/whats-your-falafel-shop-efa0c7c1e541">What’s Your “Falafel Shop”?</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thank you, Google!]]></title>
            <link>https://medium.com/@fishman/thank-you-google-bd9dbd27a71c?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9dbd27a71c</guid>
            <category><![CDATA[thank-you]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Tue, 07 Feb 2017 23:38:34 GMT</pubDate>
            <atom:updated>2017-02-08T22:21:14.011Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bL7nEtyJP1a7TsAAZWQePg.png" /></figure><p>For whatever reason I woke up today thinking about all the Google services I use regularly in my personal and business routines. Until I thought about it, I didn’t even realize how much I rely on Google in my day to day.</p><p>The list quickly grew to 30 items. Some of which are free and some I’m gladly paying for. Some I use exclusively (such as Search) and some in conjunction with other alternatives (such as Adwords).</p><h3>The Google List</h3><p>—Google Search<br> — Google Chrome<br>—Google Gmail<br> — Google Calendar<br> — Google YouTube<br> — Google Images<br> — Google News<br> — Google Alerts<br> — Google Chromecast<br> — Google DNS<br> — Google Patents<br> — Google Trends<br> — Google Maps and Waze<br> — Google Earth<br> — Google Photos and Picasa<br> — Google Analytics<br> — Google Finance<br> — Google Drive, Docs and Forms<br> — Google Hangouts <br> — Google Voice<br> — Google Translate<br> — Google AdWords<br> — Google Domains<br> — Google WiFi at Starbucks<br> — Google URL Shortener<br> — Google Sites<br> — Google Authenticator<br> — Google reCaptcha<br> — Google Speed Test<br> — Occasional lunch with Google comrades at GooglePlex</p><p>Once the list was complete, it became clear how indispensable Google is as a resource in today’s life. Since it’s easy to forget that, I felt compelled to write down a quick shout out.</p><blockquote>Thank you, Google! You guys make incredibly powerful and useful tools, which are either free or dirt cheap. Can’t imagine the world without them.</blockquote><p>PS: One notable omission from the list is Android. That’s because Apple was first to hook me on their back-button-less phones.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9dbd27a71c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bugsee is on Product Hunt Today]]></title>
            <link>https://medium.com/@fishman/bugsee-is-on-product-hunt-today-2b98f9c0ced2?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b98f9c0ced2</guid>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[product-hunt]]></category>
            <category><![CDATA[product-launch]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Tue, 24 Jan 2017 08:15:41 GMT</pubDate>
            <atom:updated>2017-01-24T08:15:41.444Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*28sGPc4xUTZ4Ub0wyyGu5A.png" /><figcaption>Bugsee on Product Hunt</figcaption></figure><p>I’m thrilled to announce that Bugsee is on <a href="https://www.producthunt.com/posts/bugsee-2">Product Hunt</a> today. Can’t wait for the Product Hunt community’s feedback and thoughts.</p><h3>Why Today?</h3><p>Last year we won the <a href="https://www.bugsee.com/blog/best-ios-crash-reporting-tool/">#1 crash reporter</a> award by <a href="http://www.crashprobe.com/ios/">CrashProbe</a> — the ultimate benchmark for mobile crash reporters. And that’s before our video, network and logs leading up to the crashes. And therefore, we’ve decided — it’s time!</p><figure><a href="https://www.bugsee.com/blog/best-ios-crash-reporting-tool/"><img alt="" src="https://cdn-images-1.medium.com/max/682/1*Y5WZhMbtDzm95_VcGbNaIw.png" /></a><figcaption>Bugsee wins the #1 crash reporter for iOS award</figcaption></figure><h3>Bugsee is, therefore I thank</h3><p>I would like to thank our early customers, our network and our investors that supported us throughout this past year. We would not have made it to today without your patience, support and candor during our early months.</p><p>I would also like to thank our incredible engineering team, working around the clock, defying all odds in building the previously thought impossible feature set. Every day, I’m humbled by your achievements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/180/1*T1qT4c2kI289YXh366oeZQ.gif" /><figcaption>Bugsee is, therefore I thank</figcaption></figure><p>I’m proud of what Bugsee team has done so far and looking forward to the year ahead of us. Exciting!</p><p>Thank you!<br>Alex Fishman</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b98f9c0ced2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Price Your Product or Service]]></title>
            <link>https://medium.com/startup-grind/how-we-settled-on-bugsee-paid-plans-421abbca9058?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/421abbca9058</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[pricing-strategy]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Fri, 16 Dec 2016 19:03:46 GMT</pubDate>
            <atom:updated>2016-12-28T16:26:42.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJcSofvMAZEpTqu-PQIYLQ.jpeg" /></figure><h4>Hard learned lessons from building our latest SaaS product</h4><h3>TL;DR</h3><ul><li>Roll out fully functional service for free to learn from early customers.</li><li>Find a role model for your pricing structure, ideally from your space.</li><li>Avoid pricing around factors that may hinder growth and/or usage of your product within customer’s organization.</li><li>Launch, learn and iterate.</li><li>Grant early customers a special early-adopter plan. They deserve it.</li><li>Figuring out pricing is longer than you think. Start early!</li></ul><p>When we’ve started <a href="http://bugsee.com/">Bugsee</a>, our goal was always to make the service as frictionless as possible. It starts from integration: all our features drop in by adding just <em>one line of code</em>. You don’t need to think ahead of time what info you might need when you debug the next bug or crash.</p><p>Therefore, we didn’t want the lingering thought of payment to be prohibitive in trying a yet untested product. So we decided to roll out a fully functional service with no strings or dollars attached.</p><p>Oh boy, it was a right decision — everything we learned, including how to actually sell our product, was learned during this session. But before we go on — thanks once again to the customers that imparted these lessons, and for the trust and patience during the first few months. As a small token of our appreciation, you all received a special free tier.</p><p>Last month we’ve officially graduated and became a paid service. Today I wanted to share with you our thought process that led us to the current model, as well as all the contemplation we went through to get there.</p><h3><strong>Pricing Exploration</strong></h3><p>When we started discussing our pricing strategy, we’ve underestimated how difficult it’ll be to come up with the right plan. It probably took us good 6–8 weeks of deliberation to converge on the current model.</p><p>Our number one goal was to make our pricing structure to be super simple and easy to understand. We did not want to have a feature matrix that complicates the buying process, forcing buyers to calculate out which features they actually need — and if they’re worth the associated price tag.</p><p>The first business model we’ve eliminated from the get-go was to have a free product and sell the collected user behavior information to third parties. It wasn’t the right approach for us — because we actually care about our customers’ data and privacy.</p><p>We also wanted to ensure we have a fully functional free tier if you’re just interested in trying things out — or if you’re just starting out at the very beginning of your product development and aren’t ready to pay for tools yet.</p><p><em>We used Atlassian’s </em><a href="https://www.atlassian.com/software/jira/pricing?tab=cloud"><em>pricing page for Jira</em></a><em> as our guiding North Star and tried to model after it.</em></p><p><strong>Then the question came — what do we tie our pricing to?</strong></p><p>In case of Jira, it is the number of team members that have access to their dashboard. We didn’t feel it would be correct for us to do the same.</p><h4>There’re two main reasons for that:</h4><ul><li><strong>Size of the organization does not always properly reflect its stage in product development.</strong> There are many small businesses/startups that have a dozen-sized teams with no product yet, or their product simply lacks a meaningful traction yet. On the other end of the spectrum— WhatsApp had only 55 employees supporting hundreds of millions of users when FB acquired them for $19B.</li><li><strong>Charging per seat also forced added hesitation into adding new hires to Bugsee </strong>— <em>is that user worth the extra $x/month?</em> We didn’t want that. We wanted the entire organization to have access to Bugsee, similar to Heap Analytics.</li></ul><p><em>If not per team member, then how do we charge?</em></p><p><strong>Another proposal we’ve contemplated was to charge per app or per project. </strong>The problem with it is that many developers like to try a small projects here and there — say, a test app, or have a separate staging build of the app. Charging per project would prohibit the exploration of this sort.</p><p><strong>Another option was to charge per a reported bug. </strong>Obviously, that was immediately turned down, as we didn’t want anyone to think twice before reporting a bug. <em>Is this issue worth an extra $0.00x?</em> Plus, it wouldn’t work for anyone trying to start something in their garage. Too cost prohibitive to report many bugs one usually has in the early days of a project.</p><p><strong>So the only factor that we were left with was charging per number of devices Bugsee is deployed on.</strong> The problem was that even in a moderately successful app, its number of users usually trumps the number of devices the app is being tested on in-house.</p><p>So we had to introduce two different kinds of devices we are tying our pricing to…</p><ul><li><strong>Test Devices</strong> — the devices you run your dev and test builds. If you test on your phone and your iPad — it’s free. Large test deployment for your app (more than 10) are paid.</li><li><strong>Live Devices </strong>— your active users of the app. And again, if you just released your app, it’s free. We’ll charge you only when your grows to above 10K MAU.</li></ul><h3>Everything is Obvious in Hindsight</h3><p>It might look obvious now, but isn’t it always the case? You go through number of different options until you land on something that actually seems like a perfect solution, that addressed all our needs:</p><ul><li>Simple and easy to understand pricing model. No feature matrix!</li><li>If you’re just starting — you get a full functional product for free, unrestricted by time (no trial period).</li><li>When your business grows — we grow with you.</li><li>Everything else in the system is unlimited — number of apps, bugs and teammates. So go ahead, create a test app, add your boss to the team — everything is included.</li></ul><h3>Now we wait to learn more</h3><p>So that’s it. This is our quick summary of our journey exploring the right business model for Bugsee. Similar to anything in a startup, our business model is a continuous refinement process. Only our customers have the answer to whether we got it right or not. So now we wait…</p><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Mro-phkgJv4rZQ223OYosA.jpeg" /></a></figure><figure><a href="https://startupgrind2017.eventbrite.com/?aff=readon"><img alt="" src="https://cdn-images-1.medium.com/max/326/1*guZPyRXCP37UGWfWDX3bnw.jpeg" /></a></figure><figure><a href="http://startupgrind.com/chapters"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*aryi71qRq78ClpWKu2be2w.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=421abbca9058" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/how-we-settled-on-bugsee-paid-plans-421abbca9058">How to Price Your Product or Service</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[App development, bug reporting, and more in this GeekSpeak podcast with Bugsee]]></title>
            <link>https://medium.com/@fishman/app-development-bug-reporting-and-more-in-this-geekspeak-podcast-with-bugsee-901265f0fd05?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/901265f0fd05</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[podcasting]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Wed, 16 Nov 2016 22:34:08 GMT</pubDate>
            <atom:updated>2016-11-16T22:34:08.605Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*3Cq7zM7rQU8Zb5jUZQYDtw.jpeg" /><figcaption>Bugsee at GeekSpeak</figcaption></figure><p>Back in early September, <a href="https://medium.com/u/deba35f0534b">Lyle Troxell</a> from <a href="http://geekspeak.org/">GeekSpeak</a> invited <a href="https://medium.com/u/bbc5dda1559e">Dmitry Fink</a> and myself to his ad-hoc studio at Netflix in Los Gatos to record an <a href="http://geekspeak.org/shows/audio/GeekSpeak_2016-11-02.mp3?1478476415">episode</a> for his podcast.</p><p>Interestingly enough, we didn’t realize we were actually going to do the recording then. We thought we were just meeting Lyle to discuss a future interview. Imagine our surprise, when we walked into a regular Netflix conference room and saw Lyle setting up his recording equipment.</p><p>We had a fantastic time chatting with Lyle. We covered a wide variety of topics. We started with the importance of titles in a startup, then went to talk about our early days working in embedded space with cameras, DVDs and phones. Then talked through our <a href="http://entrepreneurs.maqtoob.com/my-cofounder-said-i-love-what-were-doing-and-we-shut-down-our-startup-80d5e710c2b2">previous adventure</a> and how it eventually, with a bit of help from Goldman Sachs, led us to the birth of <a href="http://www.bugsee.com/">Bugsee</a>.</p><p>We covered a range of technical topics, such as recording video in production apps, its impact on UI and phone’s CPU, full network communication logging, why we use AWS and method swizzling in SWIFT.</p><p>We also touched upon some of the business challenges at the end.</p><p><a href="http://geekspeak.org/shows/audio/GeekSpeak_2016-11-02.mp3?1478476415">Take a listen</a> to what came out of it. There was another guest, Stu Sjouwerman from KnowBe4, on this episode, thus our part starts at minute 17:40.</p><p>Also, if you prefer to read through the interview instead, you can find a full transcript of our conversation <a href="http://www.bugsee.com/blog/app-development-bug-reporting-geekspeak-podcast-bugsee/#transcript">here</a>.</p><p>Thank you, Lyle!</p><p>PS: If you like GeekSpeak’s work, please consider <a href="http://www.patreon.com/GeekSpeak">supporting them</a>.</p><p>PPS: If you want <a href="http://twitter.com/BugseeHQ/status/779112802120105985">these</a> Bugsee stickers — ping me, will be happy to ship you a few.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=901265f0fd05" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 3: The Deciding Deep Dive]]></title>
            <link>https://medium.com/startup-grind/the-deciding-deep-dive-5fbf3d7baf30?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fbf3d7baf30</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Fri, 28 Oct 2016 19:57:09 GMT</pubDate>
            <atom:updated>2016-12-15T18:22:06.344Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmVPxZzRQZFjQepQiipAlQ.jpeg" /><figcaption>“We had what alcoholics refer to as a ‘Moment of Clarity.’” Pulp Fiction</figcaption></figure><h4>Our final chapter in shutting down a company and starting it right back up.</h4><p>In my previous two blogposts, I’ve covered how Dmitry Fink and I <a href="https://medium.com/@fishman/my-cofounder-said-i-love-what-were-doing-and-we-shut-down-our-startup-80d5e710c2b2">had shut down our startup</a> and then described <a href="https://medium.com/startup-grind/a-post-about-post-post-mortem-a2c6fcf3f02#.mlytbonla">our efforts to reboot with the remaining capital</a>. The last blogpost ended with:</p><p>“<em>One of the azimuths we explored was the specific challenges we had faced at our first company. We looked at the actual pains we had experienced and studied potential solutions. One of these deep dives led us to build </em><a href="http://bugsee.com/"><em>Bugsee</em></a><em>.”</em></p><p>This is my third and last post in the Pulp Fiction themed <em>restart trilogy.</em></p><h3>The final stretch of the journey</h3><p>The mobile apps at our previous venture had bugs. These bugs caused a range of unexpected behaviors, such as a broken animation, a mispeled [sic] text, a missing image or a counter-intuitive UI.</p><p>Reporting these bugs to our dev team was often a challenge. So Dmitry and I tried to recall our typical flow.</p><p>Once I saw a bug on my latest version of the app, I would first take a screenshot. Quite useless in the case of a sloppy UI transition, but what else could I do?</p><p>Then I’d attempt to reproduce the steps leading up to the problem. Of course, the intermittent bugs were often impossible to recreate. How could I know that clicking on a specific icon four screens ago caused this problem? What if the problem was caused by a temporary connection loss?</p><p>Then I would email our dev team with the pieces of collected data. While some issues were easy to describe, others were too complex to be put in words. You just had to be there.</p><p>Then the dev team would come back with tons of additional questions — Which build? The one from yesterday or today’s AM? Which iOS? Was the phone on WiFi or 3G? What did you do right before you got that screen?</p><p>As some of our developers were in a different time zone, these back-n-forth emails would sometimes take several days. Often we’d get to the bottom of the problem, but sometimes we would end with “well, just put it in Jira, we’ll be watching for it”. There simply wasn’t enough info to root cause the issue.</p><p>On top of that, our production apps also crashed on occasion. The reported call stack wasn’t always sufficient to understand the condition that caused the crash. So we faced a similar conundrum. What <em>exactly</em> did the user do to get to that particular case? What else the system was doing at the same time? The <em>historical context</em> was crucial in some difficult crash cases.</p><h3>Next steps</h3><p>Dmitry and I first asked ourselves, how could we backtrace what had led to those rare bugs? How does one report a problem with all the contextual and historic data, without even leaving the app? How can we shorten the time it takes the developer to reach that a-ha moment when looking at the report?</p><p>Then we tried to answer our own questions.</p><p>We needed an all-encompassing bug and crash reporting mechanism. It had to continuously record (and store locally) all app screens, touch events and all network traffic. This way, if a problem occurs, everything has <em>already</em> been recorded. So there is no need to reproduce the problematic sequence.</p><p>Which resembled a flight data recorder, aka the plane’s black box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Olw8woey4qh7UYmlXmJoZg.jpeg" /></figure><p>We could totally see ourselves using such a system if it were to exist. So we started researching the space. Many tools have solutions for debugging issues on the backend. But when it came to debugging and analyzing the front end — there were no complete solutions. That was surprising to us, considering how much effort is spent today on polishing the user experience and app UI.</p><p>Competitive analysis showed that there are two big players in the space of crash reporting and several small players offer some subset of in-app bug reporting functionality. None of them had a comprehensive offering, none offered a quality video that wouldn’t slow down the app UI while being App-Store-safe. No one also offered detailed network logging synced to the video.</p><p>We ran an initial feasibility study and built a functional iOS prototype to showcase to potential customers and to our investors. We showed it to the developers in our network and got a unanimous feedback that all of them wished they had it as part of their workflow.</p><p>OK, we can see ourselves using it, we got initial validation and have a working prototype. Next we needed to research the space of developer tools. We needed to scope the size of the market and its trends. As Atlassian (maker of Jira) filed their <a href="https://www.sec.gov/Archives/edgar/data/1650372/000155837015001685/filename1.htm">S1</a> last year, Goldman Sachs fortuitously assisted us with our research.</p><p>We met with all our <a href="https://medium.com/@fishman/my-cofounder-said-i-love-what-were-doing-and-we-shut-down-our-startup-80d5e710c2b2">previous</a> investors, showed them the demo and the deck with all the collected feedback. It took us some time to answer all their questions, but we did get their necessary commitments.</p><p><strong><em>Continuing the marriage analogy from </em></strong><a href="https://medium.com/startup-grind/a-post-about-post-post-mortem-a2c6fcf3f02#.nfcw3dycb"><strong><em>previous post</em></strong></a><strong><em>… </em>due to the apparent butterflies in the stomach feeling, we knew we had finally found our <em>the one. </em></strong>Dmitry and I looked at each other and shook hands over our renewed vows to the new project.</p><p>New Years break was just around the corner, which was perfect for a “bachelor getaway” before getting into a long term relationship with our new venture…</p><h3>Legal</h3><p>During the New Years break, we started to deal with the legal aspects of transitioning one company into another. It was a fascinating challenge and a fun exercise with our talented attorney.</p><p><strong>We had to address the following:</strong></p><ul><li>We needed to move the leftover cash from the previous company.</li><li>We had to rebalance founders equity, as our original split between Dmitry and I was based on no longer relevant assumptions. Plus, we needed to reset our vesting.</li><li>Our previous company had many paid customers. While the risk was small, we did not want to drag along past liabilities to the new venture.</li></ul><p>There were two obvious options. One was just to rename the company. Solved the moving-the-cash problem, but didn’t address anything else. On the other end of the spectrum was — close the first company, return the money to investors and fund a totally new company a minute later. Clearly solved all the issues.</p><p>Yet, there was one tiny complication — the logistical nightmare of returning every investor their piece of the remaining capital and then collecting it back. When we modeled everything, including accounting for the two priced rounds we had in the previous company, it became apparent we needed a simpler way to handle it.</p><p>We had to find a solution that was in between these two extremes. I won’t go into the details here. Not because it’s a secret, but rather because explaining all the details here requires a review from our a legal. And it’s not the best use of our lawyer. However, if you’re ever in a similar situation, feel free to reach out, happy to share our experience and thought process.</p><h3><strong>Bugsee — you know, like “see the bug”</strong></h3><p>And that’s how Bugsee was born in January 2016. Following Paul Graham’s <a href="http://www.paulgraham.com/name.html">advice</a>, we secured bugsee.com.</p><p>We launched our public beta in late April. So far our <a href="https://medium.com/art-marketing/imagine-yesterday-29fcbc97af47">X Factor</a> is at 920 companies with 1,300 developers signed up to try Bugsee. We plan to roll out our pricing by the end of November. Bugsee is free until then. Check out Bugsee <a href="http://bugsee.com/demo">demo account</a> and <a href="http://docs.bugsee.com/">documentation</a>, so you too can see what’s the fuss all about.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0eChRvIm2qc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0eChRvIm2qc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0eChRvIm2qc%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/79eb35db8f7d9d46ba6a0defa9911444/href">https://medium.com/media/79eb35db8f7d9d46ba6a0defa9911444/href</a></iframe><h3>Epilogue</h3><p>Perhaps the most difficult part of the restarting journey was probably lack of tangible deliverables. Throughout our entire careers, Dmitry and I used to build things. And now, for the past several months, every Friday we’d look back at the past week and what did we do? We had been only thinking, googling and excelling (Microsoft kind)…</p><p>Thank you for reading our story. I hope it can help someone in the startup ecosystem. It’s our way of paying back to the community for everything we’ve learned from others. If you ever in a similar situation or just have a question — feel free to reach out. More than happy to <a href="http://linkedin.com/in/alexfishman">connect</a>.</p><blockquote><a href="https://medium.com/u/eb4c8ee18457">Alex Fishman</a> is a Founder/CEO of <a href="http://www.bugsee.com/">Bugsee</a> — a debugging tool for developers. Bugsee lets developers watch videos leading up to crashes and bugs. Check out Bugsee explainer videos for <a href="https://www.youtube.com/watch?v=0eChRvIm2qc">iOS and Android</a> and <a href="https://www.youtube.com/watch?v=8ifopE85gXA">Web</a>, or our <a href="http://www.bugsee.com/demo">Demo</a>.</blockquote><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Mro-phkgJv4rZQ223OYosA.jpeg" /></a></figure><figure><a href="https://startupgrind2017.eventbrite.com/?aff=readon"><img alt="" src="https://cdn-images-1.medium.com/max/326/1*guZPyRXCP37UGWfWDX3bnw.jpeg" /></a></figure><figure><a href="https://twitter.com/startupgrind"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*B3UHAfn5Xm2QNIPW1sYJHA.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fbf3d7baf30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/the-deciding-deep-dive-5fbf3d7baf30">Part 3: The Deciding Deep Dive</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Camera-Killing Smartphones And Their Killer Cameras]]></title>
            <link>https://medium.com/startup-grind/camera-killing-smartphones-and-their-killer-cameras-70ff4757b7ef?source=rss-eb4c8ee18457------2</link>
            <guid isPermaLink="false">https://medium.com/p/70ff4757b7ef</guid>
            <category><![CDATA[cameras]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[smartphones]]></category>
            <category><![CDATA[photography]]></category>
            <category><![CDATA[iphone]]></category>
            <dc:creator><![CDATA[Alex Fishman]]></dc:creator>
            <pubDate>Wed, 14 Sep 2016 06:47:24 GMT</pubDate>
            <atom:updated>2016-12-15T18:22:39.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vt8Rqj-9AvWmfQikHmG7ww.jpeg" /><figcaption>iPhone 7 and iPhone 7 Plus</figcaption></figure><p>So much energy is spent these days on Apple’s AirPods and whether Phil Schiller used the word <em>courage</em> appropriately. Everyone is so fascinated with these topics, Apple could’ve changed their name to <em>Orange</em> by now and no one would’ve noticed. In my opinion, all of this is utterly unimportant.</p><p>What <em>is</em> important is that at the same time, mobile phones’ cameras are making giant technological leaps. These ultra-thin multi-sensor borderline-pinhole cameras deliver stunning imagery today. I get goosebumps every time I read about the progress in mobile imaging.</p><h3>Before I continue, a bit about myself</h3><p>I worked in the digital camera industry for 16 years:</p><ul><li>Back in 1997 I joined Zoran, where we made chips for digital cameras. With the exception of Canon, our chips were used in cameras of every other brand: <em>Konica, Minolta, Agfa, Casio, Nikon, Ricoh, Vivitar, Pentax, GE, Olympus, Kodak, Samsung, Lytro, GoPro, Flip and dozens of no-names. </em>My team worked on every third camera ever shipped in the world.</li><li>In 2005 I joined NuCORE, which also sold its chips to the major Japanese camera brands. Mediatek acquired NuCORE in 2007, where I spent another year working on more camera stuff.</li><li>In 2008 I joined a three-people imaging technology startup, called Refocus Imaging. The four of us continued evolving the technology in stealth mode for a few years and in 2011 we rebranded as Lytro. I eventually left Lytro in 2013 to work on my own <a href="http://bugsee.com/">startup</a>.</li></ul><h3><strong>Camera Phones</strong></h3><p>Ever since the first camera phones became somewhat popular in the early 2000’s, me and my colleagues from the digital camera industry had repeatedly heard that cameraphones would kill us. Every other month or so someone would proclaim that digital camera will be cannibalized by the smartphone industry.</p><p>Yet, it didn’t happen for many years. Despite immediate traction smartphones enjoyed early on, digital camera market continued to grow for another decade, until 2012. You can see this in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wrm_jkdtW3if4maZu5Q-dg.jpeg" /><figcaption><a href="https://www.statista.com/chart/5782/digital-camera-shipments/">Image Source</a>.</figcaption></figure><p>The graph is not entirely accurate. First, 2016 data is only for 6 months. Second, it doesn’t include sales by non-Japanese brands and specifically Samsung numbers. Samsung gained significant traction in 2009–2011 and was taking market share from traditional Japanese vendors. Total camera shipments in both 2010 and 2011 were around 140M units.</p><p>However, the point still stands — the industry was fine up until 2012, where it collapsed in one year and never recovered. As predicted.</p><p>For a full decade these predictions were ignored. And for a good reason. First, when you hear the same non-materializing prediction over and over again, you develop a strong immune system. You start completely ignoring the risk. And thus when it eventually does happen — it catches you by a huge surprise. Same happened to Nokia and will soon happen to gasoline cars.</p><p>Second reason, is the feature-matrix. Oh, we were obsessed with it. Up until only a few years ago, on every possible axis of comparison, cameras were always better than the smartphones: resolution, speed, flash, battery life, boot up time, lens, zoom, focus speed, display, print and image quality, noise characteristics, you name it.</p><p>So how could any respectful photographer forego their camera gear?</p><h3>Picture Value</h3><p>Turns out that the features we looked at did not matter. What killed the digital camera industry was something entirely different. It was Instagram. Or more accurately, the <em>insta</em> part.</p><p>Pictures have a unique formula of <em>value</em>. Picture’s value is inversely proportional to the period from the time it was taken. Value is almost infinite at the time you took the shot. Then it starts its ultimate decay to complete irrelevance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4l19cD3-DkZ26ta9nrn9A.jpeg" /></figure><p>The graph is not entirely accurate either. Picture value is in fact 1/x superposed with spikes around anniversaries. Basically, pictures’ value is almost identical to news stories.</p><p>And that’s where cameras could not compete. Cameras could not deliver you <em>likes</em> and <em>comments</em> within minutes of you taking the shot. Customers traded image quality for instant feedback. They never looked back.</p><p>And guess when Facebook acquired Instagram? Yep, April 2012.</p><p><strong>RIP Digital Camera. I will miss you.</strong></p><p>Many of my closest friends and I were lucky to be a part of it.</p><p>In the recent years, smartphones are closing the gaps on all other fronts of digital imaging. And those are incredible engineering achievements. And that’s what’s important in the new phones. Not their jack-lack-ness.</p><h3>Sidenotes</h3><ul><li>Coincidentally, both Zoran and NuCORE are now part of the mobile powerhouses, Qualcomm and Mediatek, respectively.</li><li>A guy named Andy visited Zoran in 2003 and pitched my team some phone camera related ideas. We even worked on porting his software onto our camera chips. He also gave us a bulky looking phone made by a company named Danger. I had the phone on my desk for weeks. It was a cool toy. Andy Rubin and his software Android joined Google in 2005…</li><li>Smartphones also killed the entire camcorder industry and specifically the beloved Flip, after Cisco paid $600M for it in 2009. Yet, some companies figured out that there are certain places where you simply won’t take your phone to. These are the brilliant DropCam and GoPro.</li><li>Yours truly spending the night in the Pentax Tokiwadai office in Tokyo, circa 2003:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zwLMtBCEd2Na899sZCpb1Q.jpeg" /></figure><blockquote><a href="https://medium.com/u/eb4c8ee18457">Alex Fishman</a> is a Founder/CEO of <a href="http://www.bugsee.com/">Bugsee</a> — a debugging tool for developers. Bugsee lets developers watch videos leading up to crashes and bugs. Check out Bugsee explainer videos for <a href="https://www.youtube.com/watch?v=0eChRvIm2qc">iOS and Android</a> and <a href="https://www.youtube.com/watch?v=8ifopE85gXA">Web</a>, or our <a href="http://www.bugsee.com/demo">Demo</a>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*koUfnfQ-YkmwubsUs4zwwQ.gif" /><figcaption>Enjoyed that read? Click the ❤ below to recommend it to other interested readers!</figcaption></figure><figure><a href="http://eepurl.com/bBbrFX"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Mro-phkgJv4rZQ223OYosA.jpeg" /></a></figure><figure><a href="http://facebook.com/startupgrind"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*kHlMuCZPyf0mQQWAuaR7HQ.jpeg" /></a></figure><figure><a href="https://twitter.com/startupgrind"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*B3UHAfn5Xm2QNIPW1sYJHA.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70ff4757b7ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-grind/camera-killing-smartphones-and-their-killer-cameras-70ff4757b7ef">Camera-Killing Smartphones And Their Killer Cameras</a> was originally published in <a href="https://medium.com/startup-grind">Startup Grind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>