1. First thing is an interactive-looking image, with a play button etc. I'd recommend embedding a real widget built with your tool there.
2. The FUTURE/TODAY sections are really spaced apart and have no images.
3. In the Skada section, "powerfull" is spelled incorrectly (should have one L).
I know that sharing stuff online is stressful - so really want to emphasize that it looks like you're doing great work here, and congratulations on shipping :)
Definitely use a video showing features above the fold. A picture doesn't communicate very much to me, especially for something for animation/motion.
As a contrast, our tagline - which my co-founder hates, and also isn't great - says "want better sleep?". It's clear what we're bringing to the table, what area we're working in.
- Moos.app has built-in "behaviors" that are sort of a template for interactions. For example the scroller behavior allows you to put text next to your visuals, when the user then scrolls your visuals will update. It also works on mobile and desktop without additional actions.
- I found that using SVG or HTML for complex animations is way to slow. That's why moos.app uses a custom WEBGL renderer.
- Moos.app works in the browser, Tumult is a mac app
- As Tumult is older it has a bigger community
- Tumult has no web hosting build in (I think). With moos.app you click a button and you get a link (or a self contained HTML file)
- Tumult is a one time payment while moos.app is usage-based-payThe examples on the website are nice, however from what I saw, they can be done in Hype as well. As you mentioned, Hype is more mature and has a sizable community, many of whom contribute towards extending its functionality by creating custom modules in JS for things like dynamic data imported w/ JSON.
For 3D animation I've also used Spline, which is in beta. It's interesting, but on my 2014 MBP, it runs slowly and the fans are constantly on, which makes it less appealing for my use.
Did you try Canvas2D? Also curious to what you used for the 2D rendering, did you do your own implementation?
It seems cool, just have never encountered pricing like that and it would certainly take me aback and reconsider using the tool. Especially when I don't fully know what a "project" is.
- One time pricing can be a real hurdle for users to pay upfront. Remember adobe costing a lot of money up front. The upside is that after this initial huge hurdle your free to use the product. For the business non recurring revenue means they need to batch changes to make buying the product worth while. This results in a long cycle between updates.
- Subscription pricing aligns the business with it's users. Users pay only for what they use and the business can ship features to the user as fast as possible.
- The downside is the subscription is often 'per user' and is done on an ongoing basis. You pay for the tool even if you don't use it.
- Usage based pricing: you only pay for what you use in the smallest quantity that is understandable. This is what I use and what AWS uses for example. I think this is a really fair pricing model. If you're only doing one project it might cost you 3 bucks, but if you are a company that uses the tool fulltime you pay accordingly.
If you open one of the examples that is one project. Your project can be published at one unique URL.
I’m not convinced. Maybe I’ve misunderstood something.
Charging for time spent developing is very different from what AWS does.
If more people have problems I will have to fallback to just MP4. It is a shame though, the AVIF files are a lot smaller.
Reminds me of Flash.
Building all of this is a lot of work (and this is only the beginning). I think open-source is not a viable way of building this right now. Development will stall before a critical mass of features allows wider adoption.
Are you familiar with Corel Rave? That was perfect Flash editor imho. I still miss it.
One feature of this tool that I am particularly excited about which I think people here will appreciate is the way expressions are implemented. Expressions are fully typed and the types are automatically inferred. When you leave a hole the editor will tell you what type fits there.
Don't forget to try out the (full) app in the playground!