<?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 SERGI BOSCH on Medium]]></title>
        <description><![CDATA[Stories by SERGI BOSCH on Medium]]></description>
        <link>https://medium.com/@sergi_bosch?source=rss-58f72ed0e569------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EnOPQdMuVc7mRu4ZcPKc4Q.jpeg</url>
            <title>Stories by SERGI BOSCH on Medium</title>
            <link>https://medium.com/@sergi_bosch?source=rss-58f72ed0e569------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:18:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sergi_bosch/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[Alert: As Of 2/23/24, Background Checks Now Take 20–30 Days For Anyone Having Worked In Los Angeles…]]></title>
            <link>https://medium.com/@sergi_bosch/alert-as-of-2-23-24-background-checks-now-take-20-30-days-for-anyone-having-worked-in-los-angeles-2cc20ede6165?source=rss-58f72ed0e569------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cc20ede6165</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[employment]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[employment-law]]></category>
            <dc:creator><![CDATA[SERGI BOSCH]]></dc:creator>
            <pubDate>Wed, 13 Mar 2024 16:08:48 GMT</pubDate>
            <atom:updated>2024-03-13T16:08:48.071Z</atom:updated>
            <content:encoded><![CDATA[<h2>Alert: As Of 2/23/24, Background Checks Now Take 20–30 Days For Anyone Having Worked In Los Angeles</h2><p>Are you aware that a new law was passed on Feb 23, 2024 regarding how background checks can be conducted in Los Angeles? Forbes details these changes in their article <a href="https://www.forbes.com/sites/alonzomartinez/2024/02/21/impacts-of-los-angeles-courts-revised-search-procedures-on-criminal-background-checks/?sh=6a05bd4b5f71">Impacts Of Los Angeles Court’s Revised Search Procedures On Criminal Background Checks</a>.</p><p><strong>What this means for you:</strong> if you have accepted a job since Feb 23, 2024, your background check will likely take between 20–30 days to complete — and may not even be completed successfully. Consumer reporting agencies (such as @HireRight) and big tech companies such as @Apple that conduct background checks will struggle; and of course job candidates from Los Angeles will suffer.</p><p>Be informed and be prepared to discuss this during your next hiring interview. If you have been impacted please comment below. Maybe we can crowd source this problem to help consumer reporting agencies (CPAs), big tech and the City of Los Angeles solve it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cc20ede6165" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: REA Maps: Route Scheduling for Realtors]]></title>
            <link>https://medium.com/@sergi_bosch/ux-case-study-rea-maps-route-scheduling-for-realtors-e788e0676326?source=rss-58f72ed0e569------2</link>
            <guid isPermaLink="false">https://medium.com/p/e788e0676326</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mapping]]></category>
            <category><![CDATA[coursera]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[real-estate]]></category>
            <dc:creator><![CDATA[SERGI BOSCH]]></dc:creator>
            <pubDate>Sun, 24 Jun 2018 03:50:32 GMT</pubDate>
            <atom:updated>2024-05-04T23:04:49.747Z</atom:updated>
            <content:encoded><![CDATA[<p>UX Case Study: <em>REA Maps: Route Scheduling for Realtors</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9JPhV8KErdBqNF9Ewu9O-A.png" /><figcaption>Final MVP Concept</figcaption></figure><p><em>REA Maps: Route Scheduling for Realtors</em> began as a result of my attending an open house to observe a realtor as he conducted his job. We spoke about his process of organizing the open house, from the steps leading up to it, to the steps he would take following it. He showed me his organizational materials, and I observed how he greeted guests as they arrived.</p><p>Being that my design brief called for a glanceable interface, my first version of this product was an app that helped an agent manage his open house process — and render a series of data points in a summary screen (like a feed) that would appear on the apps home screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*PLnjIONb_nteiKnkrzBfiQ.png" /><figcaption><em>Early prototype to assists in the materials gathering stage for an open house</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*-gB5p5kJvsaIBM-60eA7bA.png" /><figcaption><em>Feed for glanceable data points</em></figcaption></figure><p>However, after testing this app several users, I realized that my core proposal (my MVP), was not enough to carry a product. Though it would meet the need of some users, many others would not benefit. For instance, a lot of realtors don’t feel burdened by the process of gathering open house materials.</p><p>So I pivoted by focusing on another need realtors have, which is: struggling to map the route they will take when taking buyers to successive showings.</p><h3>Pivot: Open House vs Showing</h3><p>An open house has several dimensions to it. It begins with a realtor agent getting a listing from a seller, then arranging to show that home to potential buyers. That agent might show the home on Saturday from 12–3pm; or she might ask an associate show the home for her. This differs from a <strong>showing</strong>. A showing is when an agent works with a buyer (not a seller) to find them the perfect home. For a showing, the agent might schedule 6 showings between 11am and 5pm on a given day. And this is when things can get sticky — and when <em>REA Maps</em> comes into play.</p><p>As you can see from the screens below, the focus is on “when do you need to be where, and what time do you need to leave that location to make it to the next location on time”, aka, scheduling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*IEOyVkiLl_p6yOTh5jCxPA.png" /></figure><h3>Iterating on Success</h3><p>Once I nailed down my scheduling interaction design, user testing illuminated a shortcoming in my product: an agent might need to modify or cancel their route midway through the day. And that’s what led to Version 2.0, below. Notice the new edit menu.</p><p>Conclusively, this is an incomplete product as evidenced by the lo-fidelity quality of the screens displayed in this article. However, I have validated the need for this product and can’t wait to move forward with building it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*dIi02yjpB_Wxw6l5XEBcNw.png" /><figcaption>Edit screen discovered during user testing</figcaption></figure><p><a href="https://www.figma.com/proto/kzBENLwZVSkOCLvuaEgmiT/REA-Maps?page-id=0%3A1&amp;type=design&amp;node-id=1-13&amp;viewport=-2053%2C2894%2C1.07&amp;t=eMMOhtE7BXFLp7wO-8&amp;scaling=scale-down&amp;starting-point-node-id=1%3A13&amp;hide-ui=1">See Interactive Figma Prototype Here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e788e0676326" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eat Sleep Poop: $ + What’s Next]]></title>
            <link>https://medium.com/@sergi_bosch/eat-sleep-poop-app-whats-next-785ae442135e?source=rss-58f72ed0e569------2</link>
            <guid isPermaLink="false">https://medium.com/p/785ae442135e</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[baby]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[app-development]]></category>
            <dc:creator><![CDATA[SERGI BOSCH]]></dc:creator>
            <pubDate>Mon, 07 Aug 2017 17:35:48 GMT</pubDate>
            <atom:updated>2022-02-14T18:16:49.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*wkOAV2_azuk_ATIGP0ou_g.png" /><figcaption>About a double bacon cheeseburger, fries and shake from <a href="https://medium.com/u/7e829ee11e39">Shake Shack</a></figcaption></figure><p>Well, it finally arrived: my first check from Apple paying me the proceed of sales from my app. It’s been over 3 years in the making! I first identified the need for this product in March of 2014. At the time, I did not have a baby yet; rather I had a newborn nephew, whose parents kept a “baby log” in a spiral notebook. I saw that log and immediately had the idea for my product. My original design was as a Google Glass app so mothers could input the data hands-free; but Glass floundered in 2014, and thus I pivoted to iOS.</p><p>And so here we are, 3.5 years later and I’m finally seeing my efforts being rewarded via direct deposit from Apple Inc to my bank account. Are you ready to hear the amount? Well, let me tell you it paid for half our <a href="https://medium.com/u/7e829ee11e39">Shake Shack</a> meal that day, so I’m certainly not ready to retire or create an “airbnb for private jets” account. And yet I can’t help grin from ear-to-ear thinking about it.</p><p>At this venture, let me jump into the specs for all those tech junkies out there wondering what the skinny is: Swift 2.0 (was never built in Objective-C, just went straight to Swift), Parse as my MBaaS.</p><p>And then for product managers out there, Eat Sleep Poop offers: customization features (use ml or ounces; name-your-own-medication; others); share-a-child profile so a loved one or babysitter can participate from their phone; at-a-glance summaries; and the “clipboard UI pattern” I invented.</p><p><strong>What is the Clipboard UI Pattern</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2sR3RAWkvrq5twJPKWl_Dg.png" /><figcaption>Eat Sleep Poop App’s Clipboard UI Pattern</figcaption></figure><p>The clipboard UI pattern is based on the real-life experience of using a clipboard to manage the collection of data. Just as the user of a clipboard experiences transacting with a sheet of paper to mark off some quick entries, the user of this app marks off quick entries from the Home screen of Eat Sleep Poop. Using mostly one-tap actions, the user can be finished with their data entry as seamlessly as they could if they were picking up a pencil to jot down a similar entry onto a photocopied piece of paper affixed to a clipboard.</p><p>Of course, there are times when a user wants to go more in-depth with an entry. In this case, the clipboard metaphor gets stretched a bit; but for arguments sake, let’s say the user needs to “jump to page 2” to provide details of an quick input field from page 1. Eat Sleep Poop provides for this experience by providing an additional “more” view for each of the line items from the Home screen. Imagine a mother that is breast feeding and wants to add some details about how the feeding went… maybe simply a star to indicate the child latched quickly; or perhaps a note about the feeding that mom doesn’t want to forget because it might be worth mentioning to the pediatrician at their next appointment. Such details are accounted for in each of the “more” screens that serve as addendums to each event that’s being tracked.</p><p><strong>What’s Next for This Product?</strong><br>The payment arrived; growth is steady, indicating payments will continue to arrive… Things are going great, so I might as well kick back and relax right? I kind-of wish it could be that easy. After all, I have my own baby at home now (a little boy who’s already a legend in his dad’s eyes) and it would be a delight to spend every minute with him. But no, an app is like any other business: I have maintenance issues at a minimum. Additionally, combine that with ambition and my Catalan roots, and you end up where I’m at — looking at tons of opportunities to improve based on user feedback, metrics and imagination.</p><p>So that’s where you come in — since you’ve read this far, how about taking Eat Sleep Poop for a spin? Kick the tires, let me know your thoughts. The team is growing, especially development. We are migrating to Swift 3 and 4 in the next 4 months; and have a sweet backlog of stories — combining new features, bug fixes and enhancements — which require the talents of awesome Swift and React Native engineers that enjoy collaboration, working for equity, and a side project. You can contact us via sergibosch.com. And please, leave comments below. Thanks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=785ae442135e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>