<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Flowmo</title>
    <description>The latest articles on Forem by Flowmo (@flowmo).</description>
    <link>https://forem.com/flowmo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F8048%2F3656531e-1695-4574-b071-3a390ddabf46.png</url>
      <title>Forem: Flowmo</title>
      <link>https://forem.com/flowmo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/flowmo"/>
    <language>en</language>
    <item>
      <title>Half year reflections on building my first SaaS</title>
      <dc:creator>Max Shen</dc:creator>
      <pubDate>Sat, 27 Jul 2024 12:04:55 +0000</pubDate>
      <link>https://forem.com/flowmo/half-year-reflections-on-building-my-first-saas-3ci5</link>
      <guid>https://forem.com/flowmo/half-year-reflections-on-building-my-first-saas-3ci5</guid>
      <description>&lt;p&gt;It's been around a half year since I started building &lt;a href="https://flowmo.io/blog/my-dream-productivity-app?utm_source=devto" rel="noopener noreferrer"&gt;my dream productivity app&lt;/a&gt;, Flowmodor. I think it's a good time to reflect on the journey and share some insights.&lt;/p&gt;

&lt;p&gt;Start with some interesting stats:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;MRR: $52 (from 11 paying users)&lt;/li&gt;
&lt;li&gt;Total registered users: 3700&lt;/li&gt;
&lt;li&gt;Average monthly active users: 300&lt;/li&gt;
&lt;li&gt;Average monthly landing page visitors: 1000&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The overall trend is a slow but steady growth. Here are some reflections on the journey so far.&lt;/p&gt;

&lt;h2&gt;
  
  
  SEO and traffic
&lt;/h2&gt;

&lt;p&gt;On average, I get 90 new registered users per week, most of them come from organic search:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxj1z9bomw41zq1s8nq7s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fxj1z9bomw41zq1s8nq7s.png" alt="traffic top sources chart" width="800" height="668"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I think that's because I have been refining the landing page SEO for &lt;code&gt;flowmodoro&lt;/code&gt; keyword. It's not a popular term yet so I successfully ranked the top for it.&lt;/p&gt;

&lt;p&gt;This is actually a good strategy for a new product. Instead of targeting popular keywords, choosing a niche keyword can help you rank faster and get more targeted users.&lt;/p&gt;

&lt;p&gt;In addition to the landing page, I also wrote some blog posts about the Flowtime Technique and Pomodoro Technique. However, the ranking of these posts are not that good. Therefore didn't bring much traffic:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fd0ishzgvynsrnc3944sf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fd0ishzgvynsrnc3944sf.png" alt="entry pages chart" width="800" height="626"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Paying users
&lt;/h2&gt;

&lt;p&gt;I switched from PayPal to Paddle for payment processing. It's a good decision because I can now accept more payment methods and the checkout process is smoother (same for DX). It also provides a better dashboard to track the revenue and users.&lt;/p&gt;

&lt;p&gt;Among the 11 paying users, 3 of them are on the yearly plan, which is actually suggested by one of the users. I didn't expect that people would pay for a yearly plan, but it turns out that some users prefer it.&lt;/p&gt;

&lt;p&gt;I also added a 14-day free trial for every new registered user. Letting users try the full features for free is a good way to convert them into paying users.&lt;/p&gt;

&lt;h2&gt;
  
  
  Product development
&lt;/h2&gt;

&lt;p&gt;Although I care about the traffic and revenue, I think the most important thing is still the product itself. It's the real value that I'm providing to users.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://flowmo.io/blog/my-dream-productivity-app#the-plan?utm_source=devto" rel="noopener noreferrer"&gt;3 MVP features&lt;/a&gt; are all implemented and even more polished. For example the task list now supports Todoist integration, and the focus report now has a yearly heatmap view.&lt;/p&gt;

&lt;p&gt;The completion of the MVP features also means that I'll soon have a public launch. I'm planning to launch it on Product Hunt next week. I hope it can bring more exposure and users. You can &lt;a href="https://www.producthunt.com/products/flowmodor" rel="noopener noreferrer"&gt;sign up here&lt;/a&gt; to get notified when it's live!&lt;/p&gt;

&lt;p&gt;Another important thing is that I've built a &lt;a href="https://app.flowmo.io/feedback" rel="noopener noreferrer"&gt;feedback board&lt;/a&gt; for users to submit feature requests and vote for them:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjyo1cf9g0w3bta23h4i8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fjyo1cf9g0w3bta23h4i8.png" alt="feedback board" width="800" height="542"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It's a great way to understand what users really need and prioritize the development. I've already implemented 3 features from the board and I'll start working on the most voted feature: a mobile app, after the public launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Building Flowmodor is a challenging but enjoyable journey. This is my first time building a SaaS product and I've learned a lot from it. I'm grateful for all the Flowmodor users providing feedback and support. I'll keep improving the app and looking forward to the &lt;a href="https://www.producthunt.com/products/flowmodor" rel="noopener noreferrer"&gt;PH launch&lt;/a&gt; next week 💜&lt;/p&gt;



</description>
      <category>saas</category>
      <category>startup</category>
      <category>buildinpublic</category>
      <category>webdev</category>
    </item>
    <item>
      <title>5 things to do during Pomodoro break without electronic devices</title>
      <dc:creator>Max Shen</dc:creator>
      <pubDate>Sun, 28 Jan 2024 13:04:08 +0000</pubDate>
      <link>https://forem.com/flowmo/5-things-to-do-during-pomodoro-break-without-electronic-devices-303i</link>
      <guid>https://forem.com/flowmo/5-things-to-do-during-pomodoro-break-without-electronic-devices-303i</guid>
      <description>&lt;p&gt;When practicing productivity techniques like the Pomodoro or &lt;a href="https://flowmo.io/blog/flowtime-technique?utm_source=devto" rel="noopener noreferrer"&gt;Flowmodoro&lt;/a&gt; methods, it's easy to dismiss the importance of breaks.&lt;/p&gt;

&lt;p&gt;During these breaks, it's tempting to immediately reach for your phone and spend the entire time scrolling, rationalizing it as a reward for your prior concentration.&lt;/p&gt;

&lt;p&gt;However, this habit not only makes it challenging to regain focus for the next session but also denies your eyes the rest they need. Therefore, I'll introduce five activities you can engage in during your breaks, all without the use of electronic devices.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Stretch your body 🤸
&lt;/h2&gt;

&lt;p&gt;Stretching during breaks is not just a way to relieve physical tension but also to clear your mind. The nature of programming often demands extended durations of seated concentration, which can lead to physical rigidity. Simple stretching exercises can relieve muscle tension and also provide a mental reset, preparing you for the next phase of intense focus.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Go for a walk 🚶
&lt;/h2&gt;

&lt;p&gt;A short walk is an excellent way to disconnect from your work. It's not just about the physical movement but also about changing your environment. Walking away from your workspace allows you to return with a fresh perspective. Whether it's a stroll around your office, a quick venture into your backyard, or just pacing in your room, the act of walking helps in resetting your mind, making you more creative and productive when you return.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Look off into the distance 🔭
&lt;/h2&gt;

&lt;p&gt;Taking a quick break to look away from your computer screen is simple but really helpful. When you've been staring at code for a while, it's good to give your eyes a rest. Try to find a spot where you can look out a window. Focus on something far away like the sky, trees, or distant buildings. This isn't just about resting your eyes; it's also a quiet moment for your mind. As you look away, take a few deep breaths. This easy break can help you feel more relaxed.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Organize your work desk 🧹
&lt;/h2&gt;

&lt;p&gt;A cluttered desk can lead to a cluttered mind. Use your break to organize your workspace. Put away unnecessary items, arrange your documents, and clear any trash. A clean and organized environment can significantly boost your productivity and reduce stress levels.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Fill your water bottle &amp;amp; visit the restroom 💧
&lt;/h2&gt;

&lt;p&gt;Hydration is key to maintaining high energy levels and focus. Use your break to refill your water bottle. It's a simple act, but it ensures that you stay hydrated, especially important if you're so engrossed in your work that you forget to drink water. Additionally, a regular visit to the restroom is also important.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;In short, taking breaks is key to doing well at work or study. Using breaks wisely, by doing things like stretching, walking, looking into the distance, tidying up your desk, or getting water, isn't just a rest from work. It's a way to make sure you come back to your tasks with more focus and energy. &lt;/p&gt;

&lt;p&gt;These simple actions during breaks can help you feel better and work better. So, remember to step back, take a good break, and see the difference it makes in your day!&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>career</category>
      <category>learning</category>
      <category>pomodoro</category>
    </item>
    <item>
      <title>Why pomodoro doesn't work? Try this alternative 🍅</title>
      <dc:creator>Max Shen</dc:creator>
      <pubDate>Sun, 14 Jan 2024 12:00:57 +0000</pubDate>
      <link>https://forem.com/flowmo/why-pomodoro-doesnt-work-try-this-alternative-2no9</link>
      <guid>https://forem.com/flowmo/why-pomodoro-doesnt-work-try-this-alternative-2no9</guid>
      <description>&lt;h2&gt;
  
  
  What's Pomodoro
