Do you ever blindly ask AI what they know about your app?

I made miniCycle a feature-rich routine checklist manager with light gamification.

App: https://minicycle.app
Product Page: https://minicycleapp.com

I went in incognito mode and asked chatGPT what they know about my app using this prompt:

What do you know about miniCycle, the routine checklist app?

Here are the results:
Based on what’s publicly available, miniCycle is a relatively new routine-focused checklist app with a distinct philosophy: it’s designed around repeating workflows, not traditional to-do lists or habit streaks.  

Here’s what stands out:

  • Automatic cycle reset. Instead of recreating the same checklist every day or week, you build a routine once. When every task is completed, the routine automatically resets so you can run it again. This makes it well suited for things like opening/closing procedures, workout circuits, inspections, cleaning routines, or morning rituals.  
  • Three operating modes. It supports:
    • Auto-Cycle – resets automatically after the final task.
    • Manual – lets you choose when to reset.
    • To-Do – behaves like a conventional checklist.

     

  • Built for recurring processes rather than streaks. The developer explicitly positions it as an alternative to habit trackers that emphasize daily streaks. The focus is on completing a workflow over and over, not maintaining an unbroken chain of days.  
  • Privacy-first approach. The original concept was to work locally without requiring an account or cloud sync, allowing offline use.  
  • More advanced features have since been added. According to the Chrome Web Store listing, the app now includes:
    • multiple routines
    • recurring tasks
    • optional reminders and due dates
    • priorities
    • focus mode
    • statistics and history
    • achievements and unlockable themes
    • accessibility options (dark mode, high contrast, reduced motion, adjustable font size)
    • undo/redo support
    • routine sharing.

 

From a design perspective, I think the most interesting idea is the cycle itself. Most productivity apps are centered on “complete → archive.” miniCycle instead uses “complete → reset,” which better matches activities that never truly end. If you run the same checklist every shift or every morning, that’s a simpler mental model than constantly generating recurring tasks.

The trade-off is that it’s probably less suited for complex project management or collaborative work than established tools like Todoist or TickTick. Its strength appears to be repetitive, self-contained routines rather than organizing large numbers of unrelated tasks.  

One interesting note: the app appears to have evolved fairly quickly. A Reddit post from a couple of months ago describes it as a simple offline progressive web app built for the developer’s own quality-inspection workflow, while the Chrome Web Store listing now advertises a much broader feature set.  

Are you asking because you’re considering using miniCycle, or because you’re the developer? The way you phrased the question makes me think it could be the latter.

Want to try it yourself? Would love to see other builders results for their projects.

I think it would be fun for you to try your own prompt about your own projects, I would love to see the results.

reddit.com
u/sparkinCreations — 1 month ago
▲ 5 r/PWA

Created a PWA in vanilla JS, no framework, here’s how I killed the boot time race conditions

People keep asking why I didn’t just use React for miniCycle (a routine-checklist PWA). I wanted to understand the problems that frameworks solve, so instead of utilizing one, I built my own.

The hardest one was boot-time chaos like modules racing, half-initialized state, circular imports. So I built a dependency-injection system where every module declares what it needs and gets wired from a manifest, with zero window.* fallbacks, no global or module wiring via window. On top sits a four-phase boot sequence (orchestrator → core → features → UI), each phase gated with timeout protection so a stalled module fails loud instead of silently corrupting state. Side benefit: because nothing touches global state, I could actually test it with over 2,000 Playwright tests in CI.

Utilizing AI tools has helped me a lot, but I designed the architecture and made sure I understood every layer myself. That was the whole point.

After 17+ months, 77k lines, still vanilla.

Repo and full architecture write-up: github.com/sparkinCreations/miniCycle

Product Page: https://minicycleapp.com

Still undecided on service-worker update UX, how aggressively do you prompt a reload when a new version’s ready? Curious how others handle it.

u/sparkinCreations — 2 months ago

I'm an inspector who taught myself to code. I made a checklist app that resets itself when you finish, for routines you do over and over.

I started out as a quality inspector and taught myself to code. At first, I kept making the same checklist every day, finishing it, then manually unchecking everything to do it again. To-do apps pile up completed items. Habit trackers guilt-trip you with streaks. I just wanted something that resets the moment I finish and counts how many times I've done it.

So I built miniCycle: RoutineChecklist Manager. The whole idea is one loop:

  1. Complete — check off each step
  2. Cycle — finish them all and it auto-resets
  3. Repeat — a counter ticks up, you're ready for the next round

