iiinova — where your digital self keeps evolving

You know those moments when you know something could go very wrong, but there’s nothing you can do about it anymore? I’m in one of those right now, and it’s freaking me out. How do you stay calm and stop your brain from running in circles? #thoughts #life

000

Luca @lxca.de · 11/10/2026

Consistency and actually finishing things is hard, especially when you’re only half convinced by an idea. That’s why everything I build is somehow related to a problem I have myself. My approach is to ship an MVP quickly, then decide if it’s still worth investing more time into it.

010

Luca @lxca.de · 11/10/2026

I spent most of today ideating on a new project idea. I think ideation is becoming my favorite part of building. It challenges my brain, gives me room to be creative, and turns vague ideas into clear next steps. What part of building do you enjoy most? #buildinpublic #SaaS

340

Luca @lxca.de · 10/10/2026

One thing I struggle with in analytics: every change needs days or weeks before the data is actually useful. That makes it hard to know whether to wait for proof or keep building and validate later. How do you handle this? #buildinpublic #SaaS #analytics

130

Luca @lxca.de · 10/10/2026

Oh yes, I already have a few ideas for improving the onboarding. I probably wouldn’t have prioritized them without looking at the stats first. Seeing where users actually struggle made it much clearer what I should improve next.

100

Luca @lxca.de · 09/10/2026

I’m starting to realize how little I actually know about analytics. Today I dug deeper into Umami, improved my setup, and added new stats step by step. It’s surprisingly fun learning a topic that was mostly a black box to me before. #buildinpublic #SaaS #analytics

370

Luca @lxca.de · 09/10/2026

So it’s less about squeezing maximum productivity out of every hour. I just have way more things I’d love to build than time to build them, because I enjoy the process and often have ideas that would be useful to me. That’s why I tend to optimize the time I have.

010

Luca @lxca.de · 09/10/2026

Fair point 😄 But for me, building things is actually part of “life”, not just work. I regularly spend time with friends and family, go to the gym, etc. But when I have free time, I genuinely enjoy working on my projects and experimenting with ideas.

110

Luca @lxca.de · 09/10/2026

Yeah, I think that’s a good mindset at some point. But for me, having x more hours doesn’t automatically mean moving my projects x times faster. I probably just need to be a bit more relaxed about paying for tools, without going too far in the other direction.

110

Luca @lxca.de · 09/10/2026

If I really want to build a good tool, it needs time. But those are usually projects I plan to publish. Some tools are just for myself, so I vibe-code them, use them as they are, and fix things over time. I probably just need to accept that “good enough” is sometimes enough.

010

Luca @lxca.de · 08/10/2026

Am I the only one who struggles to pay for small but useful tools? I often see one, like it, check the price and think: “Nah, I can build this myself.” Sometimes I wonder if that mindset is actually holding me back. Do you try tools first and cancel if they’re not worth it? #buildinpublic #SaaS

240

Luca @lxca.de · 08/10/2026

Absolute banger of a song and video 😂

110

Luca @lxca.de · 07/10/2026

I got tired of writing texts, copying them into ChatGPT for corrections, and pasting them back. So I built a small tool that does it directly in the input field. Fully vibe-coded, definitely not perfect yet, but it works. #buildinpublic #AI #vibecoding

120

Luca @lxca.de · 07/10/2026

I’d like to give it a try! But it looks like your repository is private, so I can’t access it right now.

110

Luca @lxca.de · 07/10/2026

I’m not using screenshots because I don’t think they would look that good. Instead, I create small UI graphics that recreate the interface in a simpler way and support the text better.

000

Luca @lxca.de · 06/10/2026

A few days ago I rebuilt the Todolytics landing page. Now I’m creating detail pages for its use cases. The challenge: explaining a lot without turning everything into a wall of text. Choosing what to show and what to visualize is harder than expected. #buildinpublic #SaaS

361

Luca @lxca.de · 06/10/2026

Definitely building and watching 😄 Probably not the most efficient approach, but somehow it works

000

Luca @lxca.de · 06/10/2026

Using a UI library definitely makes individual components easier. But when I build full interfaces with AI, they often still don’t feel very polished. The annoying part is that I can’t always explain what’s wrong. I often just end up saying “this looks bad, try something different” 😄

