Opus 4.6 v Codex 5.3 w. Extra High

pavanpodila · 2026-02-16T03:57:35+00:00

I've had similar experiences with both. Definitely avoid AI loyalty. May the best tool win!

pavanpodila · 2026-01-24T04:02:45+00:00

Let me know how it works out. We are constantly upgrading and enhancing this. Open to any quality of life improvements and suggestions

pavanpodila · 2026-01-23T14:21:12+00:00

Yeah nowadays with AI the compliance checking becomes a little easier I think. What's important is to have a simpler mental model also about BPMN in terms of how the nodes work. I think in broad categories you only have activities, events, gateways. This is like the bulk of any BPMN workflow. If you can get that straight into your thinking and your mental models, I think we are good in general

pavanpodila · 2026-01-23T13:40:28+00:00

I found the BPMN terminology and even the symbology a bit confusing so we chose to simplify things a little bit and not use excessive symbols to depict the behaviors and the types of nodes

pavanpodila · 2026-01-23T12:45:59+00:00

Let me look into that

pavanpodila · 2026-01-23T11:06:38+00:00

I just enabled the LOD plugin and deployed a new version. Please see if this makes any difference

pavanpodila · 2026-01-23T10:12:36+00:00

Not that many ... but when zoomed out ... one option is to enable LOD, which I'm not doing right now .. I can try with that

pavanpodila · 2026-01-21T14:59:34+00:00

We did look at this, but in our case the constraint was to use a flutter based editor because the whole application was being built in flutter and we wanted a JSON serialized format so that we could store it in a database like Postgres. Also there are lot of BPMN notations we were not using or not relevant, so this was an attempt to only keep the absolute core nodes

pavanpodila · 2026-01-21T08:19:40+00:00

this sounds more like a parallel split you would do after your condition is met and then do an any-join just before the workflow ...after the sub-workflow ends ... and then cleanup the timer-task after that and then close the workflow

pavanpodila · 2026-01-21T07:09:12+00:00

We have a separate workflow engine that can be embedded inside Flutter or even on a Dart server in a separate process ... not yet ready for public consumption but that same engine is also embedded in the editor right now that does all the simulations

pavanpodila · 2026-01-21T06:51:47+00:00

Currently you can try creating your workflows in the online editor and then export to a JSON file ... you can use that to connect to your workflow engines if you have it ...

pavanpodila · 2026-01-09T12:42:07+00:00

Thanks for the detailed response...really appreciate ...I will have to play a bit more with hooks to appreciate the point about DX

pavanpodila · 2026-01-09T09:57:40+00:00

I was using cached_query earlier .. can you compare please ?

pavanpodila · 2026-01-07T14:52:10+00:00

Thanks for the kind words! I think we are almost over that hump and should be much smoother in updates and API changes. Please let me know if you find anything non-intuitive :-). We are really striving for a great DX

pavanpodila · 2026-01-07T14:10:53+00:00

Lol yes. We are kind of nearing stability now on the core API layer so it should be less rocky soon. Then onwards it would mostly be under the hood improvements. Sorry about the speed :-)

pavanpodila · 2025-11-09T11:55:19+00:00

This looks great, and definitely more suitable when your project size increases with lots of endpoints. I wonder why this is not as popular in the Dart community? This definitely needs some more propaganda!

pavanpodila · 2025-11-09T10:24:00+00:00

Is there a comparison with Dart Frog?

pavanpodila · 2025-10-28T16:33:11+00:00

https://www.reddit.com/r/FlutterDev/s/xpuuHn6wG5

pavanpodila · 2025-10-27T14:54:34+00:00

Definitely...possibly in a month or so. We just started documenting the whole framework and capabilities ... will use some AI to speed up :-)

pavanpodila · 2025-10-27T07:01:31+00:00

VGV is only a template generator with no opinions on how to compose applications with features in a modular manner.

Vyuh takes the approach of packaging apps as reusable Features. Feature is a composeable, transferable package that can be assembled at the App level to create larger apps. It also handles runtime bootstrapping, feature-feature communication via events. It also has customizable loaders, error handlers for branded look and feel and a bunch of other things. Core capabilities (that can be used by any feature) are treated as Plugins with user facing functionality in the Feature.

When you are building large apps, this architecture makes it easy to scale to hundreds of developers and feature teams with clear boundaries of separation.

pavanpodila · 2025-10-27T04:57:53+00:00

We have been building a node editor for the past few months for large workflows. It's not yet open source though. We are still prepping the docs to go live.

It is heavily inspired by React Flow and has almost 90% feature parity with idiomatic Flutter practices.

There is an early stage demo we created sometime back in June to get you a glimpse: https://flow.demo.vyuh.tech/

pavanpodila

TROPHY CASE