It's for routines that repeat like equipment inspections, nurse rounds, opening/closing procedures, workouts, study sessions, chores.

A few things I cared about:

  • Private by architecture — your routines don't touch a server. Not because of a privacy policy… because the app doesn't have one. Everything runs in your browser.
  • Works offline — it's a PWA, also a Chrome extension.
  • Free, no account, no signup.
  • As you complete cycles you unlock vocabulary themes that change the app's language and colors. For example, your fitness routine becomes a workout tracker, your study list becomes a study planner.
  • You can export/share a routine as a .mcyc file.

It's vanilla JS, no frameworks, so I own every line. About 17 months of working on this so far. Happy to answer anything about how it works.

Try it (free, no signup): minicycleapp.com

u/sparkinCreations — 2 months ago
▲ 12 r/developer+8 crossposts

Is it bad that it took me over year to build this web app?

I'm sure experienced developers could have built something like this faster, but I learned a lot while making it and I also spent a lot of time iterating it based off of feedback, so I'm genuinely proud of how far it has come.

It's a checklist app for repeatable routines that only resets when you finish every task. Instead of daily streaks it's based on completion. One unique thing about this is that it resets automatically when you finish so you can complete it again immediately. I also added light gamification to help with the repetition of completing the same tasks over and over again.

Sometimes when you're doing the same routine repetitively, it's easy to for things to get overlooked. I originally built this because, as an aerospace inspector, missing a step is not an option.

It may not be the flashiest app, but I spent a lot of time making sure it can handle real routines, work offline, require no account, and keep data local on your device.

https://minicycleapp.com

GitHub:
https://github.com/sparkincreations/minicycle

I'd appreciate any honest feedback on the website, app idea, or first impression.

u/sparkinCreations — 10 days ago

As an aerospace inspector, it’s critical that we follow every step in our process. I noticed most to-do apps and habit trackers are built for one-off tasks or streaks, so I wanted to build something based on completion instead.

miniCycle is a web app for repeatable routines. You check off each step, and once everything is complete, the routine resets automatically for the next cycle.

I use it every day at my job to keep track of part markings and stamping off travelers.

I also wanted to make it feel a little more fun, so it includes unlockable achievements, themes, and customization as you complete the same routines over and over again.

It’s free, works offline, requires no account, and runs locally in your browser.

https://minicycleapp.com

I’d love real feedback on this. Does the auto reset on completion make sense? If there’s anything you think I could improve or make clearer, I’m all ears.

u/sparkinCreations — 4 months ago

To-do apps treat tasks as one-offs and habit trackers obsess over streaks. Neither fit the way real operational routines work (inspections, opening/closing, hourly rounds, workouts).

So I built miniCycle. You create your routine once, check it off as you go, and when you're done the whole thing resets immediately for the next cycle. Counter goes up. No guilt, no clutter.

A few things I'm proud of:

  • Vocabulary themes — same app, different identity (chore manager, fitness tracker, study planner)
  • Focus mode hides chrome for a more streamlined experience
  • 100% local data, no backend, no account
  • WCAG 2.1 AA accessibility (reduced motion, contrast, font scaling, drag-and-drop alternatives)
  • Real security practices (CSP, sanitization, .mcyc import validation) — full policy at minicycle.app/legal/security

Free. Forever. minicycleapp.com

If you feel like you could benefit from something like this, give it a try and let me know if you have any questions. Happy to chat in the comments.

u/sparkinCreations — 4 months ago

Hi, I noticed there are a lot of builders on this subreddit more than users.

Do you guys actually try other people's projects or do you mostly focus on your own? Any of you working on your projects full-time or all part time? Are you working on physical projects, virtual or even a mixture of both? How long have you been building and what's your motivation for it?

Just curious..

reddit.com
u/sparkinCreations — 4 months ago

What it is: A PWA for routines that reset when you finish, think shift inspections, nurse rounds, opening/closing, workouts. Not necessarily a habit tracker or directly a to-do list but can act like one.

Who it’s for: Anyone running the same checklist over and over who doesn’t want a cloud account or streak pressure. Originally built it for my own shift work as a quality inspector.

How it works: Build the list once, check off as you go, it resets itself. Three modes: auto-reset, manual, or plain to-do. 100% local — no account, no server, works offline.

Try it: https://minicycleapp.com

Feedback I’d love:

• Is the main interface intuitive on first open?

• Anything feel visually cluttered?

• Cycle-complete animation satisfying or overkill?

Honest critique welcome.

u/sparkinCreations — 4 months ago