&lt;/h2&gt;

&lt;p&gt;The Pomodoro Technique, developed by Francesco Cirillo, is a time management method that uses a timer to break work into intervals, traditionally 25 minutes in length, separated by 5-minutes short breaks.&lt;/p&gt;

&lt;p&gt;These intervals are known as "pomodoros", named after the tomato-shaped kitchen timer that Cirillo used as a university student.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Pomodoro might not work for developers
&lt;/h2&gt;

&lt;p&gt;While the Pomodoro Technique is popular, it might not be the best fit for everyone, especially developers. Here’s why:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Interruption of Flow State&lt;/strong&gt;: The rigid timing can disrupt the deep "flow state" crucial for coding. When you're deeply engrossed in a complex problem, stopping because a timer goes off can break your train of thought.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Variable Task Length&lt;/strong&gt;: Coding tasks vary in complexity and often don't neatly fit into 25-minute intervals. Some tasks might require prolonged uninterrupted focus, while others are shorter and more straightforward.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Context Switching&lt;/strong&gt;: Frequent breaks mandated by the Pomodoro Technique can lead to excessive context switching. This is counterproductive for tasks that require sustained concentration and a deep understanding of the problem at hand.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The better alternative - Flowmodoro
&lt;/h2&gt;

&lt;p&gt;The Flowtime Technique a.k.a. Flowmodoro was created by &lt;a href="https://medium.com/@UrgentPigeon/the-flowtime-technique-7685101bd191" rel="noopener noreferrer"&gt;Zoë Read-Bivens&lt;/a&gt; as a solution to Pomodoro's main problem.&lt;/p&gt;

&lt;p&gt;Unlike the Pomodoro Technique, Flowmodoro counts up instead of counting down. It allows you to focus until you naturally feel the need for a break. Then, when you decide to rest, you simply stop the timer, divide the focus time by 5, and set a countdown timer for your break.&lt;/p&gt;

&lt;p&gt;This method respects your flow state and adapts to the variable nature of coding tasks.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to implement Flowmodoro
&lt;/h2&gt;

&lt;p&gt;Implementing Flowmodoro is simple and can start with tools as basic as a stopwatch and timer app. Here's a basic guide:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Pick One Task&lt;/strong&gt;: Begin by selecting a single task to focus on. This ensures that your attention isn't divided across multiple tasks.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Start the work&lt;/strong&gt;: Once your task is chosen, start the stopwatch. This marks the beginning of your focused work period. Dive into your task without any distractions.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Stop the work&lt;/strong&gt;: Keep working until you naturally feel the need for a break. This could be when you feel your concentration waning or you've reached a logical stopping point in your task. Then, stop the stopwatch. This time recorded is your focused work duration.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Take a break&lt;/strong&gt;: Calculate your break time as one-fifth of your focused work duration. For instance, if you worked for 50 minutes, take a 10-minute break. Set a countdown timer for this break period. This ratio ensures that you get adequate rest without losing the momentum of your work.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can repeat this cycle again and again. &lt;/p&gt;

&lt;h2&gt;
  
  
  Automate the process
&lt;/h2&gt;

&lt;p&gt;I have been using Flowmodoro and it really help me improve my productivity while coding. However, I noticed one minor drawback: the repetitive process of setting up the timer manually each time.&lt;/p&gt;

&lt;p&gt;To address this, I'm currently working on a solution that seamlessly integrates with this workflow. That's where &lt;a href="https://flowmo.io?utm_source=devto" rel="noopener noreferrer"&gt;Flowmo&lt;/a&gt; comes in – a web app I am creating to automate and refine the Flowmodoro process.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://app.flowmo.io" class="ltag_cta ltag_cta--branded" rel="noopener noreferrer"&gt;Get Started&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;As developers, our work requires flexibility and adaptation. Flowmodoro is designed with this in mind. Let's embrace our peak flow states with Flowmodoro!&lt;/p&gt;



</description>
      <category>productivity</category>
      <category>pomodoro</category>
      <category>career</category>
      <category>flowmodoro</category>
    </item>
  </channel>
</rss>