000

Luca @lxca.de · 06/10/2026

That’s crazy 😄 For me, it’s just one right now. I stopped working on that project a while ago, but the domain still has some time left on it, so I’m just letting it run until it expires.

000

Luca @lxca.de · 06/10/2026

That’s a nice strategy too. I usually just have a list of tasks I want to get done that week, and whenever I start working, I pick one from the list. Sometimes something unplanned comes up and feels more important, so I just work on that instead.

000

Luca @lxca.de · 06/10/2026

That leaves me with two options: teach those users how to build the habit, or focus more on people who already know what they want to do and just need a better tool to support them. I’m still figuring out which direction makes more sense.

000

Luca @lxca.de · 06/10/2026

Yeah, that’s something I’ve noticed recently too. From the feedback I got, many of my current users want to do what my product helps with, but they weren’t really doing it before. So I’m not just solving a tooling problem, but partly a habit problem too.

100

Luca @lxca.de · 06/10/2026

I really like this UI. Did you build it yourself, or are you using a UI library like shadcn/ui?

430

Luca @lxca.de · 06/10/2026

Just checked my subscription sheet (yes, I have one 😄), and I’m at 3 to 5 SaaS subscriptions, depending on how strictly you define SaaS

110

Luca @lxca.de · 06/10/2026

Back then, I also had way too many graveyard domains. I’ve learned to only register one when I’m pretty sure I’ll actually need it in the near future. Since then, I’ve bought a lot fewer domains 😆

110

Luca @lxca.de · 05/10/2026

Today I worked on my ChatGPT growth plan. Tech parts went as planned. For the creative side, I chose a different approach that should be more useful to users while keeping the SEO/GEO benefits. One more step toward making 200 Todolytics users by year-end realistic. #buildinpublic #SaaS

260

Luca @lxca.de · 05/10/2026

I’m also working on multiple features in parallel now, but I need to keep a closer eye on quality. That means improving the structure around the work and writing clearer, more detailed tasks so the agents know exactly what to do without too much back-and-forth.

010

Luca @lxca.de · 05/10/2026

I also want to experiment with stricter time limits. There’s this idea that work expands to fill the time available. I think I’m sometimes less efficient simply because I give tasks too much room. So I want to timebox more and see if tighter limits help me focus.

010

Luca @lxca.de · 05/10/2026

Some days I spend almost the entire day on development, and I’m starting to dislike how repetitive that feels. So I’m changing how I plan my time: maybe 4h on development, 2h on planning new features, 1h on ideation, etc. Same work, just with more variety.

200

Luca @lxca.de · 04/10/2026

Working on my projects with AI has started to feel a bit repetitive. The workflow is often the same, and it doesn’t challenge me that much. So I’m planning my weeks with more variety instead of pure development. Let’s see if that makes me more productive. #buildinpublic #SaaS #AI

240

Luca @lxca.de · 04/10/2026

Sometimes, yes. But most new connections actually come through people I already know. For example, someone introduces or mentions another person, or we just get to know each other through a group chat. So a lot of my network grows naturally from existing connections.

010

Luca @lxca.de · 04/10/2026

Discord is a bit different for me. That’s where I have much deeper connections with people who work in similar areas and share the same interests. It feels less like networking and more like having a group of people I can actually reach out to anytime.

110

Luca @lxca.de · 04/10/2026

I use different platforms for different purposes. Bluesky is mostly for making new connections, both within and outside my usual areas. I also use it for inspiration and to see how others approach things. LinkedIn is more for reconnecting with colleagues and people I’ve worked with.

110

Luca @lxca.de · 03/10/2026

I’ve started networking more over the past few weeks. It’s harder than I expected, but also simpler: it mostly takes time and consistency. The best part is hearing how others think. It regularly gives me ideas and perspectives I probably wouldn’t have had on my own. #buildinpublic #SaaS

160

Luca @lxca.de · 03/10/2026

Pretty much where I’m heading too. When I open a PR, I usually skim through all the changes instead of reviewing every detail deeply. But APIs, database changes, auth, and similar critical areas are things I still keep a much closer eye on.

