<?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 Kailyn Nelson on Medium]]></title>
        <description><![CDATA[Stories by Kailyn Nelson on Medium]]></description>
        <link>https://medium.com/@kailynnelson?source=rss-2742c96c204a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pznVncLrfMFqDtzmTeGhOg.png</url>
            <title>Stories by Kailyn Nelson on Medium</title>
            <link>https://medium.com/@kailynnelson?source=rss-2742c96c204a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:26:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kailynnelson/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[Case study: UI design to enhance an existing tree species search experience]]></title>
            <link>https://medium.com/design-bootcamp/case-study-ui-design-to-enhance-an-existing-tree-species-search-experience-cffa7ab94366?source=rss-2742c96c204a------2</link>
            <guid isPermaLink="false">https://medium.com/p/cffa7ab94366</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Kailyn Nelson]]></dc:creator>
            <pubDate>Sun, 11 Jul 2021 23:22:18 GMT</pubDate>
            <atom:updated>2021-07-18T20:16:53.994Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Hi Kailyn, since you have a UX background, I was wondering if you could help using Figma to design us the frontend for adding this particular feature,” began the project lead for iSeaTree, an open-source, educational mobile app to help children identify tree species.</blockquote><p>I first worked with the <a href="https://treemama.org/the-tech-treehouse/iseatree/">iSeaTree</a> team during a <a href="https://www.democracylab.org/">DemocracyLab</a> hackathon in March 2021. This new <a href="https://github.com/TreeMama/iSeaTree-React-Prototype/issues/197">GitHub issue</a> the project lead shared with me suggested an enhancement to the app’s tree species search experience.</p><p>The enhancement would:</p><ul><li>show <strong>thumbnail-sized images</strong> (pulled from the <a href="https://www.eol.ucar.edu/content/eol-data-policy">EOL (Earth Observing Laboratory)</a> <a href="https://data.eol.ucar.edu/">data archive</a>) of the tree species listed in the search results.</li><li>allow users to open the image in a <strong>detail view</strong>.</li><li>allow the user to <strong>expand a description</strong> of the species in the detail view.</li></ul><p>The next enhancement after the search results screens will be to add an identification-helper key, mimicking the experience in the <a href="https://apps.apple.com/gb/app/british-tree-identification/id1112564089">British tree identification</a> app. “Helper key” is a term the project is using to describe the <a href="https://www.nngroup.com/articles/wizards/">wizard</a> walkthrough experience that will help users identify tree species.</p><h3>Planning</h3><p>When I asked the project lead about the timeline for the design work, she said the team would start writing code in August. And it just so happened that another DemocracyLab hackathon was coming up on July 10th, which I was able to plan to attend. Challenge accepted.</p><p>In preparation for the event, I began <a href="https://www.figma.com/file/UKeusCbfR5L08lX7CslOAv/CURRENT-iSeaTree-Colors?node-id=0%3A1">compiling all the colors</a> already used in the app’s codebase so I would be able to pull quickly from the app’s existing theme on the day of the hackathon. I discovered a myriad of color values hardcoded into the app and will update the outdated <a href="https://github.com/TreeMama/iSeaTree-React-Prototype/blob/develop/src/styles/theme.ts#L4">theme colors</a> at some point.</p><h3>The hackathon</h3><p>When I joined the iSeaTree group at the hackathon, they were working on importing the data from EOL. While they continued on that front, I began pulling together references.</p><h4>Previous design files</h4><p>I began by searching for any pre-existing design work I could pull from to expedite my process. I had previously loaded a previous contributor’s Sketch designs into Figma.</p><p>While there weren’t any screens there that would be relevant for my current mission, I did find some that would be helpful for the next step (the helper key).</p><h4>Existing patterns in the app</h4><p>If there were parts of the mobile app that are already built and that could be appropriately reused in this case, I could help make it easier for the developers to implement the updates.</p><h4>Locations in the app to be updated</h4><p>I needed to familiarize myself with the context of the new feature. I located a couple of screens that would be affected by these changes.</p><p>The “Add new” screen displays to the user a form for entering a new tree species. (<em>Other designers and I have noted that the app needs some clarity around the labeling and iconography. We are working on it!</em>) An element that looks like a select actually opens up a fullscreen search UI, the primary screen affected by the updates. Thumbnail images would be added to the results in this list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4wVw_WWwea3lKg8-rEHeg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*12zQTHus_dB3uJKE4Gsjiw.jpeg" /><figcaption>The two screens in the iSeaTree mobile app that would be affected by the new search results experience</figcaption></figure><h4>Updated designs</h4><p>I worked directly in Figma, creating high-fidelity design comps for the iSeaTree development team. I considered using a rapid wireframing tool like <a href="https://whimsical.com/">Whimsical</a>, but the iSeaTree team isn’t familiar with it. And by working in Figma, creating components for the design system as I went, I would be able to support rapid, high-fidelity design work in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*4I0thPF-qdh1qrE-yUNAUQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*SrzPT67pqIaIy4fXQdYHXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*BJ9D5mJR5PrcC2pPcddj6w.png" /><figcaption>The three UI design screens I created for the updated iSeaTree search results experience</figcaption></figure><p>As I worked, I created flexible components to enable us to work faster on future high-fidelity designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*tekx-S5jHBJ3ptmONkxprA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKQeA5WXwRff7jRKxH4vPA.png" /><figcaption>A glimpse at some components I have created for the iSeaTree mobile app. I enjoy creating logical component structures and utilizing Auto layout</figcaption></figure><figure><img alt="Screen designs in a Figma file with notes beneath" src="https://cdn-images-1.medium.com/max/603/1*6uN3MMldd9Fq1G55tFY1sA.png" /><figcaption>A view of my workspace, zoomed in on a couple of screens and some notes I had after design review with the project lead</figcaption></figure><p>While working on the detail view’s expanded description, I had to reconnect with the project lead, who suggested I use the <a href="https://material.io/develop/ios/supporting/action-sheet">ActionSheet</a> component to push up the description of the tree species. After reviewing the documentation for that component, I thought it might not be quite the right component for the job since it typically has clickable actions in it (not static text). I brought this up to the lead, and she agreed it wouldn’t be the right component. Not only that but on noticing the screen that appears behind the ActionSheet, she brought up that she wanted users to still be able to review the tree image while reading the expanded description, and that there may be more than one image available for a given tree. That was a twofer of missing specs in the requirements-gathering phase! I collected that information and quickly wrote a few notes for myself using the notes from <a href="https://www.figma.com/community/file/806626024182535168">Annotation Kit 2.0</a>, color-coded <em>yellow</em> for to-do and <em>green</em> for done.</p><p>Also, knowing that the developers are using Material, I should explore the Figma <a href="https://www.figma.com/community/file/778763161265841481">Material Baseline Design Kit</a> for a full set of components that can be customized to iSeaTree’s theme.</p><h4>Coaching opportunity with a new designer</h4><p>I had the pleasure of meeting a new UX designer who chose to work with iSeaTree at the hackathon. After she finished up her work with the EOL data, she asked if I would get her set up with a UX task. I gave her a tour of the Figma file and onboarded her to the task of designing the helper key screens.</p><figure><img alt="Notes in the shared Figma file" src="https://cdn-images-1.medium.com/max/1024/1*6CQJ9dHIMcPri3lKLvnlGg.png" /><figcaption>I wrote out the steps of the helper key process as notes in the shared Figma file to unblock the new designer</figcaption></figure><p>She was new to components, so I demonstrated the structure of the components I had already put together and promised to give her a more in-depth coaching session after I finished the designs for the search results UI. We ran out of time for coaching during the hackathon, but we are scheduling out a session a couple of weeks from now. 😊</p><h4>Communicating with the developers</h4><p>I exported my designs and shared them on the original GitHub task, letting the developer who would take on implementing my designs know that I would make myself available for whatever questions they had.</p><figure><img alt="Figma screens with flow arrows" src="https://cdn-images-1.medium.com/max/1024/1*EBYyYPdakWFnF_8VqNLbgQ.jpeg" /><figcaption>A <a href="https://www.ego-cms.com/post/wireframes-mockups-prototypes-whats-the-difference">user flow</a> illustrating the navigation from the search result to the result detail</figcaption></figure><p>While exporting the screens themselves, I realized it would be helpful to see specifically which <a href="https://uxdesign.cc/affordances-and-signifiers-82bd6f50fc1a">affordances</a> led the user to which screens. I know it can be difficult to make this crystal-clear in the design-development handoff, so hopefully, this reduces the chance of confusion.</p><p>I was happy to hear from the iSeaTree project lead and to have the opportunity to help out, especially since the app is for kids learning about the natural world around them. For more information about the project, check out <a href="https://treemama.org/the-tech-treehouse/iseatree/">the iSeaTree website</a>.</p><h3>Next steps</h3><ul><li>Design the Add form with a button to open the quick-search (direct to the species results) and a button to open the helper key (to filter the possible tree species by artifacts, like a leaf or bark, that the user has to reference)</li><li>Design result detail cases where 1) there is not at least one image, 2) where there is no description, and 3) where the description is too long and has to scroll (and leaves at least half of the screen space for the tree images)</li><li>Create the icons for the helper key experience</li><li>Run a complete design system audit</li><li>Write documentation to help new designers create in the iSeaTree Figma workspace</li><li>Address suggestions from the new designer’s usability review</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cffa7ab94366" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-ui-design-to-enhance-an-existing-tree-species-search-experience-cffa7ab94366">Case study: UI design to enhance an existing tree species search experience</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>