<?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 Yuhan Li on Medium]]></title>
        <description><![CDATA[Stories by Yuhan Li on Medium]]></description>
        <link>https://medium.com/@yuhanli?source=rss-c5cc1922c2d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Vgq4pMuMJPbgKDXFW-gEdg.jpeg</url>
            <title>Stories by Yuhan Li on Medium</title>
            <link>https://medium.com/@yuhanli?source=rss-c5cc1922c2d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:30:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yuhanli/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[A  12306 Redesign Case Study]]></title>
            <link>https://medium.com/@yuhanli/a-12306-redesign-case-study-ac8f2d593e30?source=rss-c5cc1922c2d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac8f2d593e30</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[china]]></category>
            <category><![CDATA[spring-festival]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Yuhan Li]]></dc:creator>
            <pubDate>Mon, 27 May 2019 14:09:22 GMT</pubDate>
            <atom:updated>2019-05-27T14:09:22.662Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>A 12306 Redesign Case Study</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*m3fmjx094kqtepAXrNqXwA.png" /><figcaption>GIF by Chloe Jackson</figcaption></figure><p><strong>The Spring Festival Transport Season</strong></p><p>During The Spring Festival each year, millions of people move back home. It’s a huge stress test for the railway system. Why is it so hard for people to get home during those couple of days?</p><p>When everybody needs a ticket, it is a hard question for 12306 to decide whom to give it. Basically, millions of people order their ticket at the same time, it’s harder than hitting a lottery.</p><p><strong>A Railway Ticket APP designed by the Railway Ministry</strong></p><p>Back in 2010, it only has a PC web portal. It slowly covered all the railway infrastructure in China. 12306 APP didn’t come online until 2013. In 2015 Alibaba confirmed the ticket system is supported by their own web service. Today, 12306 has distributed up to 3.5 billion tickets. The picture on the top below are screenshots of 12306, the design is hideous, but it doesn’t even count as a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Cs3yGc1757mQhLp4jgR6A.png" /><figcaption>12306 Key Flow</figcaption></figure><p><strong>A Small Problem that Led to Many IPOs</strong></p><p>In 2012, Cheetah browser released an add-on for 12306. It attracted huge amount of traffic and became the income source for Jinshan. After that 360, sougou and many other browsers followed suit. They upgraded the add-on to support “一键托管”, which the API refreshed in millisecond until a seat is locked. It’s basically bots.</p><p>In July 2015, Xiecheng acquired Suanya with ￥0.1 billion. Suanya is a tiny startup with just two APPs: 智行火车票 and 订票助手. The two APPs had been grown virally for a year and took over the market. The railway ticket problem maybe tiny, but on other side of the lever is a solution called for by an enormous market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*nukK6xDq10VOqGARDe9qLA.png" /><figcaption>The Apps that made their IPO by solving the ticket problem</figcaption></figure><h3><strong>Painful Experience of Using 12306 in 2019</strong></h3><h3>🤦‍♀️</h3><p><strong>№1 Simply Forget to purchase ticket</strong></p><p>At 7:59 of the exactly 30 days before the Spring Festival Eve, you need to log into 12306 App and order the ticket exactly at 8:00! Otherwise, you have to wait till tomorrow 7:59. AND you have to stay one more day in Beijing doing nothing, because all the ticket has been sold for that day.</p><p>Worst of all, Spring Festival changes time each year, so you will need to check out calendar way before this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*OCcz5hwcgwbZdqlMmQxvbw.png" /></figure><p><strong>№2 You will never know how many ticket is there left</strong></p><p>This sounds like a joke, but it’s true. In this picture, it shows there are 11 tickets left for first-class-seat. But this number is calculated at the time your app finish loading information on THIS PAGE! Wait till you submit an order and realize all the tickets are indeed gone, you can’t help but wonder: why don’t they tell you earlier?</p><blockquote><strong>The Theory with Seat Locking: If you want to buy a ticket online, you need to wait in a line</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*Tp5dywgu1QIpX4oMP821iw.png" /></figure><p>If you want a seat on the 10:55 train, you may have to compete with millions of others, and only 100 of you will get one, it is a probability question. But when you can only choose one train to submit an order, it is an excruciating pain. Why can’t you choose more than one train? Because after your failed attempt with the 10:55 train, all the tickets are simply gone.</p><p>You know the success rate is very low, but Seat Locking is a lottery process where you can only choose one train. If your hand is fast, you will get first inline for the lottery. But if your hand is slow, your line is a very long one.</p><h3><strong>New Skill Acquired — Line Cutting</strong></h3><p><strong>Early Age of Line Cutting</strong></p><p>In early 2011, Seat Grabbing add-ons started appearing, and it was…free. People who had it installed became highly-equipped with the Seat Locking Lottery. They became loyal to the software and many followed their lead. Of course, people who didn’t have the knowledge and skills e.g. migrant workers, were soon marginalized and found themselves couldn’t make it back home even ONCE in a year.In 2013–2015, Seat Grabbing add-ons started taking over, users can order multiple seats and simply pay￥50 for each acceleration package. It’s like having multiple add-ons to help you cheat in a computer game. The more you pay, the higher the probability for winning the lottery.</p><p><strong>It’s all becoming a fair game</strong></p><p>It’s 7:30 on the morning when you got ready for this battleship. You paid ￥100 for VIP subscription on Xiecheng, then bought another ￥30 acceleration. Then you opened Qunar and bought another two ￥50 acceleration package. Just to make sure this works…you told yourself. At 8:05, all of your orders are still loading and refreshing, you opened 12306 and realized all the tickets are gone. It’s all like going back in history now. Indeed, when everyone started using money to cut lines, we became denominator in this probability calculation.</p><p><strong>Tackling the Math Question</strong></p><p>The problem of Supply and Demand is an economic one and the total supply remains the same. I think with Supply remaining the same. I can’t really solve the problem from the root and provide tickets for everyone.</p><p>But, I can redesign the system so there’s a redistribution within the demand itself. The key to redistribution is to increase the probability of seat locking of those who really needs the ticket. Usually, people who really need something is willing to devote more time and energy into this thing. So I can use this trait to redesign this system.</p><p>Below a simple graph exemplify the beginning, where add-ons were not yet invented</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*Ym3Dw6nRcx9Q0smAZSVH-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*_oo8lZVcx1KgZvry9IGr7w.png" /></figure><p><strong>Redesigned system</strong></p><p>What I intend for the system to change is to release the tickets in smaller batches and several times in a day. During the day, we could count the number of time the users tried and increase his probability of seat locking with each attempt. Therefore, the probability of seat locking will change.</p><p>People who use add-ons will have the same effect and probability. But since paying and not paying is basically the same. I think people will soon realize they are wasting money.</p><p>Ok, Now let’s take a look at the existing flow to see how to make alteration.</p><p><strong>A closer look at the current flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yw53bGN70upEOt1os0Yo6A.png" /></figure><p><strong>The Redesigned Flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hw2F1Q63V4pTSi-Wc98dkQ.png" /></figure><p><strong>Base on the Previous IA, this is the Redesigned Screen</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gf3SAKMT71QtXj7s4F71WQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XAS71rFdfqCAfTkjz1uA7w.png" /></figure><p>I added this fully new page to the design. It helps to provide several important information:</p><ol><li>The tickets of which date will be release on today</li><li>A timeline of when are tickets released, and in what amount</li><li>How many ticket are left now for the previous batches</li><li>A remainder of when the new batch opens and set an alarm for it</li><li>How many attempts I made today</li><li>A complete chart of the probability of winning for all the train I tried to lock seats today</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-DzLgfD1BUgse9gpRZgng.png" /></figure><p>Most things I did with this page is to get rid of information not related to ticket purchase. Adding a hundred more functions don’t make it easy to use at all. Beside, users never touch any thing besides the things inside the square.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bj3n4jJWPhi8xoOL-MXQ2g.png" /></figure><p>The number of seats left should be the same thing as “秒杀”designed for “双十一”, the number should no longer be static. Since the backend is already handle by Alibaba, we should expect this to be fixed soon.</p><p>I also changed the layout hierarchy to make time stand out more. But this is nothing new, Xiecheng and Qunar already have this in place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11sMOX5nhUncOWl8FpwHnA.png" /></figure><p>Most 抢票软件 already have this function. Trains are schedule at an 15–45min interval, users will have a range in mind when they order. By adding more options, they don’t have to guess which one will succeed out of pure luck.</p><p>The added module displaying the trains will also be ranked by probability of success rate. Users can select up to 5 trains per order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBWZXK4axN1HemFKLJVI5Q.png" /></figure><p>hmm…12306 is very considerate by using just a popup window, but this nerve-racking experience is better when I can actually see some more information.</p><p>The Seat Locking will still be a lottery, but more informed like a controllable experience. It is broken down into each train with success rate shown. If you fail this time, you should know how to approach this next time.</p><h3><strong>Reference</strong></h3><p>如何评价加速包的存在包</p><p>https://www.zhihu.com/question/53767670/answer/566474476</p><p>12306数据接口</p><p><a href="https://blog.csdn.net/lostinai/article/details/49719261">基于HTTPS协议的12306抢票软件设计与实现--相关接口以及数据格式 - lostinai的专栏 - CSDN博客</a></p><p>抢票软件竞品分析</p><p><a href="http://www.woshipm.com/evaluating/407013.html">http://www.woshipm.com/evaluating/407013.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac8f2d593e30" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>