<?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>DEV Community: Sev</title>
    <description>The latest articles on DEV Community by Sev (@sevleo).</description>
    <link>https://dev.to/sevleo</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%2Fuser%2Fprofile_image%2F1546342%2F34f09344-e2cf-4450-a7bd-96413336fd68.jpeg</url>
      <title>DEV Community: Sev</title>
      <link>https://dev.to/sevleo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sevleo"/>
    <language>en</language>
    <item>
      <title>I Quit My Job to Build an Open Source Social Media Scheduler</title>
      <dc:creator>Sev</dc:creator>
      <pubDate>Sat, 08 Mar 2025 17:36:58 +0000</pubDate>
      <link>https://dev.to/sevleo/i-quit-my-job-to-build-an-open-source-social-media-scheduler-3dkp</link>
      <guid>https://dev.to/sevleo/i-quit-my-job-to-build-an-open-source-social-media-scheduler-3dkp</guid>
      <description>&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%2Fk524c7ve23kbcer7tdh8.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%2Fk524c7ve23kbcer7tdh8.png" alt="Image description" width="800" height="345"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hi everyone!&lt;/p&gt;

&lt;p&gt;I’ve been working on an &lt;strong&gt;open-source social media scheduler&lt;/strong&gt; for the past 110 days, and I’d love to share it with you.&lt;/p&gt;

&lt;p&gt;For the first two months, I juggled this project alongside my 5-9 job. But then I realized I wanted to go all-in, so I saved up, quit my job, and committed to building something better.&lt;/p&gt;

&lt;p&gt;There are plenty of schedulers out there, including another open-source one (Postiz). But after trying different options such as Metricool, Buffer, Post-Bridge, Qayle, and others, I kept running into the same problems.&lt;/p&gt;

&lt;p&gt;The main problem with the existing tools is that their UI sucks.&lt;/p&gt;

&lt;p&gt;Okay, to not be so harsh, their UI has a lot of things that can be improved. The main issues are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Clunky UI: slow, cluttered, and filled with unnecessary features.&lt;/li&gt;
&lt;li&gt;Too many clicks.&lt;/li&gt;
&lt;li&gt;Poor UX choices - pop ups, distractions, and bloat that et in the way of content creation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wanted a minimalist yet powerful tool, something that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;has a &lt;strong&gt;clean&lt;/strong&gt;, &lt;strong&gt;fast&lt;/strong&gt;, and &lt;strong&gt;intuitive&lt;/strong&gt; UI&lt;/li&gt;
&lt;li&gt;focuses on &lt;strong&gt;essential&lt;/strong&gt; features&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;encourages&lt;/strong&gt; content creation, not just scheduling (this is important)&lt;/li&gt;
&lt;li&gt;loads &lt;strong&gt;quickly&lt;/strong&gt; and works &lt;strong&gt;smoothly&lt;/strong&gt;, so you don't have to slow down your &lt;strong&gt;thinking&lt;/strong&gt; having to wait when another pop up loads or when the save button finally finishes saving&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The closest tool to my vision is Typefully, but it’s expensive, mainly focused on text, and still has room for UX improvements (selecting platforms for a post is unnecessarily complicated process). My tool is heavily inspired by Typefully but aims to refine the experience even further.&lt;/p&gt;

&lt;p&gt;Unlike other schedulers that overwhelm users with branding and unnecessary visuals, I see this as a productivity tool, similar to Excel. It should just work, with as little friction as possible.&lt;/p&gt;

&lt;p&gt;One of my biggest frustrations was switching between note-taking apps (like Obsidian) and my scheduler. I wanted a space where I could brainstorm, draft, and refine content, where I can see my past content and future content and I can relate them to one another. That’s another key problem this tool is solving.&lt;/p&gt;

&lt;p&gt;I still use Obsidian to write and take notes, but I don't use it to create specific platform content/posts anymore. I've. designed my tool to be the hub for that. Obsidian for me is more of a general purpose not taking app. I usually open it alongside my app and create the platform-specific content directly in the app.&lt;/p&gt;

&lt;p&gt;That being said, the tool is currently in beta and free to use. I'm looking for early users who can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;try it out and see if it fits your workflow&lt;/li&gt;
&lt;li&gt;share feedback and help me shape the future of the app&lt;/li&gt;
&lt;li&gt;report bugs and suggest improvements.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I plan to keep it free for a few more months before finalizing a monetization strategy.&lt;/p&gt;

&lt;p&gt;If you're interested, feel free to sign up and use it. You can also self-host or contribute to the open-source project (though proper documentation is still a work in progress).&lt;/p&gt;

&lt;p&gt;Thank you for taking the time to read! 🚀&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;app: &lt;a href="https://publora.com/" rel="noopener noreferrer"&gt;https://publora.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;github: &lt;a href="https://github.com/sevleo/BrandCraft" rel="noopener noreferrer"&gt;https://github.com/sevleo/BrandCraft&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I would love to hear your thoughts and feedback. Please let me know what you think!&lt;/p&gt;

&lt;p&gt;P.S. If interested, join the discord group! The link to discord is on the landing page of the app.&lt;/p&gt;

&lt;p&gt;Cheers,&lt;/p&gt;

&lt;p&gt;Sev&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>socialmedia</category>
      <category>scheduler</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>Should I Open Source My Project If a Better Alternative Exists?</title>
      <dc:creator>Sev</dc:creator>
      <pubDate>Sun, 16 Feb 2025 08:13:18 +0000</pubDate>
      <link>https://dev.to/sevleo/should-i-open-source-my-project-if-a-better-alternative-exists-fb0</link>
      <guid>https://dev.to/sevleo/should-i-open-source-my-project-if-a-better-alternative-exists-fb0</guid>
      <description>&lt;p&gt;Hey everyone! This is my first post in the Dev community, and I’d love to hear your thoughts on something I’ve been debating.&lt;/p&gt;

&lt;p&gt;For the past three months, I’ve been building my own &lt;strong&gt;social media scheduler&lt;/strong&gt;, and recently, I started considering making it open source. My thinking was that the code itself isn’t that valuable to keep private, and open-sourcing would allow developers who don’t want to pay for a tool like this to self-host it instead.&lt;/p&gt;

&lt;p&gt;But here’s the dilemma:&lt;br&gt;
I just discovered Postiz—an open-source project that does exactly what my tool does, but better. It’s already well-developed, has extensive documentation, and was built by a more experienced developer using NestJS and a more modularized architecture.&lt;/p&gt;

&lt;p&gt;So now I’m wondering:&lt;br&gt;
Does it still make sense for me to go open source? Would anyone actually want to contribute or use my project when there’s already a superior alternative?&lt;/p&gt;

&lt;p&gt;That said, I still want to keep working on my project because:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I believe in my own vision and like having control over the app I use.&lt;/li&gt;
&lt;li&gt;My project is more beginner-friendly since I built it with a simpler stack. Backend: Pure Node.js/JavaScript (no NestJS). Frontend: Vue.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because of this, I think it has a lower learning curve and is easier to customize.&lt;/p&gt;

&lt;p&gt;So, what do you think?&lt;br&gt;
Would open-sourcing still make sense in this case? Or should I take a different approach?&lt;/p&gt;

&lt;p&gt;Would love to hear your thoughts!&lt;/p&gt;

</description>
      <category>opensource</category>
    </item>
  </channel>
</rss>
