<?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 Presto Kaung on Medium]]></title>
        <description><![CDATA[Stories by Presto Kaung on Medium]]></description>
        <link>https://medium.com/@prestokaung.ux?source=rss-102dd6eb734d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4RgzMPE8AJZKc-5e0InTfA.png</url>
            <title>Stories by Presto Kaung on Medium</title>
            <link>https://medium.com/@prestokaung.ux?source=rss-102dd6eb734d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 04:57:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prestokaung.ux/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[Everyone now makes apps. But you must know this.]]></title>
            <link>https://medium.com/design-bootcamp/everyone-now-makes-apps-but-you-must-know-this-3c1349ef1c2c?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c1349ef1c2c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 07:07:24 GMT</pubDate>
            <atom:updated>2026-01-24T12:33:52.886Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RILVtk6ZVYKt7rQirpPQTA.png" /></figure><p>(Presto Kaung didn’t wrote this with AI 😄)</p><p>I know you don’t have time, so here’s the AI summary!</p><blockquote>The article, written from a personal perspective, describes the author’s surprise at his girlfriend building a functional AI-powered Chinese language practice app in under 12 hours using AI tools. He contrasts this with his own early struggles in app development a decade ago, highlighting how AI has lowered barriers to entry. However, he warns of pitfalls: rising costs as usage scales, dependency on third-party services leading to “walls” (e.g., vendor lock-in), poor code quality from AI-generated code that’s hard to maintain or scale, time sinks from debugging AI’s errors, and a “progress-void” where users don’t gain deep skills, potentially stifling long-term growth. He concludes that AI is a powerful tool but emphasizes the need for intentional thinking over lazy reliance, urging readers to use it to enhance human strengths like critical thought.</blockquote><h4>My girlfriend made an app faster than I did</h4><p>One morning in Jan 2026, I found my girlfriend practicing Chinese with what looked like an app. I later found out that she had built the app for herself.</p><p>I showed her how do use Google AI Studio last night. It didn’t even take her 12 hours to build and use it. On top of that, she created an AI conversational practice tool. Not just a normal app.</p><figure><img alt="Two lines of images. First line showcases home screen of a language learning app, conversation-mode of the app in mobile size. Second line showcases vocab screen of Chinese language learning app and home screen of Thai language learning app." src="https://cdn-images-1.medium.com/max/1024/1*WaYSnfj8Lf0qZkp7VYwQDg.png" /><figcaption>My Girlfriend’s app Chinese and Thai Learning App with Conversation Practice (She didn’t even know what API is). And did all this in just one night.</figcaption></figure><p>When I started, not even 10 years ago, there was no shortcut, no other way but grinding after grinding to get an ugly-looking app. It took me over 20 failures and a lot of learning in product design and programming to be able to build what I consider extremely quick MVP apps.</p><p>Yet, I was no match.</p><h4>That satisfying feeling of seeing your first app</h4><p>Drama aside, I have been seeing this trend all over my friends and family. AI has grown quite a lot, and big companies are giving it away for free. Free to consumers but clever enough to constantly search for ways to make money.</p><p>Everyone knows that AI is costly and time-consuming. But for someone who has always considered app-making to be beyond several barriers to reach, this is an extremely satisfying feeling.</p><p>Even for me, seeing an app I created is one of the most joyous moments every time.</p><p>This is not AI helping us. AI companies have simply found a deep desire and need in almost everyone.</p><p>One of your daily problems is solved by an app you just made in a few minutes, something you couldn’t even imagine a year before. I can totally relate to how cool it is, how proud and satisfying it feels. I would share it with others. They can also start to create, and domino effects will begin.</p><p>But there are a few problems.</p><h4>App-generation is different from photo/video generation</h4><p>We were able to create images and videos easily while they were still in “preview,” when companies pretended to be “generous.” As these companies learned we can’t live without these tools, a cost emerges, one that can’t be justified for something we are making just for “fun.”</p><p>Simply put, it is too expensive. Before AI tools, a $20 or $40 monthly subscription was already absurd let alone $200 a month.</p><p>For generating your app with AI, there is one more catch.</p><p>Once you generate an image or a video, you don’t need to keep paying to use it. Once it’s out, it’s yours forever.</p><p>Apps are different.</p><p>Yes, you can technically still use them. But sooner or later, they are bound to hit a wall.</p><p>What wall?</p><figure><img alt="Title text  peeping from a brick wall image that says “Hidden Cost”" src="https://cdn-images-1.medium.com/max/1024/1*o17Nq5pqynUB6QOev3uwbw.png" /></figure><h4>Hidden Costs</h4><p>Apps use multiple services to function — not just one. This might be an over-generalization, but let me explain.</p><p>Imagine you just opened a restaurant. You were given a place, some cool meals to sell, and a waiter to serve ready-made, all for free.</p><p>If there are only a few customers, you’re fine. As soon as you have more customers, you need to expand. But since you are using our space, our food, and our waiter, we now have special pricing for you if you want to continue.</p><p>Then you find out you could have cooked yourself, hired your own waiter, and opened the restaurant in your garage for much less.But your customers already know this place too well and they especially love your food.</p><p>Now you’ve hit a wall. That wall.</p><p>This is by no means an evil agenda or trick. It exists as a well-known business model and tactic in modern service providers. It’s just that people who are not from this world don’t have a clue about it.</p><figure><img alt="Title text peeping from a brick wall image that says “Hard to Scale”" src="https://cdn-images-1.medium.com/max/1024/1*a2L3xNd8c7FqQ1hNVsigSg.png" /></figure><h4>Generated apps are difficult to scale</h4><p>Let’s say that since everyone loves your app, there is a chance. So you pay for everything, continue, and start to scale it.</p><p>This leads to another big problem.</p><p>There is one thing app creators and programmers really hate: repairing (or rescuing) an app made out of bad code. By “bad,” I mean code that is not optimized, not easy to read, and not easy to fix when errors appear. There are techniques and practices to avoid this.</p><p>AI can read and write code at a god-level. Because of that, it doesn’t need to write code structurally for <em>itself</em>. If you don’t specifically mention it, AI will program in a way that is most efficient for it.</p><p>And then AI forgets.</p><p>As of right now, AI has a limit on how many things it can remember. This is the same problem as not being able to give a whole textbook’s worth of text to AI.</p><p>Imagine a clothing shop. Instead of storing and displaying items properly, customers ask a person, and he searches and picks clothes from a pile. He is really, really fast.</p><p>But soon, you open another six shops. The pile grows bigger than ever. This very fast guy now can’t remember everything and starts making serious mistakes.</p><p>We chose the piling-clothes approach because he was extremely fast.</p><p>Now he forgets. And that is the big problem with scaling AI apps.</p><p>As your app grows, you need to expand not only storage but also logic to run bigger tasks or more tasks at the same time.</p><p>What makes this worse is that if AI forgets and makes an error, it can create a cascading effect. Even AI will struggle to understand where the problem is.</p><p>When ChatGPT first launched, we could only send a limited number of words. No memory. No context. Now it can handle much more and it will keep getting better every year. But welcome to the big invoices.</p><blockquote><strong>You can skip this if you are not into coding.</strong></blockquote><blockquote>Here are specific examples of what I mean by ‘bad code’.</blockquote><blockquote>AI sometimes doesn’t do modularization at all. It writes everything in one file. On the other hand, it separates everything into classes and methods all the time, making it too hard to read.</blockquote><blockquote>Even though AI knows what’s the latest, its ability comes from training on past coding methods, and it keeps using deprecated methods.</blockquote><blockquote>Even with existing classes and constants, AI sometimes doesn’t care about them and chooses to code from scratch again. E.g., it neglects a few color constants and just uses hex codes as it sees fit. And it is difficult to notice it if you don’t double-check.</blockquote><blockquote>AI’s current context window is not enough to handle complex logic. So unless a person is thinking through all the logic, AI will just make assumptions and do it anyway. And it pretends it did the best job in the world like a proud puppy.</blockquote><blockquote>The worst-case scenario is what I will say in the next part.</blockquote><blockquote>AI sometimes takes a burn-it-all approach to fix a tiny bug. In fixing bugs and errors, it only focuses on fixing them at the cost of breaking down everything we have built. One time, it deleted and switched all my typography and colors. But the app still worked, and we didn’t notice it until it was too late.</blockquote><figure><img alt="Title text peeping from a brick wall image that says “Time Sink”" src="https://cdn-images-1.medium.com/max/1024/1*35Kx2fFPaNVd6VPfk2aOWg.png" /></figure><h4>Time-sink</h4><p>Then there is the biggest problem of all.</p><p>One thing you will hear from anyone who has built a proper app with AI is this: it is time-consuming. It feels like you are sitting next to a <em>brainless genius</em> all the time.</p><p>Everyone wants to polish their app just a little bit. That “little bit” quickly turns into hours, then days.</p><p>My girlfriend stopped tweaking her app once she realized half of her day was spent on it, and she could no longer focus on her actual work. It was fun but not worth that much precious time.</p><p>One major culprit of this time sink is AI’s sudden slips and extremely foolish errors like extra fingers in AI-generated images.</p><p>Since non-programmers don’t know how code works or what things are called, going back and forth with AI to fix simple issues can take hours. In this sense, it becomes very counter-productive.</p><p>I have seen AI create logic that would have taken me more than two days in one minute. Then struggle for hours to fix an extremely simple error like a missing bracket.</p><p>In the worst-case scenario, AI uses a “<strong>burn all the houses to find the needle</strong>” approach. I have seen this happen several times in my own apps.</p><p>Time-consuming is an acceptable trade-off given what AI can help us achieve.</p><figure><img alt="Title text peeping from a brick wall image that says “Progress-void”" src="https://cdn-images-1.medium.com/max/1024/1*THQsa8HE_8jKPuAMCRBXSg.png" /></figure><h4>Progress-void</h4><p>But the real effect of this problem becomes apparent over a longer time frame.</p><p>When we do something for a long time, we start noticing intricate details and gradually become very, very good at it. This happens over months and years. This is one of the reasons juniors eventually grow into seniors.</p><figure><img alt="A graph with x axis from 2026–2032. A curve that shows human learning reach to peak faster. A line that represents a human working with AI without learning, not able to peak and hits a plateau early." src="https://cdn-images-1.medium.com/max/1024/1*yBzgFNmX24im8ARJMmU9DA.png" /></figure><p>If you spend months talking to AI to build your app, you learn nothing except how to quarrel with AI over its sudden and costly hiccups.</p><p>You can replace a junior programmer with AI today. But in three years, you will get another AI, just more powerful.</p><p>That junior programmer, meanwhile, gains experience, sharpens skills, builds intuition, and becomes a partner who can support you with much more than just coding.</p><p>This “progress-void” nature of AI also affects us.</p><p>We become better prompters but we don’t learn how code works, how logic flows, or how to build intuition. People are intrinsically lazy when it comes to thinking. We prefer asking over understanding what AI actually did.</p><p>What happens if we stop thinking for five years?</p><figure><img alt="A side by side mobile screen. Left image is a mobile app screen done by author in 2021, right one in 2026." src="https://cdn-images-1.medium.com/max/1024/1*TXLMOrZcVoO7KliNg3jvEg.png" /></figure><h4>AI is actually good and going to help us.</h4><p>AI is really good. I repeat AI is very, very, very good.</p><p>It sped up my workflow by 70–80% and helped me do things I couldn’t even imagine before, like building a game.</p><p>What I am trying to say is simple.</p><h4>It is a tool</h4><p>It is the same thing everyone is already talking about: AI is a better writer, a better planner, a better knowledge base, and a better builder. But it is still just a <strong><em>better tool</em></strong>.</p><p>We should not cloud ourselves with the speed and fun of using AI.</p><p>We must know when the fun stops and when things become real. At that point, we have to treat it as such — get clear on what we want to achieve, analyze the prospects, accept the learn–build–improve loop, plan accordingly, and build intentionally and patiently.</p><h4>Don’t be lazy</h4><p>In short, think harder and leave the manual labor to AI.</p><p>AI is not here for us to be lazy. It is here so we can focus on the one thing humans still do best: <strong><em>thinking</em></strong>.</p><figure><img alt="An image saying “Hello” and Authro’s avatar image that says “I am Presto”" src="https://cdn-images-1.medium.com/max/1024/1*_g46F2NreUJZBfOqfbLxUg.png" /></figure><p>I am a 7+ years product designer and strategist. I love making apps enough to leave my medical doctor profession. I have worked on various kinds of 100+ app and projects but mainly in ‘product design’ space.</p><p>Today, I use all my experience, learning, templates and assets to transform raw ideas into <em>real apps</em>. (known as the first app/MVP App).</p><p>Not just UX Design, not just code. But the understanding of principle of ‘Product’ as a whole.</p><h4>If you are interested in what I do, you can find me here.</h4><p>My Website 👉 <a href="https://prestokaung.com/,">prestokaung.com</a></p><p>I help founders build their first app 👉 <a href="https://spacematterapps.com/">spacematterapps.com</a></p><p>Fun videos about products 👉 <a href="https://youtu.be/uXpDmI4Wibo?si=aoeCacNbVQD_JMw-">Presto Kaung Youtube Channel</a></p><p>My Social Media: <a href="https://www.instagram.com/prestokaung.ux/">Instagram</a> | <a href="https://x.com/prestokaungux">Twitter(X)</a> | <a href="https://www.linkedin.com/in/prestokaung/">LinkedIn</a></p><p>Cheers ! Have a great day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c1349ef1c2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/everyone-now-makes-apps-but-you-must-know-this-3c1349ef1c2c">Everyone now makes apps. But you must know this.</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>
        <item>
            <title><![CDATA[Building apps as a team — things I learned the hard way]]></title>
            <link>https://medium.com/design-bootcamp/building-apps-as-a-team-things-i-learned-the-hard-way-5b8505f0b8a7?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b8505f0b8a7</guid>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Thu, 04 Jul 2024 08:48:16 GMT</pubDate>
            <atom:updated>2024-07-04T08:48:16.612Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building apps as a team — things I learned the hard way</h3><figure><img alt="Image showcasing 5 applications in mobile mobkups." src="https://cdn-images-1.medium.com/max/1024/1*23Hzj40h9O7b81MQuD6MNQ.png" /><figcaption>5 apps that I am currently working on</figcaption></figure><p>I am usually the product guy who specialize in mobile apps. But these points are usually not that specific to mobile apps.</p><h3>On Goals</h3><p>Goals are generally accepted and widely understood, but they mostly exist as an on-paper concept. The word “goals” is also slowly becoming a cliché. However, it took me some shameful moments and humiliations to truly understand the need for goals.</p><figure><img alt="Sketch on the left — a group of people understanding different goals. Sketch on the right — a group of people agreeing on one single goal." src="https://cdn-images-1.medium.com/max/1024/1*OtgKldJ5B6s30cba-i5WCg.png" /></figure><h4>🤝Mutual understanding</h4><p>It is crucial that everyone in the team, including the marketing team and engineers, mutually agrees on the goal. The goal must strike a sweet spot where it addresses user needs and business objectives. It should not be ambiguous; it must be very clear. (I have seen three products I worked on being delayed and eventually discarded due to misalignments in the stakeholders’ goals.)</p><figure><img alt="Sketch on Left: a person thinking how to get from point A to B without considering the path. Sketch on Right: a person thinking how to get from point A to B considering the path and planning it." src="https://cdn-images-1.medium.com/max/1024/1*kMogUckcyhL29qoLOridNw.png" /></figure><h4>🧭Clear strategy</h4><p>Following the goal requires a clear strategy. The team needs to understand how the current solution will impact the goal and what might come next based on possible outcomes.</p><figure><img alt="Sketch on Left: a group of people doing meeting for all 3 weeks. Sketch on Right: a group of people doing meeting on week1, planning on week2 and testing prototype on week3." src="https://cdn-images-1.medium.com/max/1024/1*7p7EvajIXPYrY2XSyetjcQ.png" /></figure><h4>🚀Actions</h4><p>The team needs to quickly agree on the plan and proceed without fearing failure. They should adopt a hypothesis-driven development approach for a fast and effective path to the final product.</p><h3>On Product</h3><p>User-centric product solutions have become the standard. However, most companies address this by simply hiring a UX researcher and designer. A user-centric solution is not just the responsibility of the UX team; it is a mentality that the whole business must adopt.</p><figure><img alt="Sketch of a person who represents target users giving wrong feedback to application prototype." src="https://cdn-images-1.medium.com/max/1024/1*C3gAB3cUKtYI1ooxNdaKTQ.png" /></figure><h4>👥 Correct Feedback</h4><p>It is important to get accurate feedback from the right people who represent the target audience. The feedback should also be honest. We should not worry about not getting the result we want. It is best to avoid getting feedback from experts, evangelists, and enthusiasts during the early prototype stages.</p><figure><img alt="A sketch of see-saw with group of people representing user-centric design on the left and money bag representing business needs on the right." src="https://cdn-images-1.medium.com/max/1024/1*E4ZKBGB98Ua5ibA1cjqJ2g.png" /></figure><h4>👥 Balance</h4><p>Users are important, but so is the business that is sponsoring the project or product. We are not solving problems for just one side; we are mostly balancing the solution by building good relationships with both sides. (I usually stay out of business objectives in my work, but my lack of interest in that area becomes a weakness when I start my own business ventures.)</p><h4>💯 Action</h4><p>Even though feedback is very important, it is not as useful if no actions are planned afterward. We must be very clear about what comes next.</p><figure><img alt="Sketch on Left: A group of people giving random answers to survey questions. Sketch on Right: Two individuals giving response to usability testing" src="https://cdn-images-1.medium.com/max/1024/1*K7WzlhmYnyM44AevvSJXfQ.png" /></figure><h4>👍 Qualitative approach</h4><p>Qualitative approaches, such as speaking, observing, and interviewing 5–7 people, are better for getting feedback on early-stage products. A quantitative approach requires a large sample size to get reliable answers, which means significant resources like time and money are needed. This approach is more suitable when the product is already successful and needs to be optimized for greater success.</p><h3>On Teams</h3><figure><img alt="Sketch on Left: A group of people pushing a cart in opposite direction. Sketch on Right: A group of people pushing the cart in one single direction." src="https://cdn-images-1.medium.com/max/1024/1*nHuRJZqHUd_rY4qj5YuDhA.png" /></figure><h4>⚙️Systems Thinking</h4><p>It’s easy to get lost in titles and roles, and who will do what. We shouldn’t limit what we create based on our roles, titles, or departments. It’s better to solve problems as a unified team.</p><figure><img alt="A sketch of a software engineer amazed by a thick 3000pages-book which is labelled as Ultimate Design System" src="https://cdn-images-1.medium.com/max/1024/1*DaM3YYsmVd-fEBazsqoJ4Q.png" /></figure><h4>🎨Design Systems</h4><p>The existence of large, impressive design systems might suggest that we need to invest significant time in building something similar. However, it doesn’t have to be a grand, ambitious solution from the start. We have to start small. Design systems are created for efficiency, not to add pressure.</p><h4>👨‍💻 Extends to code</h4><p>A design system works best if that is built together with engineers.</p><h4>📏 Rulers not containers</h4><p>Design systems are not intended to limit creativity but to streamline processes. They should be flexible to accommodate better solutions as they arise.</p><h4>🧑‍🎓Continuous learning</h4><p>Continuous learning is not just learning. It is a mindset that you are a student at all times. It works best if the entire team fosters this mentality.</p><figure><img alt="A sketch represting a goup of people taking all the time they want and don’t get any result after 3hours of meeting." src="https://cdn-images-1.medium.com/max/1024/1*4ovxjhOs4u7nWCyvOL0XaA.png" /></figure><h4>⏰Time-bound</h4><p>Deadlines are not time-bombs but reminders. Without a visible date in line, it is easy to get lost in brainstorming, aligning and agreements.</p><h4>🔬Avoid mirco-management</h4><p>Delegate responsibility to team members and trust them. If we already have agreed on the goal, we should not interfere with them until the time for feedback has come.</p><h3>On Growth</h3><p>This is an area I completely neglected, and it dealt the biggest blow when I started building my own apps. Even if you don’t aim to be a unicorn startup or achieve massive wins, neglecting growth can seriously undermine your confidence.</p><h4>🚀Growth strategy</h4><p>It is really important to get the first working product right. But it is equally important to have a good growth strategy when that happens. Even if we are focusing on working solutions first, we should have some sort of plans for the growth of this product.</p><figure><img alt="Sketch on Left: Angry users who represents users who lost trust to the brand. Sketch on right: a smart phone with heart icon representing the app with good brand loyalty." src="https://cdn-images-1.medium.com/max/1024/1*dN-U_2ZALsCQLoO2haxJYg.png" /></figure><h4>❤️Loyalty and trust</h4><p>Human relay feelings and give recommendations on products all the time. It might look like it is too early to build this but once a person feels something about your product, it is really difficult (or very costly) to change his mind again.</p><h4>💼 Know how to sell</h4><p>Even with the best sales guy, there is a big difference in selling something you believe in and selling something you don’t know. It is really important to onboard the marketing, sales and customer support team why you made the product.</p><figure><img alt="Sketch on Left: An app with money bags behind representing an app that only cares about making money. Sketch on Right: An app with loyal customers behind representing an app that cares about users." src="https://cdn-images-1.medium.com/max/1024/1*v17wA2w4Ghag6iB9wM-9Kw.png" /></figure><h4>💰 Money is not the only one</h4><p>Growth isn’t solely about increasing daily active users and paying customers. While revenue growth may be a primary objective, expanding in areas such as brand loyalty, trust, and values is equally crucial. (I have designed a program as per business objective which is to grow revenue. But we somehow couldn’t get the desired result. We later found out that the program is not working well because we lack growth in other areas we thought spending money is a waste of time and money)</p><p>One final thing..</p><figure><img alt="A sketch showcasing a path with obstacles. Four chracters crossing the path represents how they are overcoming it." src="https://cdn-images-1.medium.com/max/1024/1*AKsK9QVSgXzegBD2qITJ0g.png" /></figure><p>I always believe it is important to have fun building apps. I will already be at a disadvantage when I start my idea with pressure and stress. It really reflects on the end product.</p><p>I hope I didn’t misuse your time reading this. I hope these points are helpful for you.</p><p>Hello, I’m Presto! 👋 I’ve been obsessed with mobile applications since the start of Android and iOS. I enjoy writing my observations on how apps impact our daily lives.</p><p><a href="https://www.youtube.com/@prestokaung">Youtube</a> | <a href="https://x.com/prestokaungux?t=W9J10DEo2Aeux0NJydzvoQ&amp;s=09">X(Twitter)</a> | <a href="https://www.tiktok.com/@presto.kaung?_t=8njOmLwkXWq&amp;_r=1">Tiktok</a> | <a href="https://www.linkedin.com/in/kaunghtetkyawuiux?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=android_app">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b8505f0b8a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/building-apps-as-a-team-things-i-learned-the-hard-way-5b8505f0b8a7">Building apps as a team — things I learned the hard way</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>
        <item>
            <title><![CDATA[Agile We — how a UX Designer made his first app]]></title>
            <link>https://medium.com/@prestokaung.ux/agile-we-how-a-ux-designer-made-his-first-app-cc8e98ead58c?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc8e98ead58c</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 14:02:52 GMT</pubDate>
            <atom:updated>2024-01-22T14:02:52.199Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gp0xD0ZWcnFI0WKiaWCV6Q.png" /></figure><h3>Agile We — how a UX Designer made his first app</h3><p>In this one cold January 2024 morning, my developer friend and I was quite excited to see that our first app was verified to be released in the Playstore. There were millions of apps being uploaded, it might be too simple of a thing to care for most developers. But for me, this day was what I have dreamed of 11 years ago.</p><p>From the first days I put my hands on iPhone 3S and HTC myTouch4G (with Android 2.2), I followed smartphone apps with similar energy as the fandoms of K-pop stars. I went to internet cafes everyday just to read about what’s new with apps. I downloaded almost every new apps back then. It was my hobby. But only after I graduated from Med school ( and a year of intern), I decided to stop dreaming and start making apps for real.</p><p>But as you know, the business of making app is rough these days. And it is quite absurd to dream about apps when I am based in a third-world country without a good startup ecosystem. Anyway, my story is not about that. I am here to share how my passion for apps leads to my very first app. Just want to share how fun and insightful of a journey it is. So here it goes.</p><p>It is about 10min read.</p><h3>Part I : About the app</h3><p>Simply put, this is another to-do list app. But with a twist.</p><ul><li>Agile We is a to-do list system to help you <em>figure out your goal</em> rather than just to scratch-off the tasks for the sake of productivity.</li><li>It is a <em>delightful and lightweight</em> tool for personal use.</li><li>And based on <em>agile project management.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*ZadJAazoqeHSn_zuC6Tnxw.png" /><figcaption>Two main screen of <a href="https://agilewe.spacematterapps.com/">Agile We</a> App</figcaption></figure><ol><li><strong>Overview of where you are heading </strong>: All the goals and their progress are visible at a glance. This help me understand the big picture and the direction towards my goals.</li><li><strong>Visualize how you do things</strong> : why you are doing current task, the effort you need for it and how fast you finish your tasks in the past few days. It is much better to plan if you know your pace and nature.</li></ol><p>Overseeing the goals and doing mini-project management for personal use was what I originally intended. When we get the MVP, we found that it is useful for us to make alignments remotely. So we added super simple collaborative feature. Even though we cannot use advanced functions like admin and users, this still gets the job done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AyHYgJM5BzsY33B70Hno9Q.png" /><figcaption>Sorting, collaboration, feedback and burndown chart features</figcaption></figure><p>There are additional tiny playful things like giving feedback and showing them all in the app, hiding full gmail name when searching, organize tasks in a sprint into morning, afternoon, night tasks and finally very fun Microsoft Fluent Emojis.</p><p>Now the main question — why do I make this app.</p><h3>Part 2 : Problem and Value</h3><p>The ideas started with my own problem. And I was so obsessed with agile that I tried to apply agile principles to my day to day tasks. That is how the idea was born.</p><p>My problem is that I never really finish my own goals in the expected time. But things like school lessons and work related projects got done. There can be a ton of reasons but I found out my solution in the hard way.</p><p>My goals are scrambled and they are just in my mind. So they appear, disappear and reappear. I don’t really know how close I am to the goal or if the goal was still my goal. Then, I made extensive system in notion and airtable. It doesn’t work. After a year, I finally found a solution — writing down all my goals on the whiteboard!</p><p>Another problem is that I only make goals but never visualized in detail. If a goal is to happen, it has to be vividly planned down to every detail. Big and vague goals like ‘Make an app’ will never work. One of the best way is to break it down into milestone and try to finish step by step. For this, I use post-it note to write down my milestone and stick it near the goal on the whiteboard.</p><p>I focused on one goal, one milestone at a time. But I found that my personal stuffs like helping my mom, relationship goals came in. Then I thought they are also like goals. So I include them in my whiteboard. But then I can’t just focus on one goal alone. I have to design for my app while helping my mom and planning for next travel with friends.</p><p>That’s when agile system came in. For two week, I will run a sprint. I will set a theme for the weeks — like New Year Family Gathering. I will pick up many tasks related to the theme but will still include 3–4 tasks from other goals. So in my last sprint, I focused on family time and my resolution. So I did a lot of personal tasks but I still did a few tasks related to making apps and learning Chinese.</p><p>This way I can focus on different things for short-term like two weeks but I can still track the progress of each goal on my whiteboard and post-it notes. And it is very satisfying to see the progress on each goals. Now my goals are no longer jumping around in my imaginary head. They are solid, clear and felt tangible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63J-Uw9adNjBlYpQYHR0aA.png" /><figcaption>My paper-based system and then initial proof-of-concept app</figcaption></figure><p>When I found this works for me, I turned this into an app because I can’t carry around my whtieboard all the time. And I need to access my system at all times. So we made a basic offline app. And it became my main tool to manage things. This app was like a proof of concept version of the app we finally released called Agile We.</p><p>Using that one I was able to navigate and finish all of these in just 3 months — 3 other personal apps, 2 websites, 90 days UI challenge, 30 days life style challenge, a trip with friend and about 5 video edits. And I have been talking about this to my friends and family and realized that they also have similar problem with their goals. So I got an idea to adapt this app for others. And that’s how Agile We — our first public app was started.</p><h3>Part 3 : The business of making the app</h3><p>I have tired making apps before (with friends, I don’t know how to code). But those are all personal and portfolio apps that were not meant to be released. So it was fine with just design and code. In my 4 years of product design journey, I almost neglected the other business of making an app beyond design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N5jQ8-gjXU41lwsQ3YzCtQ.png" /></figure><p>It only took about two months to do both design and coding before getting our hands on the app. We thought we were done. But we were so wrong. We had about 4 months of bumpy ride doing several different other things just to release the app.</p><h4>First 2 months — Design and development</h4><p>It is my philosophy that both of us will need to mutually understand the product concept end-to-end to get a good product. Most of the time, a UX designer finishes his work first and ‘give’ it to developers.</p><ul><li>I have done thousands of designs in past years. And I have collected a few design templates. So I started sketching directly with Mid-Fi or Hi-Fi prototypes.</li><li>Then I align with my friend to plot the userflow. This also include tech architecture. One of my crazy idea is not to have separate registration and log-in flows. I want to simplify as just use Google. To do that we had to do a lot of checks in the back. But it turned out good.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ScfYJMp3M2OtUFYP-3pnTg.png" /></figure><ul><li>Normally, I design in task flows. Like User is making an account, user is trying to do the payment. But now, I have aligned with the flows that are in the development environment in our particular case — based on features and logic.</li><li>Finally, I have created a small design system, the fonts and colors and buttons. They are all created the same inside development environment. So we are pretty much aligned in terms of design system.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RF0RnQiGEcO6lM4s4hUz6g.png" /></figure><ul><li>And we do testing and issue tracking with powerpoint. It might be surprising but it is much better for us to navigate in the slide form. Later we use this app itself to track the issues.</li></ul><h4>Last 4 months — A bunch of things we didn’t know we need to do</h4><ul><li><strong>Usability testing without proper design is bad idea</strong> : I was so happy when the app was done. So I shared with friends and family to get disappointing results. So I had to figure out how to simplify it.</li><li><strong>Problem with real-time changes</strong> : The app can share the goals and to-dos with other person. But the changes need to happen real-time. It was quite a challenging problem. But in the end, it works and it was quite an achievement for us.</li><li><strong>We need to make tutorials</strong> : I was too focused on finishing the app that I totally forgot about a good onboarding. Onboarding was done right but I still need to make tutorials on how the app is used. So I spent weeks making videos on that. And still doing to this day.</li><li><strong>Setting up playstore account</strong> : This was straignt forward. But the problem was Google just imposed a new requirement just after we created the developer account. For any app to release on playstore, developers have to do 14 days of internal testing with 20 users. It means we have to find 20 unique users just to finish this step.</li><li><strong>Go to market plan </strong>: We had zero idea how to announce this to the internet. All we have is LinkedIn accounts. We are both introverted guys whose social media accounts were barely in existence.</li><li><strong>Bug-fixes and the itch to make random tweaks :</strong> As we are spending time on these things, we came across small bugs and certain things we really want to change. If we do that, we will have to spend time designing and coding again delaying the release time. So we have to think hard on what to do and what to pass.</li><li><strong>The logo</strong> : This process take surprisingly longer than it looks. We didn’t pay attention to this and used random picture as logo for our tests until we have to upload for the release.</li><li><strong>Web App and iOS app : </strong>We use flutter for cross-platform function. But there are small things we need to take care of. We are still stuck with iOS app release. But we have finally optimized the screensizes for Web App.</li></ul><h3>Final thoughts/conclusion</h3><p>This app might not be for everyone. But it has become a major part of my daily routine. And it is pretty useful for me to figure out my goals.</p><p>You can try it on Android and Web right now from here. <a href="https://agilewe.spacematterapps.com/">https://agilewe.spacematterapps.com/</a></p><p>The journey is nothing like I expected . The main take away for me is the part where I have to own it and set the vision for it. I always thought these were just corporate jargon. And I didn’t need to think about it in my job and freelance work. But this time it became really important for me to keep the progress of the app in line with what I dreamed. I have to set a serious timeline and have to respect it and restrain myself from getting sidetracked.</p><p>I worked together with this talented developer friend. He is going to share his insights and learning on technology ( probably in his LinkedIn here &gt; <a href="https://www.linkedin.com/in/minminchit?">https://www.linkedin.com/in/minminchit?</a> )</p><p>I am also going to share more as Youtube videos here. <a href="https://youtube.com/@prestokaung?si=er3NxlfshDTlivCY">https://youtube.com/@prestokaung?</a></p><p>Thanks for watching till the end.</p><p>Presto</p><p>Hi I am going to share many of my stories about product making here in Medium. When I dreamed of making an app, I searched for these kinds of stories which I never found. I hope my sharing is helpful for you and everyone who needs it. Thanks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc8e98ead58c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We should try this for Health App Dashboards ( Redesigning Withings App )]]></title>
            <link>https://medium.com/@prestokaung.ux/we-should-try-this-for-health-app-dashboards-redesigning-withings-app-a9d3096b51f5?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9d3096b51f5</guid>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Mon, 27 Nov 2023 05:13:23 GMT</pubDate>
            <atom:updated>2023-11-27T07:17:18.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlNvT3DpnSDumY4Z2AFhQw.png" /></figure><p><em>I am redesigning this for educational purpose. I saw Withings’ announcement in CES 2023, their products look so polished that I started checking their website and found the app. I was so inspired that I want to learn how they design. That’s how I got to this fun exercise.</em></p><h4>Evaluation</h4><p>I used to judge an app screen by just how it looks. Then I might tap here and there randomly. But this really lacks strategy and direction for a good redesign. Slowly, I have built an approach that is suited for my style. I check</p><ul><li>what the contents of this screen is implying</li><li>how the app is telling you to do your tasks. I call this ‘Getting the objective’ for lack of a better word.</li><li>how does the app make you feel or what’s the identity the app assuming</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mdycYvA0unv7SaV63R9AXg.png" /><figcaption>Withings App Homescreen</figcaption></figure><p><em>Note : I made this redesign in May. Withings has already updated their UI.</em></p><p>This UI is already good, but I am going to look through my personal preference lens.</p><ol><li><strong>Where to focus</strong> — there is a lot happening. It would take quite an effort to read each card.</li><li><strong>Comparing unconsciously</strong> : this might be my pet peeves. When I see a list view like this, I was subconsciously comparing with the above card and below cards.</li><li><strong>What to do</strong> : The screen is telling us that this is an overview of my data. But it is not helping me pin point on what I should do next.</li><li><strong>Do I really need the graphs</strong> : I also felt the small graphs are not very descriptive and not very helpful to me. I want to try to replace them with simpler ones.</li></ol><h3>Grid View</h3><p>I think it will be better if I can just throw a quick glance and see everything. And maybe read one or two metrics. My idea is to have a grid view, as more contents can be packed. And make the digits distinct. And I replaced the graphs with small icons as I thought it is better than text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dILTxZptpkxql_DgjVEwpg.png" /><figcaption>List View to Grid View</figcaption></figure><p>I like the grid view better. I can see more at a glance. But it was a headache to put back all the texts — eyebrow description, the digit, short description, time last updated, the graph or icon.</p><p>So I tried various emphasis on those informations and finally settled with this sequence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MkbakzTR5Uu0-E7CKZ8hfw.png" /></figure><ul><li>If I have an illustration or graph, that will be enough to ID what it is. So the eyebrow titles are secondary in nature and they got secondary treatment — not noticeable at a glance.</li><li>Users are often familiar with the units and they can differentiate them by a quick look. No need to read. So I don’t need to make them the same size as the digits.</li><li>The icon is the main impact of look and feel. But I noticed icons lack identity. This home screen looks like Withings App home screen because of those small little graphs. And they are very well-made. I think it is wrong to use icons. So I bring back the original small graphs.</li><li>I get rid of the time indicator. It is too much for me. Instead I reference messaging apps. The latest ones have a visual identifier while already read message will have a more muted look.</li></ul><p>Now let’s take a look.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OF4CYbVmN27GphQ-07eIdg.png" /></figure><p>The grids are better, I can read the metrics easily, the other texts do not get on the way. And I can easily figure out what type of data by the iconic small graphs. And I know immediately which data are already read and which not.</p><p>But it is still lacking something.</p><h3>Highlight and enhance important points</h3><p>Changing the grid made it easier to scan (at least for my taste), but there is still one thing lacking here — what this dashboard is trying to tell me as a whole.</p><p>For this I thought like this, let’s say a gym trainer is keeping track of my metrics. When I ask him what’s new, it will be so strange if he just reads back my metrics one after another.</p><p>Rather he will say, your sleep score is good. Or why is your SPO2 low for 3 days straight!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrnU5Db6H0IOImJuh1SRmg.png" /></figure><p>That’s exactly what I did here. The dashboard will now tell me what’s happening to me. Not just abnormal findings, it will tell me very good results and great improvements too.</p><h4>Finally</h4><p>I am not very sure if the grid view is better. But I think it is easier to scan now. But the analysis highlight part is really working well for me. I cannot say the redesigned UI is better because I do not know the context of the entire app and I am doing mainly UI design exercise here.</p><p>I can say that I learned a few things from here. Especially how those small graph design that reflects Withings brand. It is quite a good concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kCFd9UuA9xyPFEKqGO0jKA.png" /></figure><h4>Lessons Learned</h4><ol><li>I was wrong about removing the small graphs. They look like not much but it is a huge part of the app’s identity. That’s where people will remember about this app.</li><li>I think it is much better for health tracking apps do the analysis for us and highlight the abnormalities. In fact, that was one of the reasons why we use them in the first place.</li><li>I love the color spectrum I get to learn here. It is very unique and works really well together.</li></ol><p>Thanks for reading till the end.</p><p>____________</p><p>👋</p><p>Hi I am Presto. I am a product designer aspiring to become an app maker. I have done from strategy to design prototyping for application projects in telco, fintech, education and healthcare.</p><p>I share my view of digital products on our daily lives as articles here at medium &amp; as videos on <a href="https://youtube.com/@prestokaung?si=jRBTlVWWXhutVZ8Q">youtube</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9d3096b51f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[90 Days of UI :  What Secrets Will You Discover? ✨]]></title>
            <link>https://medium.com/@prestokaung.ux/90-days-of-ui-what-secrets-will-you-discover-47ca39ff0ea0?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/47ca39ff0ea0</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[product-desig]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Sat, 16 Sep 2023 06:04:31 GMT</pubDate>
            <atom:updated>2023-09-16T07:45:01.332Z</atom:updated>
            <content:encoded><![CDATA[<h3>90 Days of UI : What Secrets Will You Discover? ✨🔓</h3><figure><img alt="An animation of many smartphone UI designs flowing." src="https://cdn-images-1.medium.com/max/800/1*eA1jwHLLpwhN1ja_IqM7Iw.gif" /></figure><p>TL;DR - I did a 90 day UI design challenge without losing streak. This simple practice reveals 5 great mindset for future growth on top of improved UI skills.</p><h3>Back story</h3><p>I bet you are already familiar with daily design exercises. It is very common and often overlooked. I have not even done a 10 day streak before doing this challenge. I joined <a href="https://michalmalewicz.medium.com/">Michal Malewicz</a>’s <a href="https://hype4.academy/">Squareplanet Daily UI Challenges</a>. ( Check out his video on that <a href="https://youtu.be/2WnmQiQffKw?si=ho2BkKiMvnC9d0bn">here</a>. )</p><blockquote>There is one catch. You cannot lose streaks during the 90 day challenge if you want to earn badges.</blockquote><p>I took the commitment and squeeze time to make these challenges everyday without fail. And finally finished all in this (2023) September.</p><p><em>Note: I joined the challenges during beta and was not open to public yet at that time. So I only shared with friends in the community. It is live now. You can check all my 90 designs </em><a href="https://hype4.academy/profile/3388de61-18ec-44f3-899e-73a82a3cb59b"><strong><em>here</em></strong></a><em>.</em></p><h3>Recap of the 90 days</h3><figure><img alt="Five UI design pictures I made." src="https://cdn-images-1.medium.com/max/1024/1*VWIdi-2NX40uS5jtKIRKXQ.png" /></figure><p>Everyday, I check the prompt, think what extra-challenge I can do. Draw it. Share it with others in the community and give feedback to each other. In short,</p><ul><li>I tried different styles — Neubrutalism, Skeuomorphism, Minimalism, Dark UI…</li><li>I played around with crazy ideas.</li><li>I played around with animations.</li><li>I tried new screen sizes.</li></ul><p>After completing this, the improvement in just 3 months is comparable to what I would have learned in two years. I wish I did this sooner.</p><figure><img alt="Five UI design I made. Emphasizing playful style." src="https://cdn-images-1.medium.com/max/1024/1*GaZH3JUBH4gU3BndU4exXA.png" /></figure><p>I am able to design in much more detail, use a wider array of colors, tame the fonts sizes better, explore more unique and playful styles. And I am able to get out of my comfort design.</p><p>More importantly…</p><p>There’s another big thing I realized. 👇</p><figure><img alt="A big text saying there is no secret. No is highlighted in blue." src="https://cdn-images-1.medium.com/max/772/1*kPBa_EYduD4UbhpJc1bL4w.png" /></figure><p>Yup! This is the secret itself ! I have seen this so many times and cringed on this one. And missed the point for several years !</p><ul><li>I have chased after so many great designers hoping for the secret sauce they put in their great designs.</li><li>I joined several courses, spent time hoping to find the best method.</li><li>I have constantly watched, read and followed the topic of UX design.</li><li>I thought that one day I will find this “Holy Grail” method to great product design.</li></ul><p>Actually, we tend to focus too much on someone to teach us the secret method rather than learning it ourselves. Even if there is such a thing called secret method, it won’t actually be that useful in our hands without the original person’s insights.</p><p><em>Note : It is really important to learn yourself. But this doesn’t mean we should avoid having mentors — biggest regret I have.</em></p><p>From this ‘no-secret’ secret, these mindsets unlocks. 🔓</p><h3>Break the limits</h3><figure><img alt="Time frame from 10 to 90 days with different emoji pictures." src="https://cdn-images-1.medium.com/max/1024/1*5oirvqnoMQF48MZ1zstlFA.png" /></figure><p>When I joined the challenge, I underestimated the consequences. It is not just 1–2 extra hours of design. It demands so much thinking that it really wears me out. I am usually designing this after my job. After that, I became way too exhausted.</p><p>This happened near 20–25 days. I was not sure how I would keep this up. Luckily I am doing this together with my friends in the community. And that kept me going.</p><p>After passing 60 days, it suddenly became very easy and fun to do this. I still struggle to get time to design this physically. But I am no longer fighting mentally. I am no longer afraid to do this again. It’s like I have unlocked another level of endurance.</p><h3>Confidence</h3><figure><img alt="Three pictures side by side. First picture shows apple watch design, second a smart TV and third a card dashboard UI." src="https://cdn-images-1.medium.com/max/1024/1*rZuVxDQpZ1Js1c79LUq6_Q.png" /><figcaption>A few unconventional designs (for me) from the challenge</figcaption></figure><p>No doubt, I believe a lot more in my UI and graphic capabilities after this challenge. Since the beginning of my career, I have jumped into doing research and flows for standard native mobile designs. It didn’t feel like I am good at making pretty and catchy UIs (for the lack of a better word). This was nagging me for sometime. I tried to learn and practice. But only after finishing this one, I have gained enough confidence that I can do at least average to decent looking ones, if not the best.</p><h3>Persistence</h3><figure><img alt="Two cartoon sketches side by side. Left depicts a person breaking through walls one after another. Right one depicts a person turning back upon meeting his first wall." src="https://cdn-images-1.medium.com/max/772/1*k9DaboEdIfwQMzjIPndBZw.png" /></figure><p>What if I am sick and not able to do it. What if I am traveling. What if I am too tired. These questions pop up whenever I do challenges that need to keep the streak.</p><p>Our mind is too good at tricking us with smart excuses. We avoid inconveniences even if it is very minor. Because of that, it is so easy to excuse a day. Then the next and the next until the momentum dies off and puts the challenge to an end.</p><p>In this challenge, my friends and I had finished the designs on bad days, many times. Don’t have enough time and uploaded in literal last minutes. Travelling and finding ways to complete design. Too tired, yet finished something.</p><p>What is the difference if I miss 3 out of 30 days vs a solid 30 days streak. Immense ! There is no dip in momentum if you do this straight. So the quality keeps up and continues building. And you want to test your limits and breakthrough to higher high. Once I know I can excuse a day every now and then, I will definitely take a day-off if I hit a wall.</p><p>In fact, I can say this. 27 out of 30 days will give you like 40% improvements. But 30/30 will give as much as 90%. ( just random figures to make my point.)</p><h3>Understanding yourself</h3><figure><img alt="Five UI Design I made in a style that I prefer." src="https://cdn-images-1.medium.com/max/1024/1*OFVLp3OvHuw06EXGCCVs5g.png" /></figure><p>Since the challenges are very long, I’ve got plenty of time to think about the way I design. Normally we have built up personal preferences and styles over time. This is problematic for me as I am not getting out of my own perspective bubble.</p><p>During this challenge, we are able to see how different designers approach the same prompt. And I was able to see how designs can feel totally different from tiny differences. This also reveals precise areas I am weak at and where to emphasize my learnings.</p><p>With that, I also start to develop a sense of my own style.</p><h3>Finally</h3><figure><img alt="A collage of 90 UI designs in one picture." src="https://cdn-images-1.medium.com/max/1024/1*y8AjgaHIZC9iwVe2qcUmPA.png" /></figure><p>You’ve got contents to show-off ! Take this article for example. And if someone wants to see how many different designs I can do, I have all in my pocket — Neubrutalism, Skeuomorphism, Crazy Colors, Smartwatch, Smart TV and even freaking Car Dashboards !</p><p>💡If you are also stuck like me, I would really recommend to do the challenge.</p><p>🙏That said, I did Michal Malewicz’s challenge prompts. He is one of few unique persons I look forward to. If you are interested (and I bet you already know him), check out <a href="https://hype4.academy/"><strong>his academy</strong></a><strong> </strong>and join these challenges for free. And I thank him and my friends from the community again here for the amazing journey.</p><p>You know, the best resources are <em>free</em> because it demands your commitment not your money.</p><p>👋 Hi, I am Presto Kaung. A product designer who is trying to build his own apps. Currently making a personal agile management app. Cheers !</p><p><a href="https://instagram.com/prestokaung.ux?igshid=MzMyNGUyNmU2YQ==">Instagram</a></p><p><a href="https://www.linkedin.com/in/kaunghtetkyawuiux">LinkedIn</a></p><p><a href="https://youtube.com/@prestokaung?si=17OiaHWqDkjE1kUv">Youtube</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47ca39ff0ea0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyzing various subscription models]]></title>
            <link>https://medium.com/design-bootcamp/analyzing-various-subscription-models-92b1642589d2?source=rss-102dd6eb734d------2</link>
            <guid isPermaLink="false">https://medium.com/p/92b1642589d2</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Presto Kaung]]></dc:creator>
            <pubDate>Thu, 17 Nov 2022 06:39:50 GMT</pubDate>
            <atom:updated>2022-11-19T04:43:52.738Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>TL; DR:</em></strong><em> Our mindset about subscription vs what app makers think. I present different subscription patterns and discuss which one benefits who.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEZXx5pBivgE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEZXx5pBivgE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEZXx5pBivgE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e78a93816a2ea8704b7f164420ccdfac/href">https://medium.com/media/e78a93816a2ea8704b7f164420ccdfac/href</a></iframe><h3>Is subscription ok for us?</h3><figure><img alt="Emoji image of haircut, grocery bag and payment receipt." src="https://cdn-images-1.medium.com/max/1020/1*eqLzt9W0IBv-L9AFvHrT4g.png" /></figure><p>Subscription is already around us. Haircut, groceries, bills — all are recurring payments. But we don’t feel these are not worth subscription. Because transactions happen before our own eyes making us feel we are in control. Plus, we have already accepted it is natural to pay again and again for those.</p><figure><img alt="Emoji image of hammer, toilet, and table clock with subscription amount." src="https://cdn-images-1.medium.com/max/1024/1*mJ6n1fRTaee9ocZIjfyTeQ.png" /></figure><p>Subscription for these things sounds ridiculous, right? Nowadays, applications are starting to replace most of our day-to-day tools. E.g. We used to make music by playing — today, making music on a computer is more common. With that relation between tools, we felt that these apps should stay with one-time payment model.</p><h3>What if we are app makers</h3><figure><img alt="Image comparing how much time it takes to make back the building cost from fixed-amount charging and subscription." src="https://cdn-images-1.medium.com/max/1024/1*XLHInXOPdRxjETKS0cHWJw.png" /></figure><p>I have thought of starting an app. Subscription is a very lucrative model. In the old days of one-time purchase model, I, as a company, would only make a fixed amount from a user. For $20 app which costs 2M to build, we need 100,000 customers to make it back let alone thinking about profits.</p><p>With subscription of $5/m (cost of a soft drink per month), we would only need around 35,000 customers using our app for just a year. There are some difficulties, but still much easier than the classic model. It is no wonder, every business turns towards subscription.</p><p>I have listed here a bunch of subscription patterns I have seen so far.</p><h4>1. Not flexible and flexible</h4><figure><img alt="Two images comparing inflexible pattern and flexible pattern." src="https://cdn-images-1.medium.com/max/1024/1*8ivtWCorYxGrCx3SIknbcg.png" /></figure><p>Both models are quite common. But forcing yearly commitment by making a wide gap between yearly and monthly payments will hurt the reputation even if the product is giving really good value. It is true as a business that I will also want customers to commit longer. But this way will not earn loyalty.</p><h4>2. Overcharged</h4><figure><img alt="Two columns comparing pricy subscription model vs token and count-based model." src="https://cdn-images-1.medium.com/max/1024/1*pw6JzIx8HylyqFZ1RtolSg.png" /></figure><p>To be clear, it is overcharged from the perspective of the customer. Business might have reasons. But most of the time, it is obvious when the price is too high for what it is doing. It will be a shame if it is a good service since few customers will get exposure. In this case, token feature makes sense (one token to do one task). If you are simply curious, you can buy a few tokens for a cheap price and use them without time limitation. Even monthly task limits based on frequency of use is a much better approach.</p><h4>3.Remove Ads</h4><figure><img alt="Two mobile screens comparing Ad-removal subscription vs one-time ad removal per feature." src="https://cdn-images-1.medium.com/max/848/1*HxNS1HGJrVmVre8EeP-naA.png" /></figure><p>This is quite common. And it is a good model because business can provide free chance to customers while making money out of Ads. But the problem comes when the service asks a steep subscription fee for only Ads removal — no promise of feature update or maintenance update. If I am an app owner, I will go for one-time fees of Ad removal for a feature, or a service as shown in picture. That way I can make multiple income while giving the customer flexibility.</p><h4>4.Tools with subscription</h4><figure><img alt="Using Hammer as example, two columns comparing subscription vs flat fees and upgrade plan model." src="https://cdn-images-1.medium.com/max/1024/1*o2J3WU9tZ37qDr61aAGvlA.png" /></figure><p>This is the problem I stated at the start. We don’t want to pay for tools that should last very long. Normally digital audio workstations, movie editors, page editors and graphic editors are in this category. We are now witnessing these apps’ transition to subscription models, and they are the priciest of them all. These are heavy desktop apps that went through pricy and lengthy development processes.</p><p>Unlike mobile apps or SaaS products, the upgrades from these apps really matter and usually that is the selling point for v2, v3 etc. With that said, I find an interesting transition to subscription model. There is this upgrade plan where you get all updates that are released more frequently in a year. Customers enjoy useful feature updates much earlier while a subscription works. And it is the user’s choice if they don’t need upgrades and keep owning older versions without paying any subscription.</p><h4>5.Baits</h4><figure><img alt="Two images comparing basic tier of an app being too limiting vs being reasonable." src="https://cdn-images-1.medium.com/max/694/1*iQkxWYk1RTF1akU0yvq9gQ.png" /></figure><p>This is fine until the gap between basic and pro (or any name) is too big. Some basic tiers are more limiting than alternative free ones. This is commonly seen in new products wanting to monetize too soon. But it is also problematic if the basic tier becomes too good and pro tier gets less interests.</p><h3>Is this the best app for its value?</h3><figure><img alt="Image of Black Magic Davinci Resolve software, free version and paid version." src="https://cdn-images-1.medium.com/max/1024/1*DmkKpu4QsSS6C24ire511Q.png" /></figure><p>Finally, I really like how Davinci Resolve (Pro Video Editing Software), cut the free and pro line. There are specific features where normal users never need but a must-have for pros. Davinci Resolve only cuts those points. For example, normal users will not need AI background detection.</p><p>😄Thank you for reading till the end. I have made a ‘fun’ YouTube video (5min) on this article. Feel free to check it out.</p><p>Presto Kaung</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92b1642589d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/analyzing-various-subscription-models-92b1642589d2">Analyzing various subscription models</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>