Vella.ai

Vella.ai

Software Development

San Francisco, CA 682 followers

Unleash discovery with Vella.ai

About us

Unleash discovery with Vella.ai Delightful content and recommendations are just out of reach due to disconnected data and privacy expectations. Connect your emails and socials to our privacy-first smart feed to unlock content suggestions.

Website
https://vella.ai/?q=stealth
Industry
Software Development
Company size
2-10 employees
Headquarters
San Francisco, CA
Type
Privately Held
Founded
2020
Specialties
Consumer, Software, and AI/ML

Locations

Employees at Vella.ai

Updates

  • View organization page for Vella.ai, graphic

    682 followers

    We are launching our MVP to help you clear out your inbox at the end of the month. Upvote us on ❤️ Product Hunt ❤️: https://lnkd.in/gBfj28yB Tune into the monthly local-first talk for the insider track on the Vella.ai origin story.

  • Vella.ai reposted this

    View profile for Yonatan F., graphic

    Founder & CEO at Vella.ai | Harvard MBA, x-LinkedIn dev

    📣 Another exciting step towards a frictionless, silo-free internet. Kyle Simpson has been working hard to re-imagine identity as something you take with you across applications. And no, it's not a single sign-on; there are no servers involved. Everything can now be encrypted at rest with a biometric factor (FaceID, TouchID, etc) using passkeys. 🙅🏽 No servers involved 🔓 Encrypted at rest 🛜 Works offline Still reading? Join the movement to de-silo the internet at http://lofi.so and dig into the post below.

    View profile for Kyle Simpson, graphic

    [OFFLINE PAUSED ACCOUNT]

    Remember my several recent posts talking about that "Local Data Lock" library? There were lots of inquiries/feedback assuming that such a library should also handle local client-side storage (localStorage, IndexedDB, etc). I didn't think that LDL should handle this, as it was designed more narrowly to focus only on the encryption (and protecting the cryptographic key in a biometric passkey). With LDL, you *might* end up storing the encrypted data locally. Or maybe not. ---- HOWEVER! I did take the point that making the storage part much easier, and especially abstracting across various client-side storage mechanisms, while still automatically handling the encryption (on write) and decryption (on read)... that was a useful idea and a library that should exist. So I built it! It's called "Local Vault". This library provides a simple key-value storage abstraction, backed by 5 different client-side storage mechanisms (IndexedDB, Local-Storage, Session-Storage, Cookies, and OPFS). It automatically handles the encryption key stuff, including the biometric passkeys. Should make it dead-simple to build local-first web apps that protect user data on-device (no servers!), encrypted at rest, without requiring the user to do anything more than present a single biometric passkey factor (FaceID, TouchID, etc) to access or update their data. No insecure/troublesome passwords to worry about! Example code: import "@lo-fi/local-vault/adapter/idb"; // IndexedDB adapter import { connect } from "@lo-fi/local-vault"; var vault = await connect({ storageType: "idb", addNewVault: true }); await vault.set("property","my value"); // true await vault.get("property"); // "my value" I'll link to this library github repo in the comments soon. But if you poke around my github commits you'll quickly find it. It's also on npm at "@lo-fi/local-vault". Enjoy!

  • View organization page for Vella.ai, graphic

    682 followers

    Clear out your inbox & unleash discovery with https://vella.ai

    View profile for Yonatan F., graphic

    Founder & CEO at Vella.ai | Harvard MBA, x-LinkedIn dev

    A month ago, I attended the first local-first global conference in Berlin. It took me a full month to clear out my inbox, and while I enjoyed the reminder for my Berlin trip, nine emails for one round-trip flight is too much. Our inbox was not designed for this use case. Soon Vella.ai will allow me to collapse these nine emails into a single live widget that I can archive with a tap.

    • No alternative text description for this image
  • View organization page for Vella.ai, graphic

    682 followers

    Join the next local-first Discord meetup on Tuesday. Here is our guide to catching up on all things local-first. 🎓 The original local-first paper: https://lnkd.in/dwNv-9bB 🎥 App.js 2024 local-first presentation: https://lnkd.in/gd9g98gB 📅 The first global local-first conference coming up next week: https://lnkd.in/g3uZu5eE 🏡 The home of local-first: https://lofi.software -Enjoy! #localfirst #lofi #localfirstsoftware

  • Vella.ai reposted this

    View organization page for Vella.ai, graphic

    682 followers

    Another great post on #localfirst right on the heels of the awesome interview by Scott Tolinski and Wes Bos at Syntax.fm: https://lnkd.in/g5krmiEa Checkout https://lofi.software to learn more

    View profile for Michael Awad, graphic

    Setting you up for productivity without complex systems

    There's a new movement in software development. It’s called local-first development. Here's why it has the potential to be the next big thing: People are caring more about their digital privacy. Their entire lives revolve around their smartphone, which is the main reason. Another issue arises when moving to mobile: Unreliable connection. You submit a form and get confronted with an endless spinner. Everything you filled in is gone. Recognizable? There are ways to avoid this, but we haven’t resolved the deeper problem. Mobile-first development isn’t enough. We need to rethink our approach to software development. That is where Local-first development comes into play. 🔐 Privacy & Security:  Local-first places priority on safeguarding user data. It keeps it where it belongs, on the client's device. This pivot away from traditional cloud dependency is a technical paradigm shift and takes digital privacy to the next level. 🌐 Offline Capability:  Local-first development allows the freedom of seamless functionality, irrespective of your internet connection. It ensures your digital life continues when you move into a dead zone. 👤 User Control:  It revolutionizes who controls the data. Empowering users to own their digital footprint, local-first applications are setting a new standard for data sovereignty. ⚡ Superb Performance:  By minimizing reliance on remote servers, local-first apps offer a huge performance increase. It works with you, on your terms, and at your pace. There are downsides 🔄 Data Synchronization Challenges: Ensuring data synchronization across multiple devices involves complex algorithms and increases architectural complexity. 👥 Collaboration Difficulties  Developing efficient and secure collaborative features without relying on a central server to mediate data exchange poses significant technical challenges. 📱 Increased Resource Requirements  Local-first applications demand more storage and processing power from the user's device. It leads to high battery consumption and feasibility on less powerful devices. 🛠️ Complexity in Development and Maintenance  Sophisticated data management, synchronization processes, and security measures increase development and maintenance complexity. 😕 User Experience Trade-offs  Balancing offline functionality with performance and usability leads to user experience challenges like data inconsistency and synchronization delays. There is a future where technology respects user autonomy, enhances privacy, and bridges the digital divide. Are we willing to take on the complexity that comes with it? Google Docs, Figma, and Notion paved the way for us.

    • No alternative text description for this image
  • View organization page for Vella.ai, graphic

    682 followers

    Another great post on #localfirst right on the heels of the awesome interview by Scott Tolinski and Wes Bos at Syntax.fm: https://lnkd.in/g5krmiEa Checkout https://lofi.software to learn more

    View profile for Michael Awad, graphic

    Setting you up for productivity without complex systems

    There's a new movement in software development. It’s called local-first development. Here's why it has the potential to be the next big thing: People are caring more about their digital privacy. Their entire lives revolve around their smartphone, which is the main reason. Another issue arises when moving to mobile: Unreliable connection. You submit a form and get confronted with an endless spinner. Everything you filled in is gone. Recognizable? There are ways to avoid this, but we haven’t resolved the deeper problem. Mobile-first development isn’t enough. We need to rethink our approach to software development. That is where Local-first development comes into play. 🔐 Privacy & Security:  Local-first places priority on safeguarding user data. It keeps it where it belongs, on the client's device. This pivot away from traditional cloud dependency is a technical paradigm shift and takes digital privacy to the next level. 🌐 Offline Capability:  Local-first development allows the freedom of seamless functionality, irrespective of your internet connection. It ensures your digital life continues when you move into a dead zone. 👤 User Control:  It revolutionizes who controls the data. Empowering users to own their digital footprint, local-first applications are setting a new standard for data sovereignty. ⚡ Superb Performance:  By minimizing reliance on remote servers, local-first apps offer a huge performance increase. It works with you, on your terms, and at your pace. There are downsides 🔄 Data Synchronization Challenges: Ensuring data synchronization across multiple devices involves complex algorithms and increases architectural complexity. 👥 Collaboration Difficulties  Developing efficient and secure collaborative features without relying on a central server to mediate data exchange poses significant technical challenges. 📱 Increased Resource Requirements  Local-first applications demand more storage and processing power from the user's device. It leads to high battery consumption and feasibility on less powerful devices. 🛠️ Complexity in Development and Maintenance  Sophisticated data management, synchronization processes, and security measures increase development and maintenance complexity. 😕 User Experience Trade-offs  Balancing offline functionality with performance and usability leads to user experience challenges like data inconsistency and synchronization delays. There is a future where technology respects user autonomy, enhances privacy, and bridges the digital divide. Are we willing to take on the complexity that comes with it? Google Docs, Figma, and Notion paved the way for us.

    • No alternative text description for this image

Similar pages