BioDrop VS dioxus

I've started My Open Source Journey by Contributing to one of their Open Source project LinkFree (Currently Known as BioDrop) and the Community members Helped me in that process!

The link to the “Biodrop Account” project

A few months later, Biodrop, another open-source project, followed the same implementation that we used in our project to enable the embedding of their cards on other websites.

As this kind of large repository includes both frontend and backend, understanding the codebase and setting it up locally was quite hard, and for some, I did not had the necessary infrastructure or software in the system by the time. But gitpod.io was really helpful here in setting up the few projects that are integrated with it. Gitpod is a cloud-based development platform. It provided a seamless and ready-to-code environment, ease the complexities of local setup. In this process, I made contributions to the Biodrop and freecodecamp.

I have also contributed to other open source projects, including EddieHub, Forem, and my own.

I follow a lot of projects from different backgrounds, like Kubernetes, Docker, Preevy my Livecycle etc. But I want to give a special mention to BioDrop from the EddieHub Community. It's an awesome project that helps you connect to your audience with a single link. I'm also a maintainer and focus more on the DevOps side of things.

LinkFree connects to your audience with a single link. It allows you to showcase the content you create and your projects in one place, making it easier for people to find, follow and subscribe.

- https://github.com/EddieHubCommunity/LinkFree: Connecting with your audience with a single link, showcasing your content and projects.

View on GitHub

They seem to develop some stuff like a linktree alternative and a first issue finder.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI