<?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 Elif Ceren Dik on Medium]]></title>
        <description><![CDATA[Stories by Elif Ceren Dik on Medium]]></description>
        <link>https://medium.com/@ElifCerenDik?source=rss-f5e46d629924------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s8g-K20n33uV6ZlTjVPbQw.jpeg</url>
            <title>Stories by Elif Ceren Dik on Medium</title>
            <link>https://medium.com/@ElifCerenDik?source=rss-f5e46d629924------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:45:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ElifCerenDik/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[How to structure your online forms for success]]></title>
            <link>https://medium.com/swlh/how-to-structure-your-online-forms-for-success-4f0e4308cc9d?source=rss-f5e46d629924------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f0e4308cc9d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Elif Ceren Dik]]></dc:creator>
            <pubDate>Thu, 25 Oct 2018 10:36:43 GMT</pubDate>
            <atom:updated>2018-10-25T10:37:50.774Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ztkotfPtrIoOFlbDAebDPQ.jpeg" /><figcaption>Originally published on <a href="http://jotform.com/"><strong>JOTFORM.COM</strong></a></figcaption></figure><p>Forms.</p><p>I know, your pulse doesn’t start racing with excitement.</p><p>Forms get a bad rep.</p><p>Love or hate them, from registration to collecting payments, forms are here to stay. Forms equal input, they mean collecting data from anyone who interacts with your business.</p><p>A form is successful when it engages rather than frustrates your user, and if it provides you with the data you need.</p><p>A form consists of different parts. And building a form that does what it needs to do relies on rules, principles, logic — and a bit of play.</p><p>Here are some ways to structure online forms that actually convert.</p><h3>Deceptive simplicity</h3><p>Forms look simple. A few fields, a bit of text, a couple of buttons. Is there really much more to it than that?</p><p>Well, yes.</p><p>A successful form <em>feels</em> simple for the user. But behind the apparent simplicity lies a spectrum of decision-making, tweaking, careful wording, and thoughtful strategy.</p><p>All these are necessary to create a form that garners the useful data you need. Without them, forms won’t yield what you need.</p><p>Like a Lego construction, a good form relies on architecture. That means strong foundations, the right kind of structure and attention to detail.</p><p>There are five essential rules to keep in mind when you build a form.</p><h3>1. Start with questions, bottom up</h3><p>As in a Lego game, the organization of your form needs to be informed by questions. It’s questions that build a form from the ground up.</p><p>That makes listing questions a good place to start.</p><p>I always encourage our users to start by writing down all the questions that come to mind when thinking about what a form needs to achieve.</p><p>Make them proper questions, with a question mark at the end. Give yourself time to do this. You may want to ask colleagues to join you and add their questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SIC3g3tm1TQVnLQ4" /></figure><h3>2. Remove any questions you don’t need</h3><p>Removing the unnecessary questions is essential because you need the cooperation of your users — the people who will be taking the time to fill out the form.</p><p>What are the chances of these people having a long time to spare on something they don’t see the point of? None.</p><p>So don’t offend your users by wasting their time. Cut with an eye for what you really need to know. Then rephrase each of these questions as succinctly as possible, without losing an inch of clarity.</p><p>Every time your user gets confused, doesn’t understand a question or doesn’t know what’s expected of them, the risk of them giving up increases dramatically.</p><p>Every additional question will affect a form’s conversion rate, and a user’s likelihood to complete it. If you don’t need it, don’t ask for it.</p><h3>3. Organize questions into groups</h3><p>Once you have trimmed and streamlined your list of questions, divide them into groups and subgroups where necessary.</p><p>Organizing questions in groups will help create logic and flow, which will support your user in progressing through the form. It will also make questions more digestible, and lower the overall cognitive load.</p><p>Some other affordances of grouping questions:</p><ul><li>A large form can be divided into multiple sections.</li><li>Grouped questions can be skipped by setting a single Skip logic condition</li><li>A set of questions can be repeated for every unit, such as members of a household</li><li>A set of questions can be displayed together on the same screen during data entry</li></ul><p>You can mark the ‘theme’ of each group (i.e. what holds the questions together) with a short, informative header at the top of each section (e.g. contact details — personal details — work experience). This lets the user quickly scan the form to see what type of information they will need to provide.</p><p>All this will lead to groups of succinct, thought-through, clear questions. Some of these groups will be bigger, some small. You may have some orphan questions. All good.</p><h3>4. Sequence your questions skilfully</h3><p>Even if you have more than one question per page, your user will have to answer them one at the time.</p><p>Every section in the form should nudge users to the next one. That means you need to order groups, and questions within groups, in a sequence that is logical and makes sense.</p><p>So ‘Who are you?’ will come before ‘ Where do you live?’ which will, in turn, come before ‘What’s your work experience?’</p><p>On a payment form, you would start by taking details, follow with shipping information, and finish by asking for payment. If you asked users to pay first, they would be far less likely to do so.</p><p>Sometimes, questions will need to be asked in a specific sequence because they don’t make sense out of context.</p><p>As a general rule of thumb, try and stagger questions from easy to hard. This helps users move through questions more quickly and motivates them to continue.</p><p>Remember to be ruthless when it comes to eliminating unnecessary questions. You can always ask optional questions after a form is completed — chances of getting a higher response rate this way is always likely to be better.</p><p>For example, questions like “How did you first hear about us?” or “Would you like additional information about our services?” feel less invasive when presented as an optional follow-up question.</p><p>Each of your questions is half of a whole. The other half is provided by your users. You can see the way you build your form as the blueprint for a conversation, or a dance.</p><p>The key thing to keep in mind is that there’s someone else you need to engage with, and who needs to engage with you. That’s what’s going to drive your decisions on how to order the questions on your form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0pY49UFLlnVkaKYg" /></figure><h3>5. Create movement in your form</h3><p>Your next, and final, rule follows from this: there needs to be movement in your form.</p><p>Each bit needs to prepare your user for the next one. In essence, it needs to become a story that you co-write with your users.</p><p>The way you construct and order your form needs to have some kind of narration woven within it — and that narration will be an important part of what makes your reader hanging.</p><p>Who is going to be your conversant who will co-create the form with you? That’s the question to keep in mind as you build the form. Forms are not just about mindless data — they are about people with minds.</p><h4>Key components of a form</h4><p>A form has one overarching goal — to get the recipient to completion. Part of guiding them down this path is explaining</p><blockquote>a) what type of form they are filling out and</blockquote><blockquote>b) what they can accomplish by filling it.</blockquote><p>Realistically, few people will take the time to read a detailed description of a form’s purpose, so you need to capture it concisely. That’s why the title is so important.</p><p>Make your form title is absorbing, informative and apt. Don’t waste words; get to the point. You want your reader to remember the purpose of the form as they continue to fill it out.</p><p>A good form doesn’t start abruptly: it will have a welcome page. It won’t end abruptly either: it will finish with an expression of thanks. Make sure you don’t skip these two parts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_KNS3gTepyL1VNJv" /></figure><p>Some forms require more effort than others. For instance, some will ask the user to check external bits of paperwork (e.g. passports). Some will take a substantial amount of time to complete.</p><p>Don’t spring this upon your user halfway — this will annoy and demotivate them. In the case of a more elaborate or more demanding form, give a brief, upfront description of what they can expect right at the start.</p><p><strong>Some more technical stuff</strong></p><h3>Types of Input Fields</h3><h4>Selecting the right divider</h4><p>Choosing the right type of divider for your form is essential. Depending on a form’s length, this could be very minimal.</p><p>Our new product, <a href="https://www.jotform.com/cards/">JotForm Cards</a>, presents each question separately. But in the case of traditional forms, placing dividers in (to visually break sections up) reduces overwhelm.</p><p>Communicating distinctions between groups don’t require much visual difference. In fact, too much contrast can distract people and stop them from being able to scan the form. The focus should always be on a form’s content rather than its presentation.</p><p>As information design expert Edward Tufte points out:</p><blockquote>“Information consists of differences that make a difference.”</blockquote><p>Basically, any visual element that isn’t actively signifying something makes it worse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ca7QqP5sry4l64rg" /></figure><h4>Multi-page or single page?</h4><p>Is it better to group each topic on a single page or divide them across a series of pages? How many pages should there be? The answer is… it depends.</p><p>Some types of forms work better with multiple sections on one page and others work better with various pages, depending on length and content, and the users’ mental model.</p><p>When distinct topics are short enough to fit into a few sections, <strong>a single page</strong> will probably work best. When each section begins to run long, multiple pages may be required to break up the conversation.</p><p>When we released Card Forms, <a href="https://www.jotform.com/blog/how-focusing-on-the-customer-not-the-competition-brought-us-over-1-million-new-signups-in-a-year/">the JotForm Data Team conducted research</a> about conversion rate (Form View/ Successful submission rate) of our new cards. The study showed that even in short forms (up to 7–8 fields), asking questions in a single page provided a better conversion rate.</p><p>Because of this set-up, we also added a summary page and a progress bar. This displays how many questions there are remaining and how many have been completed, motivating users and encouraging them to finish the form with the endowed progress effect.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QXbw1GhBdTx3pS1G" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1xR4JZWd1AJkgqTb" /></figure><h4>Distinguish between primary and secondary actions</h4><p>Grouping questions also have the advantage of distinguishing between primary and secondary actions. Primary and secondary actions let users complete forms without any issues.</p><p>A primary example encourages you to complete the form. A secondary action takes you back when necessary. The most common example of primary and secondary actions is moving forward or backward.</p><p>But there are also use cases for secondary actions such as Save for later, preview, export and reset.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UzTFAAWfBAhxcwkc" /></figure><h4>Advantages of using input groups and flexible inputs</h4><p>Finally, there is the question of <strong>flexible input vs. form validation</strong>.</p><blockquote>Form validation = required field, for example, someone’s name.</blockquote><p>These should always be visible. However, when an input is flexible, it can be useful to offer the option of collapsing the field to minimize overwhelm.</p><p>Carefully consider the right input field for the type of answer you’re looking for. Could it be yes or no? A predefined selection?</p><p>Whenever possible, give affordances to help people answer questions quickly. Having predefined answers or yes/no questions will also help you collect and analyze data more easily.</p><p>You can always add an ‘other’ section if necessary.</p><p>Equally, remember to indicate which fields are optional and which aren’t. The (*) symbol is well-understood to mean ‘required’.</p><p>Associate required or optional indicators with input labels to demonstrate which questions need to be answered. The (*) symbol is well-understood to mean ‘required’.</p><h3>Final thoughts</h3><p>Yes, forms exist to gather data — but they do so through a collaborative process between you and your users. Skillful form building is not a mechanical process: it involves reflecting on what you are trying to achieve, and what’s the best way to achieve it.</p><p>That means, amongst other things, thinking about which data type will be most useful to answer the questions at hand. Focused forms are most likely to yield actionable results.</p><p>Building an effective form is a creative process, but forms are no place to get fancy. Keep it as simple, short and focused as possible. Good luck.</p><h4>Thanks for reading. If you enjoyed this article, feel free to hit that clap button 👏 to help others find it.</h4><h4><a href="http://pix.jotform.com/lR_wcwgN">Say Hi on Twitter</a> or check out what we’re building at <a href="http://pix.jotform.com/Vci4H3l8">JotForm</a>.</h4><p><em>Originally published at </em><a href="https://www.jotform.com/blog/successful-form-structure/"><em>www.jotform.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f0e4308cc9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-structure-your-online-forms-for-success-4f0e4308cc9d">How to structure your online forms for success</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it’s like to spend 326 days on a massive product release for 3.2M users]]></title>
            <link>https://medium.com/swlh/what-its-like-to-spend-326-days-on-a-massive-product-release-for-3-2m-users-4df6f9a9bdd7?source=rss-f5e46d629924------2</link>
            <guid isPermaLink="false">https://medium.com/p/4df6f9a9bdd7</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Elif Ceren Dik]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 11:30:08 GMT</pubDate>
            <atom:updated>2018-03-09T12:20:37.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*y-naup-C5fnBcAHT-hzhsA.png" /><figcaption>Launch day</figcaption></figure><h4>326 days of JotForm Cards</h4><p>At JotForm, our users matter to us. A lot.</p><p>After all, we have <a href="https://www.jotform.com/blog/331-How-NOT-following-my-dreams-enabled-me-to-build-a-startup-with-3-2-million-users">3.2 million of them</a>. They create forms and receive responses through us every day.</p><p>We want to make our users’ experience with us as easy and enjoyable as possible. How do we do this? By listening to them and learning from them whenever we can.</p><p>And that’s why we created <a href="https://www.jotform.com/cards/">JotForm Cards</a>, our most user-driven project ever.</p><p>While we built Cards, our users guided us every step of the way; from research and design through to development.</p><p>Our founder wrote about how focusing <a href="https://www.jotform.com/blog/355-How-focusing-on-the-customer-not-the-competition-brought-us-over-1-million-new-signups-in-a-year">on the customer (not the competition) brought us over 1 million new signups in a year</a>.</p><p>From concept to launch, this process took us 326 days to complete.</p><p>How did we go about it?</p><p><em>Here’s what happened…</em></p><h3>Day 1 — Idea</h3><p>Looking at things like user feedback or bug reports over a large timeframe, we realized our forms needed an update.</p><p>Well, the internet reminded us, too.</p><p>“<a href="https://www.jotform.com/blog/352-How-to-launch-when-everyone-s-watching">It’s not easy to hear that your product is ugly,</a>” wrote <a href="https://twitter.com/aytekintank">Aytekin</a>,</p><blockquote>“Sure, the internet has its share of “haters” and trolls who love to hurl dumb insults, but sometimes that negative feedback has merit.</blockquote><blockquote>In 2016, I knew the critics were right. JotForm was 10 years old, and our forms were looking tired.”</blockquote><p>We could make as many minor tweaks as we wanted, but the fact remained: the design of our forms, and the experience of filling them out, <a href="https://www.jotform.com/blog/355-How-focusing-on-the-customer-not-the-competition-brought-us-over-1-million-new-signups-in-a-year">was behind the times</a>.</p><p>Our forms needed to be more aesthetically-pleasing, user-friendly and smart.</p><p>Thus, we began our journey with a single aim: <strong>re-invent our online forms</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*pwfkx601p5QHNtnYvOlcIw.png" /><figcaption>Meeting for the 2017 mission</figcaption></figure><h3>Day 18 — Hack week 1: Fundamentals</h3><p>Here’s how it works at JotForm: whenever we’re looking for answers, alternative solutions or ways of pushing the boundaries, <a href="https://www.jotform.com/blog/357-Sprint-without-losing-your-sanity">we organize a hack week</a>.</p><p>This requires all teams to drop their daily responsibilities and work on a single task for five days straight. And so, the idea for JotForm Cards was born.</p><p>Now we’d specified our goal — <strong>to reinvent online forms</strong> — we had to ask ourselves:</p><blockquote>“How on earth can we reinvent online forms?”</blockquote><p>This question immediately gave rise to other questions, too.</p><blockquote>What would define this new generation of forms? How could we create solid ground for the rest of the project?</blockquote><p>At the time, trying to find answers felt like staring at a blank page. We knew what we were working towards, but we didn’t know how to get there.</p><p>So, we started to analyze as many forms as possible, in as much detail as possible, zooming in on different aspects such as label alignment, colors, animations and so on.</p><p>We also started to analyze our own users’ forms in more depth. To create a product — no matter what your role in the team is — the most common strategy is to do online searches, read academic articles and review what your competitors have done.</p><p>But, in our experience, these tactics don’t always point the best way forward. Indeed, our founder wrote about <a href="https://www.jotform.com/blog/355-How-focusing-on-the-customer-not-the-competition-brought-us-over-1-million-new-signups-in-a-year">how focusing on the customer (not the competition) brought us over 1 million new signups</a>.</p><p>Long story short, we prefer to take our users’ choices as our starting point.</p><p>So, when we’re at a turning point, our users’ forms provide us with input and guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lp4LE91C0nvo0inybamk7w.png" /><figcaption>Example forms from the first hack week</figcaption></figure><p>On the basis of our analyses, we began to create prototypes. At the end of the week, each team shared and explained their decisions, setting out their ideas using the form prototype they had developed.</p><p>We saw that all teams struggled with similar problems and arrived at similar evaluations — but often their solutions were different.</p><h3>Day 39 — Hack week 2: What might forms look like in 2027?</h3><p>By the end of the first hack week, we’d put the fundamentals for the project in place.</p><p>Now it was time to push the limits. The subject of hack week 2 was:</p><blockquote>“what might forms look like in 2027?”</blockquote><p>We didn’t know what the design trends would be in ten years time, or which technologies would be available to us.</p><p>So we let our imagination run wild.</p><blockquote>How could we push what we already had, break the rules and create a free-thinking mindset?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3LBgelCVg_r96NLSECulbw.png" /><figcaption>Example forms from hack week 2</figcaption></figure><p>During hack week 2, we experimented with voice-overs, AR, and creating designs from a space age. It was a lot of fun.</p><h3>Day 60 — Hack week 3: Pimp my form</h3><p>Hack week 3: time to try something totally different. Instead of working on one idea for a whole week, each team randomly picked a form and spent the day improving its visuals and functionality.</p><p>We used real-life instances picked from our users’ forms. And at the end of each day, the new version of the form was sent to its original owner for feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MlEDkuUYfCc1f939bqUO-g.png" /><figcaption>Before/after versions of a form</figcaption></figure><p>With only one day to analyze problems and find solutions, we were forced to move quickly. This was a good thing. There was no time to obsess over tiny details or try different ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ceBYOLGBrYez8Weh8bb3ng.png" /><figcaption>Before/after versions of a form</figcaption></figure><p>This hack week helped us develop a mindset of dividing large problems into smaller pieces and addressing them one by one.</p><p>(ps. I know I keep talking about hack weeks. In case you are interested, here is <a href="https://www.jotform.com/blog/357-Sprint-without-losing-your-sanity">how hack weeks can encourage innovation and creativity</a>)</p><h3>Day 81 — Hackweek 4: Invent Form 2.0</h3><p>During hack week 4, all teams tried (almost) all possible form layouts. We needed to create something amazing on the basis of the prototypes we’d developed, the analyses we’d done and the knowledge we’d gained over the previous weeks.</p><p>So, all teams started to create final prototypes to show what, in their opinion, the new generation of online forms should look like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*6W6AnBZHvBR4c-HEUXJzEA.png" /><figcaption>Example forms from the hack week 4</figcaption></figure><p>It was time to start making serious decisions. So we asked for our users’ opinions once again. We prioritized user-friendliness, fun, and ease.</p><h3>Day 88 — First Prototype</h3><p>On the 88th day of the project, the first prototype of <a href="https://www.jotform.com/cards/">JotForm Cards</a> was ready for action (at this point, it didn’t even have a name yet).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-lBP27Z8bUCwh2k2zu5P_g.png" /><figcaption>Our first prototype</figcaption></figure><p>With our first prototype done and dusted, it was time to move on to the next phase: development.</p><p>Initially, we tried to remain as independent as possible from JotForm’s original infrastructure and focus on creating something new. But equally, we needed to figure out a way to support JotForm’s traditional form layout as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WE8jvuWkRZ4qRWt9Zc269w.png" /><figcaption>JotForm team at a meeting</figcaption></figure><p>We reviewed our legacy code to see whether it should be renewed or reused for JotForm Cards. We eventually decided that reusing the current code base would be a lifesaver; and, that it would be best to design the new software architecture according to our current infrastructure instead of updating it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bCuu8Hv3wCy7YwAzLtOzBQ.png" /><figcaption>A member of Untitled Team working hard</figcaption></figure><p>Now, it was time to do some heavy lifting and convert the prototype into a feature-complete product. All form fields were redesigned and redeveloped, all micro-animations were rewritten, and all our original decisions were re-evaluated again.</p><h3>Day 138 — A/B tests start</h3><p>After months of hard work, we were ready to share our secret project with the world. It was super-exciting for us to see user reactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*LyB82uFpDoPmp7ohZUueJQ.png" /><figcaption>A member of Data Team while working on JotForm Cards stats</figcaption></figure><p>We immediately started to pay close attention to the statistics that were rolling in. The Data Team analyzed answers to questions like:</p><blockquote>Did users like JotForm Cards? Did they want to switch back to classic form layout? How many users stayed active when using JotForm Cards? How many fields were added?</blockquote><h3>Day 195 — New user group</h3><p>After nearly two months, the numbers from the A/B test didn’t reflect what we’d hoped: we needed to go back to the drawing board.</p><p>We began brainstorming to look into the root of the problems, experimenting with changing the default colors and looking for a correlation between user categories and the form layouts they preferred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*I7zSu_eykQoY3Wfo3wrmlQ.png" /><figcaption>A brainstorming session</figcaption></figure><p>In the meantime, we were still receiving feedbacks from real users. And since they’re the ones who will be using the product, we always give their thoughts priority.</p><p><strong>What were they saying?</strong></p><p>It was something along the lines of:</p><blockquote>Yes, you did something new — which is super cool — but there is still a need for the classic form layout.</blockquote><p>And that was it! Once again, our users showed us the way.</p><p>They were happy to try something new like JotForm Cards, but they didn’t want to lose the classic form either.</p><p><em>Why couldn’t they have both?</em></p><p>So, we started working on a new test group who could create forms of both types and add them to ongoing A/B tests.</p><p>By the time the A/B test was updated, JotForm Cards had nearly every major feature of our classic forms.</p><p>Time for more hack weeks!</p><h3>Day 214 — Hack week 5: New features</h3><p>So, we’d managed to get JotForm Cards to the same level as our classic forms and updated our A/B tests.</p><p>Usage statistics were increasing every day. It was time to take JotForm Cards to the next level.</p><p>For the 5th Hack week — and for the first time in the <a href="https://www.jotform.com/">JotForm history</a> — all teams worked on different ideas for a week.</p><p>And we made great progress.</p><p>One of our product teams developed a ‘Smart Embed’ feature, which automatically adapts JotForm Cards to mimic the page it’s embedded in.</p><p>Another team developed the ‘Inline Embed Editor’, which lets users adjust their form’s embedded style on their pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Hc50_cQJ4_uxUAoey91iDQ.png" /><figcaption>Inline Embed Editor</figcaption></figure><p>We also updated the mobile version of the JotForm Cards from top to bottom, adapting all layout elements, animations, and gestures to provide the best user experience on a mobile device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*b4nhvRJFspRF9CwaiWxOfg.png" /><figcaption>JotForm Cards mobile version</figcaption></figure><h3>Day 242 — Hackweek 6: Fields</h3><p>During the 6th hack week, it was time to improve form fields and add cool features to them.</p><p>All teams worked on different form fields to make prototypes as parallel processes. We selected the target fields according to usage rates of fields and user feedback.</p><p>One problematic field was the Input Table. We managed to improve this field by updating its design and adding new features such as an emoji slider, thus making one of the most boring fields fun to fill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7fTcUhI4LNsYWv7r1Zzckw.png" /><figcaption>Input Table Emoji Sliders</figcaption></figure><p>We worked on the address field too, adding an autocomplete feature to make it easier to fill out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ednCOAMv_B2XqKi159HkeQ.png" /><figcaption>New address field with the autocomplete feature</figcaption></figure><p>We also developed the Multi-line Question, which lets users add more than one field to a single card.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WuZ2-KpFTjPxv0_VcXZZqA.png" /><figcaption>Multi-line Question</figcaption></figure><h3>Day 262 — Hack week 7: More fields</h3><p>Improvements during hack week 6 had a great impact on user feedback. So, we decided to look back into improving the most-used form fields.</p><p>One team worked on the payment field and integrated a shopping bag feature, which lets form submitters see the products they want to buy listed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*oDMQF2CITakVyffoGhanRA.png" /><figcaption>New product list and shopping bag</figcaption></figure><p>Another team made updates to the email field and added verification features to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*wkk3X_TXv1jMTn_jnOIAHQ.png" /><figcaption>Email field with the verification feature</figcaption></figure><p>Finally, we updated the Long Text Entry field to add emojis, files or styles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*UWBmFxaVepxY7EKu3rodNQ.png" /><figcaption>Long text entry field</figcaption></figure><h3>Day 274 — New group for the test</h3><p>Our testing continued, and when we analyzed the numbers, we saw the third test group was a great success.</p><p>The decision was made: our users should be able to create <em>both</em> types of forms, new and classic.</p><p>Now, we wondered, what was the best way to present these options to users? Another A/B test it was!</p><p>We prepared three different form layout selection models for each group and put them to test with a control group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*JaWXjz4pnSmdLELjimMH_w.png" /><figcaption>A version of the form layout selection modal</figcaption></figure><h3>Day 298 — Hack week 8: Wrap it up</h3><p>The 8th and final hack week was our last opportunity to make big, brave changes to the product. It was time to give the ideas we never had time to try out a chance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*QrMwffb_V4jkDu_CDMpWmw.png" /><figcaption>New welcome page</figcaption></figure><p>We worked on colors, fonts, spacing, the welcome page and all general elements.</p><p>We also worked on an import tool, improved the feedback button embeds and created mini cards.</p><h3>Day 313 — Sharing our product with the world</h3><p>Following eight hack weeks in 10 months, we were ready to pack up JotForm Cards and share it with the world.</p><p>We decided to give users both of the form layout options and wait for the test results to decide which design we’d use. But, none of the test groups could determine a winner.</p><p>We updated the test again, but this time, all of our new users were able to see both options.</p><h3>Day 327–Release!</h3><p>Finally! On February 6th, we announced JotForm Cards as our newest product.</p><p>For 326 days, we’d worked on this project full-time, day and night: poring over details big and small, fixing more than 280 bugs and implementing 102 feature requests. Phew.</p><p>Best off all, we succeeded in making a product that our users love.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*y-naup-C5fnBcAHT-hzhsA.png" /><figcaption>Launch day at Ankara Office</figcaption></figure><p>We hope you love <a href="https://www.jotform.com/cards/">JotForm Cards</a> as much as we do, and we can’t wait to hear your thoughts!</p><p><em>Originally published at </em><a href="https://www.jotform.com/blog/372-What-it-s-like-to-spend-326-days-on-a-massive-product-release-for-3-2M-users"><em>www.jotform.com</em></a><em>.</em>Thanks for reading.</p><blockquote>If you enjoyed this article, feel free to hit that clap button 👏 to help others find it.</blockquote><p>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4df6f9a9bdd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-its-like-to-spend-326-days-on-a-massive-product-release-for-3-2m-users-4df6f9a9bdd7">What it’s like to spend 326 days on a massive product release for 3.2M users</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Implement Color Search]]></title>
            <link>https://medium.com/jotform-form-builder/how-to-implement-color-search-96698bb5c659?source=rss-f5e46d629924------2</link>
            <guid isPermaLink="false">https://medium.com/p/96698bb5c659</guid>
            <dc:creator><![CDATA[Elif Ceren Dik]]></dc:creator>
            <pubDate>Sat, 20 Dec 2014 06:40:42 GMT</pubDate>
            <atom:updated>2014-12-20T06:40:42.802Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we implemented a color search for the JotForm Theme Store using color spectrum segments</h4><p>We have just launched a theme store for our users and we wanted to make it easy to find themes by color. When you are looking for a suitable web form design theme to match your website design, searching based on colors simplifies the process.</p><p>In this blog post I will explain how we created color search feature of <a href="http://www.jotform.com/theme-store/">JotForm Theme Store</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*xTeSmTwn5WOkPQ8RmPACkQ.png" /><figcaption>You can search for similar themes by clicking on one of the colors on a theme you are looking at. You can see an example by clicking on one of the colors <a href="http://www.jotform.com/theme-store/theme/santas-reindeer">here</a>.</figcaption></figure><p>When searching for colors, it is not enough to find exact matches. We need to also find themes with similar colors.</p><p>Our first approach was to generate all color values similar to the target color. This way you could search for the themes which contained one of the generated colors. This approach (generating similar color sets) looked like a simple and straightforward solution. But, when we started implementing it, calculating and comparing hundreds of colors turned out to be NOT an effective way to perform a color search.</p><p>We then found a better solution. Instead of calculating absolute values of similar colors, we have decided to <strong>divide the color spectrum into a certain number of segments</strong>, and then use those segment numbers for matching similar colors.</p><p>In this method, a segment refers to all similar colors in a specific area of the color spectrum. This means, if two different colors give same result after the segment number calculation, they could be considered as similar colors.</p><h3>So, How Do We Calculate a Segment Number?</h3><p>In the beginning of a color search process we first get the hex value of the target color, and then we convert it to the HSB (Hue Saturation Brightness) color model. Basically, we use HSB color model components to specify a unique number for each segment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/277/1*o7Y3zKxEoeVv7Ln2c1woXg.jpeg" /><figcaption>Source: <a href="http://www.tomjewett.com/colors/hsb.html">http://www.tomjewett.com/colors/hsb.html</a></figcaption></figure><p>The segment number calculation has 3 steps:</p><ol><li>Identify the area number according to saturation and brightness values.</li><li>Identify the layer number according to hue value.</li><li>Calculate the segment number</li></ol><p>We have divided the color spectrum into small pieces. This is a tricky process since the bottom of the color spectrum contains blackish colors while top left area of the spectrum contains colors which are approaching white. As a result of this, we did some adjustment before determining the boundaries of the segments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*migk9R5QCSDBL-0d3CL8ow.png" /><figcaption>Spectrum divided into segments</figcaption></figure><p>In the first step of the calculation, we simply specify the area number according to the color’s saturation and brightness values. It can be a number between 1 and 4 or 145 and 148. If the number is between 1 and 4 it means that the target is a shade of a color. If the area number is between 145 and 148 that means the target color is very close to black, grey or white. That’s how we know a color can be considered in a particular segment number.</p><p>Next, we calculate hue partition of the color. In the HSB color model, the hue component can be in an interval between 0 and 360. We have mapped this interval into groups which consists of 10 values. It’s possible to think every group of the hue component as a different layer. So, there would be 36 layers for the hue component. The result of this step finds the number for the corresponding layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*SZnXWDxhoJTpPRiq0-dgZQ.png" /><figcaption>Hue layers</figcaption></figure><p>Imagine that we have a divided color spectrum for every layer of the hue component. Then we give a number to the areas continuously (except black, white and grey) according their layer number. For example, the area number for a color with values (15, 80, 90) is 5. This is exactly what we are doing in the final step of the segment number calculation. The generated <strong>segment number of a specific color is a combination of an area number in color spectrum and the hue layer number</strong>.</p><p>In the color search algorithm that we are using for <a href="http://www.jotform.com/theme-store/">JotForm Theme Store</a>, we defined 148 different color segments by using this calculation. 144 of these segments are coming from 36 different hue layers that have 4 different areas on their color spectrum. 4 of them (145, 146, 147, 148) are the constant segments for black, dark grey, light grey and white.</p><h3>How Do We Match Themes Based on Segment Numbers?</h3><p>Segment number calculation is needed at two points in our system: saving themes and searching themes.</p><p>When someone is saving a new theme, we extract the 8 most commonly used colors and calculate their segment numbers. Completing this heavy work during the saving of the theme allows us to do less work during the search. Converting only search input color to its segment number is sufficient for generating search results.</p><p>When a user is searching themes by color, our goal is to return all similar colors as well, so we convert the RGB color model to the HSB color model, calculate its segment number and then return themes which contain the same segment number.</p><p>When we decided we needed a color search for the <a href="http://www.jotform.com/theme-store/">JotForm Theme Store</a>, we had no idea how much fun we were in for. We are excited to know that our users can now browse stunning form themes by color thanks to the simple solution we found.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96698bb5c659" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jotform-form-builder/how-to-implement-color-search-96698bb5c659">How to Implement Color Search</a> was originally published in <a href="https://medium.com/jotform-form-builder">Jotform Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>