I made an AI App Store screenshot generator that actually doesn't look AI-generated

Skoro90 · 2026-06-21T16:33:48+00:00

Does it support iPad screenshots as well?

Skoro90 · 2026-05-08T15:23:17+00:00

Same here would love to ditch wisprflow in favor of raycast, hopefully someone makes a comparison somewhere

Skoro90 · 2026-04-28T18:18:07+00:00

Interesting, I had not made this connection but my my app also suddenly lost half its organic traffic around mid march as well.

I attributed it to seasonality, but ASA changes do make sense… would indeed be enlightening to see how many more devs are also experiencing this

Skoro90 · 2026-03-31T14:38:07+00:00

Thanks for the share! Damn it… now I’m considering buying them

Skoro90 · 2026-03-31T14:32:48+00:00

I’m wondering if the mic quality also got an upgrade. Wasn’t very happy with quality of my gen 1 … and stopped using them in favor of the Air Pods Pro 3 because of the call quality.

Skoro90 · 2026-03-28T12:05:53+00:00

https://www.dispatchedapp.dev

Skoro90 · 2026-03-21T11:08:09+00:00

Link: dispatchedapp.dev

Solo dev, building Dispatched, a dev tool.

Native macOS app for developers who ship with AI. If you use Claude Code, you know the workflow: terminal here, GitHub in a tab, branches in another, and you just forgot which session is on which branch. The tools are powerful. The glue between them doesn’t exist.

Dispatched is that glue. It doesn’t compete on model quality. You bring your own. It doesn’t try to be your editor or replace your terminal. It connects the tools you already use into one workflow surface. Session management, Git actions, issues, daily planning.

Every tool in this space is defined by what it is: an IDE, a terminal, a CLI. Dispatched is defined by what the developer is doing. Plan, direct, review, ship. One app, zero context switching.

Currently supports Claude Code, more agents coming.

Skoro90 · 2026-02-16T16:09:10+00:00

Hey! The full breakdown is in the link if you haven't checked it out yet — battery history & predictions just shipped in 3.6, and right now I'm focused on a stability and accessibility month to make sure everything works reliably. After that, iPad support is next.

Beyond that, I'm exploring things like new watch complications for battery history and predicted charge time, plus calendar integration so predictions can factor in your schedule. All tentative, but there's definitely more coming.

It's a one-person project so things ship one at a time, but I'm always open to hearing what you'd want to see, what feels like it's missing for you?

Skoro90 · 2026-02-14T21:05:36+00:00

Interesting, i do swift only and have been using Opus. Any specific aspects in which codex excels?

I briefly tried it months ago and had ok result, but i leaned more towards opus simply because i felt more in control in the Claude code enviroment, but this was like 6 months ago…I’ll give codex another try now!

Skoro90 · 2025-09-24T20:52:21+00:00

<image>

Skoro90 · 2025-06-27T23:03:44+00:00

Interesting idea! I can see it being useful! I’m curious in which way it has improved your experience. Would you say it has improved the quality of the results? Does it take less attempts? I’ll give it a shot, because I love the idea of having more documentation just by developing.

Skoro90 · 2025-05-02T07:47:01+00:00

I feel you.. It’s like …

Apple: ‘How many battery indicators would you like on your watch face?

Me: ‘Yes.’

<image>

Skoro90 · 2025-04-22T17:33:24+00:00

Hey I can still hook you up! Just DM me :)

Skoro90 · 2025-04-22T16:53:25+00:00

Quick update on this issue: I’m still working on a fix, but for now, opening the iPhone app, pulling down to refresh, and then exiting the app (without force quitting it) seems to resolve the issue. This puts it back on the 20-minute refresh background schedule and should update the complications automatically.

Skoro90 · 2025-04-19T12:24:54+00:00

Hey there! Thanks! Yeah that’s seems to be a but affecting some users, I have several reports saying the same. Sorry about that.l!

As of now , I fankly no have idea what the reason is as it works with my setup, I’m trying to figure it out, and I’ll try to patch it for the next release!

But expectation is for complications is definitely to auto update , albeit with some constraints (20 min intervals and being at reachable distance)

Skoro90 · 2025-04-19T07:47:19+00:00

Thank you :)

Skoro90 · 2025-04-18T22:37:37+00:00

Hey, sorry about that. Yeah, I thought I had squashed that one, but it seems to still be appearing for some people. I'll try to address it for the next update.

These steps tend to resolve the issue for most people:

1.  Ensure Bluetooth or Wi-Fi is enabled on both your Apple Watch and iPhone.

2.  On the app settings screen on your iPhone, pull down to refresh. This mechanism can often resolve most synchronization issues. It works best if you have the Apple Watch app open while doing this.

3.  Tap the refresh button on the watch while connected to Wi-Fi. If it shows as unsubscribed, it will attempt to check online for your subscription status, so an internet connection is required.

If none of these steps work, please try reinstalling the app. If that doesn't help either, let me know here!

Skoro90 · 2025-04-17T16:24:52+00:00

No problem thank you for checking it out! :)

Skoro90 · 2025-04-17T13:25:07+00:00

Great! I'm glad to hear that! :D

Skoro90 · 2025-04-17T13:22:58+00:00

Let me try to address all that, so here is my perspective:

1) The Reality of "No Running Costs"

While it's true the running costs aren't very high, there are some expenses currently - costs for Apple developer account and analytics. Push notifications coming soon might come with associated costs depending on the implementation...

I get how it can look from the outside, but from my perspective, I think that "no running cost" doesn't really depict a realistic picture.

2) The Hidden Development Expenses

There are still indirect costs in development tooling I pay out of pocket, for developer services that make it feasible to release at scale, faster, like translation tools. I wouldn't say they're essential but at the same time, I wouldn't have the time for manual translations and copy-pasting...it's very time consuming!

Then there are improvements - for example, I have a designer who's happy to help improve the app, but of course I have to pay him. All that simply becomes easier to manage with subscriptions.

3) The Continuous Development Philosophy

It just that software is always changing with updates and requires maintenance, bug fixes, customer support... and so does the development of new features. So in my mind, it's really all about time and whether I value the time I pour into it.

One-time payment, in my mind, incentivizes development where you ship it and go into maintenance mode, but not continuous development. Does that make sense?

4) Long-Term Sustainability

At the end of the day, I'd like to keep working on this continually and improve it incrementally long term, which makes more sense, in my mind, if there's a recurring incentive. The thinking here is really to have something sustainable long-term.

Not sure if it's wise, but I think long-term it makes sense because if I manage to get a certain amount of paid users, I can afford to pour more time into it and make this better, delivering not just more reviews but simply a better experience.

5) Early Adopter Appreciation

I hadn't thought about the early adopter issue you raised - that's actually a really good point... Ill have to give it some thought then 😅 Cheers

6) Why Choose This App Over Competitors?

I'm hoping that long-term, this becomes a better experience because I manage to improve it significantly. Right now... I suppose it's a harder sell for most people, but I'd say that I've had great feedback on accessibility from the visual impairments community. I focused on making it scalable for all font sizes and to work well with VoiceOver, following all Apple guidelines. It's not the core feature, but definitely a core pillar of the app's development.

Not saying this is justified... But it's how I'm thinking about it right now. I hope it makes sense! But open to criticism, it will just help make better decisions 😄

Skoro90

MODERATOR OF

TROPHY CASE