webviz VS lowdefy

For the web based part, in terms of integration with ROS RobotWebTools (especially with RoslibJS) and rosbridge cover already a lot, so maybe you may want to first check what's available there. Webviz is also a great web based tools with many components for visualisation.

Hey HN, one of the creators here! I made it at Cruise because it was super painful to develop https://webviz.io with manual memory management (lots of ArrayBuffers), WebWorkers, etc. I thought that there must be a better way.

Very curious to hear stories from other folks building intensive stuff in the browser. How are you dealing with performance issues in Javascript? Have you tried using Rust or C++ with WebAssembly for parts of your apps? How did you make 2d/3d rendering faster? Would you want to use something like Zaplib?

Webviz is a great tool. Just drag the .bag file onto the browser window and you can start viewing the data.

Webviz is actually open source for the most part. https://webviz.io

U can try https://webviz.io/ or https://foxglove.dev/

Cruise | Software Engineer | San Francisco, Seattle, or REMOTE | VISA acceptable | https://www.getcruise.com

Cruise is building the world’s most advanced, self-driving vehicles to safely connect people to the places, things, and experiences they care about. We believe self-driving vehicles will help save lives, reshape cities, give back time in transit, and restore freedom of movement for many.

I'm an engineering manager hiring specifically for the Webviz (http://webviz.io/) team. I'm looking for frontend engineers who want to make fast, beautiful browser-based visualizations of the car using WebGL, WASM and Javascript.

Much of the work that we do on this team is open-sourced (check out the code at https://github.com/cruise-automation/webviz). Cruise vehicles produce mountains of data; we have to visualize it in dozens of different ways at a high frame rate. We recently built a Javascript object proxy that wraps all of our input binary data in an object-like interface that only parses data on access, so that we can limit garbage collection pressure and improve our frame rate. If this kind of project sounds interesting, you might enjoy working on Webviz!

Reach out directly to me if you're interested in the above (open to associate/senior/staff levels), or if you have any questions about Cruise.

PS - for those of you who have seen or used Webviz, Foxglove may look familiar. Some of our team previously worked on Webviz at Cruise, and we reused much of their code, although it has been heavily refactored, several new features added, and we have more coming soon.

I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.

I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.

Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?

See Lowdefy:

https://lowdefy.com/

https://github.com/lowdefy/lowdefy

Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!

Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)

https://github.com/lowdefy/lowdefy

Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy

co-founder here :)

100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.

We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.

This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.

1 - https://github.com/lowdefy/lowdefy

https://github.com/lowdefy/lowdefy Co-Founder here.

Check out https://lowdefy.com/ they even have a sample survey app as one of their examples.

You can build an app that would do this

Lowdefy is a low code tool that uses AG Grid as a block component, allowing you to create apps which render data in AG Grid without a lot of coding knowledge. There is a Lowdefy example using AG Grid here.

Shameless plug, also check out Lowdefy - https://github.com/lowdefy/lowdefy

I’m also going to jump in here and say try Lowdefy https://github.com/lowdefy/lowdefy - co-founder here.

We take a different angle and believe that low code should still work like code. We focus on a developer first approach.