<?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 Shuhei Fujita on Medium]]></title>
        <description><![CDATA[Stories by Shuhei Fujita on Medium]]></description>
        <link>https://medium.com/@shuheifujita?source=rss-3ce6f5fa984------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Hy8FDcUDa-kbX9EYBbUz_Q.jpeg</url>
            <title>Stories by Shuhei Fujita on Medium</title>
            <link>https://medium.com/@shuheifujita?source=rss-3ce6f5fa984------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:04:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shuheifujita/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[Behind the Scenes at Indeed Trust & Safety Team]]></title>
            <link>https://medium.com/@shuheifujita/behind-the-scenes-at-indeed-trust-safety-team-bd1a8fafe0d6?source=rss-3ce6f5fa984------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd1a8fafe0d6</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[indeed]]></category>
            <category><![CDATA[software-engineer]]></category>
            <category><![CDATA[content-moderation]]></category>
            <category><![CDATA[trust-and-safety]]></category>
            <dc:creator><![CDATA[Shuhei Fujita]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 21:01:21 GMT</pubDate>
            <atom:updated>2025-06-25T21:01:21.477Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndS87cMU-JEfKXC19XhsnQ.jpeg" /><figcaption>at Indeed Tokyo Tamachi office</figcaption></figure><p>Trust &amp; Safety work involves protecting users and maintaining quality on platforms that operate at massive scale. Indeed attracts 24 million visitors and sees 1.5 million new job postings every month in the Japan market [1], making user safety and content quality both critical and complex challenges. The Trust &amp; Safety (T&amp;S) team serves as the guardian of platform integrity, but the role’s responsibilities extend far beyond what most people imagine.</p><p>I worked for Indeed’s T&amp;S Japan team for 3.5 years, from 2019 to 2022. When I joined Indeed, I had little idea of what the Trust &amp; Safety role involved. Even today, after having left, I find it challenging to explain the role concisely because of how many different responsibilities it encompasses. Unlike the U.S. headquarters, where Indeed’s Trust &amp; Safety department was already large enough to clearly divide responsibilities among specialized teams, Japan team was still relatively small. This created a startup-like environment that allowed me to wear multiple hats and rapidly developing diverse capabilities.</p><p>This unique position offered an unexpected foundation for building universally valuable professional skills. The combination of small team dynamics and large-scale platform challenges created opportunities to develop expertise across policy development, technical implementation, and stakeholder communication. In this article, I’ll break down what Trust &amp; Safety entails and share the transferable skills and insights I gained from this multifaceted experience.</p><h3><strong>1. Policy Development: Translating Abstract Missions into Concrete Rules</strong></h3><p>One core responsibility of T&amp;S was establishing clear guidelines defining acceptable and unacceptable job postings, essentially setting standards for “high-quality content.” This required translating abstract concepts into actionable criteria for automated systems and human moderators.</p><p>Take, for example, the policy against keyword stuffing [2] [3]. Keyword stuffing is especially common in Japan’s job market, where employers overuse keywords to boost search visibility and appear welcoming to diverse candidates. Job descriptions overloaded with keywords were suspected of manipulating search algorithms and compromising readability. In this case, it was challenging to defining “poor readability” quantitatively. To address this, I analyzed user engagement metrics correlated with keyword density and established clear numerical guidelines.</p><blockquote><strong><em>Example of Keyword Stuffing:</em></strong></blockquote><blockquote><em>#FullTime #Employee #PartTime #PartTime #ShortTerm #DailyPay #HighIncome #NewListing #MenWelcome #WomenWelcome #InexperiencedWelcome #ExperiencedWelcome #MajorCompany<br> #StableCompany #TokyoStockExchangeFirstSection #CustomerService #Sales #CustomerServiceSales #Staff #BusinessDevelopment #SalesStaff</em></blockquote><p>[2]</p><p>This systematic approach to policy development became foundational to my professional toolkit. The process of breaking down abstract concepts, gathering supporting data, and creating measurable criteria taught me to define problems logically and support decisions with concrete insights — skills that proved invaluable across all aspects of my role.</p><h3><strong>2. Policy Enforcement: Automation and Technical Skills</strong></h3><p>After defining policies, the next step was operationalizing them on Indeed’s massive content database. We needed to rapidly and accurately detect violations among millions of job postings. This required leveraging technical tools such as keyword matching and machine learning.</p><p>For the keyword stuffing policy, violations were initially identified manually by content reviewers. Recognizing inefficiencies and inconsistencies, I proposed and implemented a regular-expression-based automation solution. This eliminated the need for manual review and ensured every job posting was consistently checked for violations.</p><p>Occasionally, new policy introductions or product updates led to sudden spikes in review backlogs, causing brief operational chaos. During these periods, I proactively identified bottlenecks and further automated tasks, helping restore stability.</p><p>Keyword stuffing was just one example of the policy enforcement work. We regularly reviewed other policies and their enforcement strategies, identifying opportunities for improvement. This involved developing automation scripts to detect new types of violations, analyzing manual moderation queues to refine review targets, and building moderation tools to streamline the human review process. This proactive approach to identifying and solving operational challenges was a core part of my role.</p><h3><strong>3. Content Moderation: Enhancing Business Communication Skills</strong></h3><p>Content moderation required extensive human collaboration despite our automation efforts. Our review operations involved working closely with outsourced moderation teams, internal Sales and Customer Support teams, and client companies. I hadn’ expected human-powered processes to play such a significant role behind the scenes of an IT-driven business, but this collaboration became central to effective policy enforcement.</p><p>Clear communication was essential for managing these complex stakeholder relationships. Supporting outsourced reviewers and making final decisions on nuanced cases demanded empathetic and precise communication. Early in my role, my communications regarding policy violations sometimes unintentionally caused confusion or frustration among stakeholders, highlighting the need for a more thoughtful approach.</p><p>Learning to communicate effectively with diverse stakeholders became one of my most valuable skills. Through trial and error, I developed the ability to clearly explain policy context</p><p>and rationale, offer reasonable correction timelines, and genuinely empathize with different perspectives. This communication-focused approach not only improved cooperation across all teams but also taught me skills that proved essential for any collaborative business environment.</p><h3><strong>Conclusion</strong></h3><p>My experience at Indeed’s Trust &amp; Safety team demonstrated how platform governance requires balancing three distinct but interconnected functions. The team operated like a complete governmental system:</p><ul><li>developing policies (legislative roles)</li><li>implementing them through automation and technical solutions (administrative roles), and</li><li>reviewing content through human judgment (judicial roles).</li></ul><p>This comprehensive approach was essential for managing platform quality at Indeed’s massive scale.</p><p>The role’s diverse responsibilities developed three universally valuable professional skills. I learned to define problems logically by translating abstract concepts into measurable criteria, improve operations through technology by building automation tools and systems, and communicate effectively with diverse stakeholders ranging from outsourced teams to client companies. Each skill reinforced the others, creating a foundation for tackling complex operational challenges.</p><p>These experiences equipped me with highly transferable capabilities that extend far beyond Trust &amp; Safety work. The combination of analytical thinking, technical problem-solving, and stakeholder communication creates a versatile skill set applicable across industries and roles. This foundation has shaped my approach to professional challenges and continues to guide my career development.</p><ul><li>[1] <a href="https://jp.indeed.com/%E6%B1%82%E4%BA%BA%E5%BA%83%E5%91%8A/indeed%E3%81%AE%E5%88%A9%E7%82%B9">https://jp.indeed.com/求人広告/indeedの利点</a></li><li>[2] <a href="https://indeedinc.my.site.com/employerSupport1/s/article/Policy-Keyword-Stuffing?language=ja">https://indeedinc.my.site.com/employerSupport1/s/article/Policy-Keyword-Stuffing?language=ja</a></li><li>[3] <a href="https://indeedinc.my.site.com/employerSupport1/s/article/Policy-Keyword-Stuffing?language=en_US">https://indeedinc.my.site.com/employerSupport1/s/article/Policy-Keyword-Stuffing?language=en_US</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd1a8fafe0d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experiment with Japanese Meal Kits in the U.S.]]></title>
            <link>https://medium.com/@shuheifujita/my-experiment-with-japanese-meal-kits-in-the-u-s-f1684f21a25e?source=rss-3ce6f5fa984------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1684f21a25e</guid>
            <category><![CDATA[food-industry]]></category>
            <category><![CDATA[japanese-culture]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[japanese-food]]></category>
            <category><![CDATA[lean-startup]]></category>
            <dc:creator><![CDATA[Shuhei Fujita]]></dc:creator>
            <pubDate>Sat, 10 May 2025 16:40:37 GMT</pubDate>
            <atom:updated>2025-05-10T16:40:37.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypnvyu92Hi8lsp0CE0vlvQ.png" /></figure><p>When living abroad, craving food from home is something almost everyone experiences. As someone who moved from Japan to the U.S., I also frequently find myself longing for authentic Japanese cuisine. Yet, busy lifestyles and the difficulty of sourcing authentic ingredients often make cooking traditional meals challenging, leading many to give up, thinking it’s too complicated or time-consuming. Motivated by this common experience, I decided to explore ways to simplify this process. Here’s my journey experimenting with Japanese meal kits in the United States.</p><h3>Turning Personal Struggles into an Entrepreneurial Idea</h3><p>A few months after starting my master’s program in the U.S., I noticed my health deteriorating. The cause was clear: my busy student life had led to poor eating habits. I often resorted to fast food or quick takeout meals due to convenience and lack of time.</p><p>With grocery stores located far from my dorm, I found meal kit services like Blue Apron and Hello Fresh a convenient first step toward healthier eating. After trying about 15 different services, however, I discovered that most offered mainly Western cuisine, with very limited options for Japanese or Asian meals. This gap sparked my interest in launching Japanese meal kits tailored specifically for the U.S. market.</p><h3>Meal Kit Industry in the U.S.</h3><p>The U.S. meal kit market is substantial, valued at around $10.4 billion [1], nearly ten times larger than Japan’s meal kit market of approximately $1.4 billion [2]. Despite this sizable opportunity, competition is fierce, with 382 companies actively competing for consumer attention [3].</p><p>Yet, Japanese meal kits appeared to be a unique niche. Approximately 1.6 million people in the U.S. (about 0.5% of the population) identify as Japanese or Japanese American. However, there were only two existing services, BentOn and Yoko Street, both focused exclusively on ready-to-eat meals. I found an unexplored niche in traditional “cook-at-home” Japanese meal kits.</p><h3>Gaining Valuable Insights by Sharing My Idea</h3><p>I strongly believe in openly sharing my ideas for constructive feedback. Discussing my meal kit concept connected me with professionals in Boston’s local food industry, who shared invaluable insights about industry challenges, effective marketing strategies, and competitive dynamics that I wouldn’t have discovered alone.</p><h3>Learning from a Small-Scale Experiment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mCMGZr-xU6SHXKOzoFZ8TQ.jpeg" /><figcaption>Assembling the meal kit with fresh, pre-portioned ingredients</figcaption></figure><p>With a clearer concept, I conducted a small pilot test with a group of friends. I personally handled everything — from choosing menus and sourcing ingredients to packaging and door-to-door delivery.</p><p>The experiment highlighted two significant challenges:</p><p><strong>First, menu selection:</strong> Half of the participants weren’t Japanese, and several had dietary restrictions such as vegetarianism or religious dietary preferences. Traditional Japanese meals like “Ichiju-sansai” (one soup and three sides) proved impractical due to recipe complexity and ingredient availability. Ultimately, I chose “Okonomiyaki,” a versatile savory pancake, as a suitable recipe for this first experiment.</p><p><strong>Second, pricing:</strong> The initial version of my recipe ended up being much more expensive than typical U.S. meal kit prices, which usually range from $8 to $15 per meal (including delivery). To bring the cost down, I had to cut out several ingredients and simplify the recipe as much as possible, eventually reducing the cost to about $8.63 per serving. I tested selling the kit at $12, but even then, profitability was difficult to achieve. It’s also important to note that in a real business, there would be additional expenses, such as marketing, hiring staff, and other operational costs, which I didn’t encounter in this small-scale experiment.</p><p>Participants enjoyed the food and experience, but their feedback suggested a shift from my original intention. While I had aimed for these meal kits to be a convenient option for everyday dining, participants felt they were better suited for special occasions or social gatherings, viewing them more as “food as entertainment.” Some even recommended expanding the concept to include a wider range of Asian cuisines, further emphasizing the appeal of variety and novelty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OksOhRXdJzZJnKrBsSTMPA.png" /><figcaption>Cost breakdown table used to calculate the price per serving for each meal kit</figcaption></figure><h3>Key Insights and Changing Direction</h3><p>While expanding into broader Asian meal kits was appealing, I realized this approach strayed from my original mission of encouraging healthier eating habits. Through the process of menu planning, it became clear that many traditional Japanese meals are quite carbohydrate-heavy, which doesn’t always align with daily healthy eating goals. Another challenge was geographic: with over half of Japanese and Japanese American communities located on the West Coast and in Hawaii, reaching my intended audience efficiently from Boston would pose significant logistical hurdles. Factoring in these difficulties, I decided to conclude the project after the experimental phase. Nevertheless, this experience sparked a deeper interest in health and longevity, ultimately steering me toward developing a digital wellness app that I’m currently working on.</p><h3>Conclusion: Important Lessons Learned</h3><p>This experiment taught me two key lessons:<br>First, openly sharing my ideas with others brought invaluable feedback and helped clarify my direction.</p><p>Second, even small steps-like running a limited pilot-provided real-world insights that I couldn’t have gained otherwise.</p><p>I plan to carry these lessons forward as I continue building meaningful products that align with my passions and values.</p><h3>References</h3><ul><li>[1] Grand View Research: <a href="https://www.grandviewresearch.com/industry-analysis/us-meal-kit-delivery-services-market-report">U.S. Meal Kit Market Report</a></li><li>[2] Japan Management Association Research Institute: <a href="https://search01.jmar.co.jp/static/mdbds/user/pdf/release_20200803.pdf">Japanese Meal Kit Market</a></li><li>[3] Wall Street Journal: <a href="https://www.youtube.com/watch?v=89u2Ftt23Sk">Meal Kit Market Analysis</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2uX0kke6XRXIuKRAY8XmOg.png" /><figcaption>A custom-crafted Okonomiyaki recipe, tailored for the ingredients included in this meal kit</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1684f21a25e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons I Learned from Growing My iOS App Beyond 50,000 Downloads as a Solo Developer]]></title>
            <link>https://medium.com/@shuheifujita/lessons-i-learned-from-growing-my-ios-app-beyond-50-000-downloads-as-a-solo-developer-a24636358af0?source=rss-3ce6f5fa984------2</link>
            <guid isPermaLink="false">https://medium.com/p/a24636358af0</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <dc:creator><![CDATA[Shuhei Fujita]]></dc:creator>
            <pubDate>Sun, 06 Apr 2025 16:13:19 GMT</pubDate>
            <atom:updated>2025-04-06T16:16:02.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stJLKPDUi0VGWcS3VsVUxA.png" /></figure><p>Last month, I officially ended the service for my iOS app, <em>TimeTable — Simple Class Scheduler</em>, which I had been developing and maintaining as a solo developer for six years. As my very first project, this journey was full of valuable lessons and insights that shaped my perspective on technology, business, and app development.</p><h3>About TimeTable</h3><p><strong>TimeTable</strong> was designed to help college students manage their class schedules and assignments. In Japanese universities, students often take more than ten courses per semester, making it challenging to keep track of weekly timetables alongside assignments and exams. I created TimeTable to simplify this process, offering features like schedule management, assignment tracking, and syncing with calendar apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*5VeYaHDY_ZE3PRrqn6upIw.png" /><figcaption>The main page of <em>TimeTable</em>, displaying a weekly class schedule in a clean, color-coded table format.</figcaption></figure><h3>Experiencing the Rapid Evolution of Technology and Market Dynamics</h3><p>Developing and operating TimeTable for six years gave me a front-row seat to witness the rapid pace of technological advancement in the smartphone era. When I started working on the app in 2014–2015, smartphones were just becoming ubiquitous, and cloud technology was emerging as a major trend. Around that time, Apple introduced iCloud compatibility for third-party apps, which allowed me to integrate cloud functionality into TimeTable without needing a server-based infrastructure. Within just two years, cloud services became mainstream — a transformation that felt remarkable at the time but is now taken for granted.</p><p>I also observed how quickly the app market matured into a highly competitive space. In 2015, the App Store was dominated by apps from independent developers like myself. Even within the niche category of class schedule apps, competition was sparse — most were created by students or hobbyists. However, over the next three to four years, competition skyrocketed as larger companies like Recruit Holdings Co., Ltd. (the parent company of Indeed Inc. and Glassdoor LLC) entered the market. The once “blue ocean” quickly turned into a “red ocean,” with established players solidifying their positions.</p><p>This experience underscored how rapidly IT technology evolves compared to other industries. Witnessing these shifts firsthand taught me valuable lessons about adapting to fast-changing markets — insights that will undoubtedly serve me well as I explore next emerging technologies like AI and the metaverse.</p><h3>3 Lessons in Business Strategy</h3><h3>1. First-Mover Advantage</h3><p>Launching TimeTable early in a relatively untapped market gave me a glimpse into the challenges of leveraging first-mover advantage. When TimeTable debuted, there were fewer than ten similar apps on the App Store. To stand out, I included features that competitors lacked: iCloud support, calendar syncing, iPad compatibility, and more. While these features gave TimeTable an edge in functionality, breaking through the dominance of higher-ranked apps proved difficult. Apps that already ranked high in App Store search results tended to maintain their positions due to user behavior favoring top-ranked options. Similarly, there were hardly any cases where newer competing apps surpassed TimeTable’s rank.</p><p>This taught me that even with innovative features, capturing market share requires more than technical superiority — it demands strategic marketing and user acquisition efforts.</p><h3>2. Monetization Challenges</h3><p>TimeTable’s revenue model relied on in-app purchases for premium features and banner ads within the app. Before launching, I estimated potential downloads and paying users based on the number of college students in Japan minus competing apps. However, my estimates turned out to be overly optimistic. While the conversion rate for paying users (2.8%) slightly exceeded expectations, overall revenue fell short due to lower-than-expected download numbers.</p><p>This experience highlighted how difficult it is to accurately predict user behavior and market demand without real-world data — and how critical it is to test assumptions early.</p><h3>3. Leveraging User Bases for Growth</h3><p>One key realization during TimeTable’s operation was the inherent revenue ceiling for timetable apps targeting college students. Since students typically have limited spending power and use such apps briefly each day, both in-app purchases and ad revenue remained modest. Observing competitors taught me how some companies overcame this limitation by leveraging their user bases strategically. For example:</p><ul><li>Recruit Holdings Co., Ltd.’s <em>Sugoi-Jikanwari</em> app capitalized on its college student user base by integrating part-time job listings directly into the platform, effectively aligning its services with the needs of its audience.</li><li><em>Penmark</em> integrated a student-only social network into its app as part of its monetization strategy.</li></ul><p>These examples emphasized the importance of planning beyond a single product — thinking about how to grow a business by connecting one service to another.</p><h3>Final Thoughts</h3><p>I’m deeply grateful to everyone who used TimeTable over the years. All the reviews and feedback from users motivated me throughout this journey and helped shape the app into what it became. A special thanks goes out to my friend M — your honest feedback during beta testing was invaluable.</p><p>Reflecting on these six years has been incredibly rewarding. While TimeTable has come to an end, the lessons I learned from this experience will guide me as I pursue future projects in technology and entrepreneurship.</p><p><em>(This article is adapted from my </em><a href="https://medium.com/@shuheifujita/ios%E3%82%A2%E3%83%97%E3%83%AA-6%E5%B9%B4%E9%96%93%E3%81%AE%E9%96%8B%E7%99%BA%E3%81%BE%E3%81%A8%E3%82%81-fcddd98347c8"><em>original Medium post</em></a><em> in Japanese published on December 31, 2021.)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a24636358af0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOSアプリ 6年間の開発まとめ]]></title>
            <link>https://medium.com/@shuheifujita/ios%E3%82%A2%E3%83%97%E3%83%AA-6%E5%B9%B4%E9%96%93%E3%81%AE%E9%96%8B%E7%99%BA%E3%81%BE%E3%81%A8%E3%82%81-fcddd98347c8?source=rss-3ce6f5fa984------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcddd98347c8</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[smartphones]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Shuhei Fujita]]></dc:creator>
            <pubDate>Fri, 31 Dec 2021 15:49:02 GMT</pubDate>
            <atom:updated>2021-12-31T16:13:20.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uFxoYf-OyFlDV3Um7XdVw.jpeg" /></figure><p>先月、6年間自身で開発と運営を続けてきたiOSアプリ <a href="https://timetable.mystrikingly.com/">シンプルな時間割-TimeTable</a> のサービスを終了しました。初めて取り組んだプロジェクトから得られた経験・知見をまとめます。</p><p>TimeTableは、大学生が授業のスケジュールや進捗をトラッキングできるiOSアプリです。日本の大学では１学期に10以上の科目を履修します。1週間のスケジュールやそれぞれの課題・テストなどの管理が大変で、このアプリを作成しました。</p><p><strong>技術・市場形成の速度を実感</strong></p><p>6年間アプリの開発運営を継続したことで、スマートフォン関連技術の移り変わりを直に体験できました。私がこのアプリを開発した2014〜15年当時はスマートフォンが普及したてで、「クラウド」がトレンドになっていた時期でした。ちょうどiCouldがサードパーティアプリでも利用可能となり、TimeTableでも早速対応しサーバーレス開発の恩恵を受けました。クラウドはその後2年弱で普及しました。現在は当たり前に使用されていますが、普及の速度感を実感することができました。</p><p>またアプリ市場が3–4年かけてレッドオーシャンと化していく様子も間近で目撃しました。2015年当時、App Store上では個人開発者によるアプリが中心でした。時間割アプリも同様で、私のように学生が開発したアプリが両手で数えられるほど存在するのみでした。それが年々加速度的に競合が増えていき、時間割アプリというニッチな市場であっても、現在では(株)リクルートを始めとする企業プレーヤーも参入するほどに成熟しました。</p><p>IT技術の進歩は他の産業と比べ特に早いと言われています。スマホアプリ市場を通してそれを若い時期に実感できたことは、今後AIやメタバースなどの新しい技術に取り組む際の良い知見となりました。</p><p><strong>ビジネス戦略の教訓</strong></p><p>TimeTableの運営を通して、ビジネス戦略の基本も学ぶことができました。</p><p>１つ目は、先行者優位。既に市場に競合がいる場合その牙城を崩すにはかなりの有利性が必要になるということ。TimeTableをリリースした際、App Storeには10に満たない類似アプリが存在していました。TimeTableにはそのどれにもなかった機能 — 時間割管理の基本機能に加えて、先述のiCloud対応・カレンダーアプリとの同期機能・iPad対応などのアドバンテージをつけた上でリリースしました。既存アプリのシェア獲得に自信を持っていましたが、それは想定以上に困難でした。App Store上の検索結果で既に上位を占めていたアプリは、たいていそのランクを維持し続けました。やはり多くのユーザーは検索結果上位に流れるため、ランキングが固定される傾向があるのではないかと推測します。同様に、 TimeTableの後にリリースされた類似アプリがTimeTableを追い越すケースはあまり見られませんでした。</p><p>２つ目は、収益化戦略の失敗経験。TimeTableのマネタイズは一部機能を有料としたアプリ内課金とアプリ上に設置した広告バナーを利用しました。プロジェクト開始前に、想定ダウンロード数・課金ユーザー数を計算していましたが、これが大きく外れました。日本全国の大学生数と競合アプリ数から導いた数字で、分母を大きく見積り過ぎていました。一方で、課金ユーザへのコンバージョンは2.8%と想定をやや上回りました。このような数字は、実際にリリースしてみないとわからないのだという印象を得ました。</p><p>３つ目に、ひとつのサービスを次に繋げるという視点。他ジャンルのアプリに比べ、時間割アプリそのものの収益は小さいです。学生ユーザをターゲットとするためユーザあたりに大きな課金が期待できず、またアプリの性質上ユーザの滞在時間も短く広告収入も上がりません。TimeTableの運営中に感じた天井でした。一方で競合アプリ(株)リクルートによる「<a href="https://www.sugojika.com/">すごい時間割</a>」では、アプリ内に学生向けのバイト求人情報を掲載することで獲得したユーザをレバレッジしています。また、前澤ファンドに投資された「<a href="https://penmark.jp/app-link">Penmark</a>」では、学生限定のSNSを組み込みマネタイズを図っているようです。このように、獲得したユーザをどう活かすか・ビジネスをどう次のステージに持っていくか、という視点を学びました。</p><p><strong>おわりに</strong></p><p>TimeTableを使用してくださったみなさんに感謝します。また、レビューやフィードバックを送ってくださった方々、大変ありがとうございます！本当に励みになりました。そして最後に、リリース前から１ユーザとしてTimeTableを使い続け、率直な感想とアドバイスを共有してくれた大学の友人Mにspecial thanksを送りたいと思います。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcddd98347c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>