Been working on mapping out more of the features I'm adding to Screenity (not exhaustive) + comparing against other screen recorders. Hard to compete with some of these as a solo indie maker (some features are 💸💸💸), but I'm making it work so far by optimizing costs. What else should I add? 💡 - ThreadSky

alyssaxuu.bsky.social • 691 days ago

Been working on mapping out more of the features I'm adding to Screenity (not exhaustive) + comparing against other screen recorders.

Hard to compete with some of these as a solo indie maker (some features are 💸💸💸), but I'm making it work so far by optimizing costs.

What else should I add? 💡

Comments

thejoat.bsky.social•691 days ago

is this the featureset your building against? imho branding is everything.

alyssaxuu.bsky.social•691 days ago

It's a bit more nuanced than that imo, the app is free & open source rn w/ 160K+ users. I need to:

- Convince at least some of them to upgrade
- Attract new users, switching from Loom/others

I think a decent featureset would help w/ that. Branding is top priority too though, redoing it all from 0.

thejoat.bsky.social•691 days ago

freaking awesome just gave it a try. Is there a way to prevent the overlays from being recorded too? the obs orb and the controls...

alyssaxuu.bsky.social•691 days ago

Not really possible with the Chrome API as an extension. But I am looking at ways in the new version to hide and obscure the UI so it's not as prominent.

dkh.bsky.social•688 days ago

Make pricing simpler than those! It seems like you're doing the recording as well so you can do this. Since you are in charge of the recording settings, there's no reason to separate time/resolution/size costs. If, say, a video was within the time limit but too big in file size, it would be on you.

alyssaxuu.bsky.social•688 days ago

I set the metrics I'm charging through the provider I use for streaming/transcoding/storage/... which are storage+bandwidth. I've set reasonable caps/user "globally" to stay cost effective, but there's other added costs (e.g. editing, edge cases) which I need to take into account. Bit tough 😅

dkh.bsky.social•688 days ago

I have always loved the way Mux does it: One rate. Since they are the ones in charge of the codec, bitrate, etc. they can't really charge the user for things outside their control. If your screen recorder will let users choose some of these settings themselves, then you can still charge for them

alyssaxuu.bsky.social•688 days ago

I do want to avoid all these "micro-limits" as much as possible since they're annoying but I don't want to accidentally put myself in a position where the cost to sustain a user > what they pay, as a solo maker w/ no funding.

dkh.bsky.social•688 days ago

The price should still be whatever you need it to cost. I am not saying to lower it, but just make it easier to estimate. Someone using a web-based recorder likely does not want to think about if the higher resolution will also inflate the file size too much (or not understand it)

dkh.bsky.social•688 days ago

Since we already know that higher-resolution will make the file size bigger, factor the cost of one into the other maybe

alyssaxuu.bsky.social•688 days ago

Yeah, maybe, it could work. I'm still fine tuning these things, I'll likely not have the finalized pricing in a while, planning to see the reception first. I think my main concern is less so the resolution and more so the traffic from sharing those videos, it can get pricey.

Comments

Posting Rules

Reply