openreplay VS appsmith

- Optimize user experience: use insights to refine and improve your app’s usability.

Interested? For more details, you can check out the GitHub repo [0] or documentation [1]:

[0] https://github.com/openreplay/openreplay or documentation

[1] https://docs.openreplay.com/en/rn-sdk/

Hey HN,

For anyone who uses session replay tools to debug, monitor, or analyze user journeys, this feature might come in handy. OpenReplay — the self-hosted session replay tool that helps developers troubleshoot web apps faster — now supports tabbed browsing.

*Here's how:*

1. Capture and replay user sessions that span across multiple browser tabs, all within a single recording.

2. OpenReplay's tracker communicates across browser tabs, ensuring accurate tracking of each tab, even when duplicated or opened with `window.open` without `_blank`.

3. With "co-browsing", you can watch and support users in real-time and see how they navigate across multiple tabs of your app.

*Why it’s important?*

1. This feature is convenient for developers as it allows them to easily identify bugs by reviewing a complete session in one replay, rather than having to reference multiple recordings.

2. It provides a deeper understanding of the user journey and interactions across multiple tabs in your web app, helping in the comprehension of complex user behaviors and paths.

3. It provides accurate feedback on user tab actions such as opening, switching, and closing tabs, assisting in UX/UI improvements.

Interested? For more details, you can check out the GitHub repo at https://github.com/openreplay/openreplay.

You could maybe get in a scenario where a company rather sneakily changes their license without proper announcement to make usage non-open and billable, but that's pretty rare and bad behavior and that underhandedness may bite them back if it goes to court (I am not a lawyer). That said, it can happen. As an example, see this discussion I opened where the project switched licenses and the maintainers thought it was enough to only really announce this within a 1 hour YouTube video (Rather than their blog or update notes).

OpenReplay would not be typically be considered open source. (Which I have raised with them and have since been blocked from their repos).

How does it compare to OpenReplay ?

> Before deciding on ClickHouse, we were planning to use OpenSearch

You should have tried Quickwit :)

Anyway, sounds like a great project, best of luck!

[1] https://github.com/openreplay/openreplay

[2] https://github.com/quickwit-oss/quickwit

I would disagree with OpenReplay being open source, as I raised with them back in July (I've also since been blocked from their GitHub org for opening that discussion).

appsmith — Low code project to build admin panels, internal tools, and dashboards. Integrates with 15+ databases and any API.

For instance, although we don't have a native signature capture widget (yet), you can easily build one with just a few lines of JavaScript, and the signaturePad.js library.

Effective communication and efficient meeting management are key to a team's success in the modern workplace. Recognizing this, we will develop an AI-powered meeting assistant app to transform Google Meet recordings into automatically generated meeting notes with key takeaways and action items. The blog post is tailored for every creator from developers to no-coders who are interested in the intersection of AI and productivity tools. It's particularly useful for those with limited AI-development experience and who want to build AI applications by using simple low-code tools like Unbody and Appsmith.

And if you don't need a mobile app and can get by with web only, check out Appsmith. It's open-source, can connect to Google Sheets, Airtable, and any API or database, and is free for unlimited users and apps. Feel free to DM me if you need a hand getting started with either one. I'm Joseph from the Appsmith Developer Relations team, and GreenFlux on the AppSheet forums.

Appsmith- Build build custom software on top of your data.

This wasn't an easy journey. While this functionality was in high demand, early versions were frustrating to use. In our earliest implementations, it wasn't even possible to pinpoint where the conflicts were in a file. Even members of the Appsmith development team would avoid using our early Git implementations. We even had a rule for our internal “Hackathons” that using the Git feature was banned because it kept breaking! So we know why other app platforms had avoided fully implementing Git: it really was a challenge to get it working right.

Suggest features and help to guide Appsmith’s future: Appsmith's community keeps us at the forefront of internal tools with feature requests for the latest third-party integrations and robust community support.

Ever tried building a responsive web application using AppSmith as the frontend and Baserow as the backend? Well, Frederik Duchi created a new set of videos showcasing the entire process! The videos include an interesting use case: reporting a nest of Asian hornets in an area. 🤯