The most common workflow we see is people bouncing between 5-10 different dashboards daily. Would love to hear what pain points you're running into.
Also happy to give you early access if you want to test it out.
I built Toffu after getting frustrated juggling 20+ marketing tools.Instead of logging into Google Ads, opening GA4, checking Meta dashboards, and writing reports, you just chat:"What's my ROAS this week?" "Pause underperforming ads" "Create a competitor analysis" "Increase budget on winning campaigns"The AI executes everything – not just recommendations.Connects to: Google Ads, GA4,...
I’m Or (YC S18), i previously founded the Yo app and co-founded Anima.I’m now building an AI agent that’s like Devin for marketing.While building the agent I’ve realized how different it is than conventional SaaS.For example, I realized that if I use schema for the db, I limit what the agent can do (As it can only store structured data based on my schema).I no longer think of features, as that...
So we've built Scooby and added some missing feature like code comparison.
We focused on simplicity and cost optimization.
Feedback and contributions are welcome!
Amongst other things designers also use our generated code to learn how designs can be viewed in browsers as HTML/CSS.
When Sketch introduced Symbols, they started making designers think like developers, in the sense of reusable self-contained components. This makes our and companies like us live easier. And for that we thank them :)
For example, we (Anima - YC S18) are doing it (https://www.animaapp.com)
When you say "users", what do these users "use" Bitcoin for besides speculating on its price?
Do you know of any real usage?
If this works as advertised, this is huge.
When I'm making API calls from my app to different services, I know for a fact that there is no extra latency that might be caused by a third-party. How do you deal with maintaining low-latency while still having to re-route my original API call?
Again, as someone who dealt with many APIs over the years, I think this kind of service is game-changing.
Today the tools we provide force designers to think in a more structured way. A great example of this is Stacks, which forces a layout to be consistent. Unstructured design, or in other words, floating layers corresponds to CSS's absolute position. Stacks, however, corresponds to CSS's Flexbox.
By enforcing designs to adhere to concepts which are borrowed from the development world, we can actually convert design to code.
In the long-term, we see that not only layout will be structured and translated, but all aspects of a user interface.
For the time being, even if developers don't use the generated code, but rather just inspect it is better then guessing how a component should work by staring at a static image or a GIF.
If you take for example this elaborate interactive component: https://handoff.animaapp.com/#/timeline/XKHmOQP5Hcuipv/anima...
It was made completely by Michal, our co-founder/designer in Sketch with Anima. No code was manually written. Trying to convey this today usually involves hand-waving or for advanced teams, a GIF. By handing off functional code, a developer can interact and see the values that make this work. Even if not using the actual generated code.
Does that make sense? What do you think?
So while using Auto-Layout can save an enormous amount of time creating UI, it definitely needs to be used by all designers that work on the file.
In terms of exporting to other parties such as Zeplin, we have a feature that turns off all the layout rules just before exporting. If you have tried it out here it is: https://animaapp.github.io/docs/v1/launchpad/faq.html#Export...
And thank you for the kind words!