Fine with me, it just means I'm not going to use this. On an individual basis that's fine, but if you intend to get some B2B action by selling this app to shops and groups >25 people, you should be aware that supporting only one OS is going to make it a lot harder to pick your app.
Again though, serve whatever niche fulfills you. I don't even know what their app is/does after reading this article, so I'm going to assume it's not a life-changer so much as it is a native version of something we already have.
Agreed—and we're currently deliberating how we'll build for other OSes.
Re the article not explaining what Remotion does, we're trying to avoid plugging our app itself in our technical posts—we figure anyone who's interested can click onto the main site.
Your site asks me to fill out a form to get started. It's pretty narrow on jobs list, but only after getting me to fill it out do you tell me that NOPE, thanks for the survey data, still need to "CALL SALES" anyway like some kind of 20th century dinosaur.
Super annoying that you want to schedule a call "or" get an invite. If an invite works, people should not need a call.
> "Want to skip the call? Ask any Remotion user for an instant invite."
I'd assume you're a user. I'm asking for an invite. Email in profile. :-)
That's fine. I just don't really see much of a use for this personally, especially if it's Another Competing Standard for video calls. I've been able to get similar results by just pinning a Google Meet window at the top of my screen, but maybe I'm missing a killer feature here?
Fair enough. Many of our users used to do what you do.
Reasons they sometimes switch from long-lived Meet calls:
- Free up 200-300 MB of RAM when in call.
- Features specific to coworking (e.g. shared music DJing) or eng pairing (e.g. multi-way screen share).
- Presence when out of video calls. For example, you'd see if anyone on your team is in the Meet without having to ping each other. Leads to more unplanned hang outs.
Considering that people mostly use either webapps in a browser, or Electron-based 'native' apps, does saving 300 MB with a specific app really makes that much of difference?
I do understand that macOS APIs and libraries are easy to use, development experience is (at least in my opinion) better than with Electron + framework of your choice, and you can achieve better integration with the OS, but I don't think that saving 200-300 MB is really important to the end users.
TBH we weren't sure how much people would care. What we've found is that when we build a bucket of value props to solve for a given use case (e.g. eng coworking), different users will find different value props to resonate.
So some people are very glad to save RAM, CPU, etc. Others don't care but love shared music DJing etc...
Again though, serve whatever niche fulfills you. I don't even know what their app is/does after reading this article, so I'm going to assume it's not a life-changer so much as it is a native version of something we already have.