SaaS founder · @kylereddoch

Kyle

Founder background

Solo founder building independent apps through RelayByte. I’m the maker of Trayage, StylePort, and Drift, with more ideas taking shape. I build tools that solve everyday problems, respect people’s privacy, and give them control. Here, I share what I’m working on, why I’m building it, and what I learn along the way—from early ideas and design decisions to launches and the work that follows. Building apps. Sharing the process.

Expertise

  • Engineering

Public profiles

X

Personal site

LinkedIn

Instagram

TikTok

Products

Hinge Habits

Track your iPhone Duo folds with free, customizable Home Screen widgets.

Drift

A good find. A new conversation.

Trayage

A little order for your Downloads

Recent posts

A Practical Way for Solo Developers to Say Not Yet to Features

Building my own apps has taught me that not every good feature idea needs to happen right now. Sometimes saying "not yet" is the best decision you can make for your product. That's what inspired my latest article. Curious how other indie builders handle feature requests. 👇

StylePort is now on the Mac App Store 🎉

I built StylePort because I wanted my favorite website styles to feel at home in Safari. It lets you import CSS and UserCSS themes, customize their available options, and manage your styles in one place—with backup and restore built in. Your style library stays stored locally. Getting from “this should work” to a shipping Safari extension involved plenty of testing, interface refinements, and learning Apple’s release process. I’m excited to finally share 1.0. If you use Safari and enjoy making the web your own, I’d love for you to try it. What’s the first website you’d restyle? https://styleport.app

Your Release Notes Are Part of the Product Experience

“Bug fixes and improvements” doesn’t give users much to go on. I wrote about making release notes useful: what changed, who it affects, and what to do next. What do you wish more developers included in their release notes?

Better Bug Reports for Indie Apps: A Reproduction Checklist

A better bug report can start with one simple question: “What happened just before things went wrong?” When you’re building and supporting an app yourself, a little context can save a lot of back-and-forth. I put together a practical guide with five questions you can adapt for your own bug-report form, plus a few thoughts on protecting user privacy and following up when something gets fixed. What’s one question that’s helped you get more useful bug reports? I’d like to hear what’s worked for other indie developers.

Five Questions Your App Should Answer Before Anyone Has to Ask

When you're building an app, it's easy to get caught up in features, design, and getting the next update out. But sometimes we forget what it's like to discover that app for the very first time. Does someone understand what problem it solves? What happens when they open it? What happens to their data? What if they make a mistake? And what will it cost? I've been thinking about these questions while building my own apps. I think answering them clearly can be just as important as the features themselves. I wrote about five questions every developer should consider before expecting someone to try their software. Sometimes the next improvement isn't another feature. It's doing a better job explaining what you've already built. I'd love to hear how other builders approach this.

I won a Buildside shirt! 🎉

Unfortunately, it’s definitely NOT my size. 💀😂 The shirt fits… but it’s one deep breath away from a security breach. @Buildside and @urielbitton , y’all got an enterprise edition? 🤣use

Why I Built Trayage Around Review First, Cleanup Second

Coming from IT and cybersecurity, I’ve seen how much trust an app asks for when it can change or remove someone’s data. That shaped Trayage: show why a file is worth checking, then let the person decide what happens next. I wrote about that choice, the tradeoffs behind it, and what I learned building my first Mac app.

Explore more SaaS founders building in public