000

Luca @lxca.de · 03/10/2026

When I need to sketch something, I also use Excalidraw. It’s simple, but still surprisingly powerful. But sometimes I have no idea how to visualize what I’m thinking, so I open it, stare at the blank canvas for a few seconds, close it again, and just start implementing 😆

120

Luca @lxca.de · 02/10/2026

AI makes me faster, but speed creates a new problem: reviewing code I didn’t fully write. I’m trying to define which parts of my SaaS I need to understand deeply, and where I can trust AI more. Finding that balance feels like a skill on its own. #buildinpublic #SaaS #AI

270

Luca @lxca.de · 02/10/2026

One idea: define areas where I need full understanding, like the data model, auth and API. For less critical areas, I can give the AI more freedom. That way I still set the architecture and boundaries, while letting AI solve problems beyond my current skillset.

000

Luca @lxca.de · 02/10/2026

Yeah, that’s pretty close to how I work right now. Every feature is a small PR I can review. But I catch myself approving things I don’t fully understand just to keep moving. So how do you stay fast with AI without sacrificing reliability or security?

210

Luca @lxca.de · 01/10/2026

I keep thinking about where to draw the line with AI-assisted coding. I want to build SaaS fast, but keep it clean, secure, and understandable. AI helps me move faster, but I don’t know every part of the codebase anymore. Where do you draw the line? #buildinpublic #SaaS #AI

150

Luca @lxca.de · 01/10/2026

Congrats on the strong growth! Whether you reached your goal or not, you kept going, and that’s what really matters. I was also considering registering my tool, Todolytics, but for now I decided against it. I want to focus on improving the product first before taking that step.

000

Luca @lxca.de · 30/09/2026

Since I shared my Todolytics user goal for the end of the year, I’ve been learning a lot about measuring user behavior and attracting new users. Setting that goal already pushed me to learn things I probably wouldn’t have otherwise. It’ll be tough, but I’m sticking with it 🚀 #buildinpublic #SaaS

040

Luca @lxca.de · 29/09/2026

I have multiple projects, all in different areas. I work on them in phases: a few weeks focused on one, then I switch when another needs more attention. It works, but context switching is still tricky. How do you handle multiple projects at once? #buildinpublic #indiehacker

161

Luca @lxca.de · 29/09/2026

You will. 7 paying subscribers just weeks after launch is proof people want this. Now it’s about talking to users, improving the offer, and making it easy for the next 93 people to say yes. Rooting for you 👀

010

Luca @lxca.de · 28/09/2026

Just pushed the newly redesigned Todolytics landing page 🚀 todolytics.app It took me quite a while to get to a design in Google Stitch I was actually happy with, but it’s finally live. Looking forward to creating much better designs from here. #buildinpublic #SaaS

040

Luca @lxca.de · 28/09/2026

So far, the most repeatable thing that brought users has been the Todoist integration directory. It worked surprisingly well without much active marketing. Now I’m trying to find channels I can actively repeat and improve instead of relying on discovery.

100

Luca @lxca.de · 28/09/2026

I like the idea of treating marketing as retrieval rather than persuasion. For Todolytics, I think the search would probably be something like “Todoist weekly review” or “how to do a weekly review in Todoist”. I should definitely start collecting recurring questions/problems more systematically.

000

Luca @lxca.de · 28/09/2026

That’s pretty much what I’m trying to build now. My main acquisition channel so far has been the Todoist integration directory. I’m currently improving my analytics to better understand the full journey from landing -> signup -> first weekly review -> returning user.

000

Luca @lxca.de · 27/09/2026

I have to admit, I overcomplicated Todolytics. Old flow: Sign up → connect Todoist → start review New flow: Sign up with Todoist → start review Much less friction. Learning: question everything. Don’t do something just because it’s the “standard” way. #buildinpublic #SaaS

180

Luca @lxca.de · 27/09/2026

That’s a good question, and something I’m still figuring out. Right now, I’m improving the event tracking so I can better see where users drop off or struggle. For me, a good signal would be noticeably higher engagement or completion rates in the area the experiment was meant to improve.

000