DEV Community: Fortune Nabhel Harmony

Yo! I Built My First Figma Plugin

Fortune Nabhel Harmony — Wed, 20 Nov 2024 08:42:03 +0000

It’s still a bit surreal to me — like, I never actually thought I’d create a Figma plugin. Let me tell you how this whole thing started. So there I was, just scrolling through Twitter, when this tweet caught my eye.

Some guy was going on about how he’d only hire designers who could code. Sigh — Not this debate again! I’ve seen this argument pop up like a million times before.

So I quoted that tweet with my thoughts. Like, honestly? I think it’s such an outdated question, especially now that we’ve got all these AI tools making it easier for creators to actually build stuff. These tools are literally bridging the gap, letting designers do way more than just push pixels.

Man, you wouldn’t believe what happened next! My quote BLEW UP. Comments started flooding in from both sides of the argument.

I tried explaining my point to people — I’m just saying AI and new tools are helping designers build more without needing to be hardcore coders, you know? But nah, people started twisting my words real quick. They thought I was out here saying designers should never code, which wasn’t my point AT ALL!

Then came that one person, you know, the one that gets under your skin? They challenged me — “Have you ever actually built anything using AI?”.

Now, I’m not usually one to do Twitter banters cause I don’t give a f*ck, but something about that comment just hit different. Not because I needed to prove anything to some random internet stranger, but because deep down, I’d always wanted to build something useful for the community outside of client works and I guess this was the push I needed.

Deciding what plugin to build 🤔
Coming up with what plugin to build? That part was actually pretty easy. I had this whole list of things I wanted to build to help with my personal design workflows. But check this — while I was browsing through Figma’s community looking for some resources, I found this plugin that was getting dragged in the comments. Users were going off about bugs, lack of updates, and it was a paid tool too! That’s when it hit me: why not create something similar but make it way better, with more functionality? That’s how Text Bender was born — a tool that lets you curve or bend text however you want.

The building adventure begins 🚀
The actual building part? Whew, that taught me so much about perseverance and the straight-up excitement of creating something from scratch. I started with the design first (obviously), sketching out exactly what I wanted the plugin’s interface to look like — preview area, space for the logo, sliders to control the radius and angle of the curve. I even tried adding some extra features like flipping text vertically or horizontally. But real talk? That flip functionality was being super buggy and complex. Had to strip it back and focus on making the core features actually work first.

Once I got the design locked in, I open VS Code and got to work. I had my AI assistants, Claude and ChatGPT, by my side, plus my engineering background.

If you didn’t know, I’m a first-class Computer Science graduate with solid coding experience 👩🏽‍💻. Yes baby, I will flex that BSc degree cause I worked super hard for it 😏 . On top of that, I also earned a distinction in my MBA, but let’s get back to the story.

Even though it sounds simple in writing, it was low-key super frustrating building this plugin. Like, my CSS would look PERFECT in my browser, but the moment I copied it into Figma’s plugin setup? Everything started breaking! 🫠 . Instead of having a separate file for my CSS I ended up just throwing everything in the HTML file cause honestly? I don’t like stress. The BIGGEST headache? Getting that text to curve right in Figma.

My preview would be looking clean, but hit that “apply” button to paste it in the Figma editor? Text would come out looking all kinds of wrong — skewed, facing backwards, doing everything except what it was supposed to do.

I spent three days just debugging this one thing. But each time something failed, I learned something new (even if I wanted to throw my laptop out the window). When I finally got it working? THE RELIEF!

The Launch Day Jitters 🥶
I ran like 14 different tests just to make sure everything was solid. Checked the curve, the placement, what happened if someone hit cancel — everything. It wasn’t 100% perfect, but you know what? I told myself: “We’re shipping this!”. Submitting the plugin to Figma for review had me NERVOUS. Like, what if they don’t approve it? Made a Twitter post about it too, just putting it out there that I was waiting.

// Detect dark theme var iframe = document.getElementById('tweet-1853490092880617487-136'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1853490092880617487&theme=dark" }

Then, less than 24 hours later — IT GOT APPROVED!🎉

// Detect dark theme var iframe = document.getElementById('tweet-1853842535212536300-577'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1853842535212536300&theme=dark" }

Being the perfectionist I am, I immediately went to test it live and found some tiny bugs. That little voice in my head started screaming “FIX IT NOW!” but I reminded myself that this was just V1. Rome wasn’t built in a day. I can keep improving it over time. Had to take a deep breath, celebrate the Win, and share my plugin on Twitter.

Link to the plugin in figma community

I also created a Youtube Tutorial on how to use the figma plugin.👇

The Takeaway 🤗
Building this whole thing taught me that I can do anything I put my mind to. Looking back, I can say sometimes — Twitter drama can lead to actual growth (who knew?). Now I’m super pumped to build more tools and keep learning along the way. That’s the story of how Text Bender came to be, and trust me, this is just the beginning!

And to that person who asked if I’d ever built anything with AI? Thanks for the motivation, I guess! 😏

I know you’re itching for the twitter drama, catch all the highlights here. Make sure to use the plugin and tag me to your creations. 😉

XOXO Nabhel 🖤

How to Create Custom Plans with “plan.md” in Goose

Fortune Nabhel Harmony — Tue, 19 Nov 2024 23:14:54 +0000

What is Goose?
Goose is a developer agent that enhances software development by automating coding tasks within your terminal or IDE. Guided by your input, it intelligently analyzes your project’s needs, generates the necessary code, and implements changes autonomously. When working with Goose, having a structured way to guide its execution toward specific goals is essential. This is where the plan.md file comes in. A plan.md file allows you to define a customized plan for Goose, using flexible text formatting and the power of Jinja templating to create dynamic, reusable, and goal-oriented plans.

How to Set Up Goose
Before creating your custom plan.md file, you need to set up Goose.

Step1: Fork the Goose and Goose Plugin repositories on GitHub and clone them.

Step2: Install Homebrew — Visit brew.sh and follow the installation steps, or run:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Step3: To install Goose, use pipx. First ensure pipx is installed:

brew install pipx
pipx ensurepath

Step4: Then install Goose:

pipx install goose-ai

Step 5: Start a session — From your terminal, navigate to the directory you’d like to start from and run:

goose session start

Goose works with your preferred LLM. By default, it uses openai as the LLM provider. You'll be prompted to set an API key.

What Are “plan.md”Files?

The plan.md file is a text file that serves as a blueprint for Goose to follow. It consists of two essential components:

A kickoff message that sets the context and overall goal
A structured list of tasks for Goose to execute.

Why Use plan.md file?

Customization:
You can tailor Goose’s actions for specific tasks or projects.
Reusability:
Templates make it easy to reuse and modify plans for similar goals.
Clarity:
Outlining goals and steps ensures better control and predictability.

Creating Your First plan.md File

Let’s say you want Goose to help set up a new design system. Here’s an example of how your plan.md might look:

Your goal is to set up a fresh design system for our app's redesign.

- Create folders for design components (buttons, forms, colors)
- Set up color palette based on brand guidelines
- Create typography styles for headings and body text
- Design basic button components with all states
- Create form elements (inputs, dropdowns)

See those dashes (-) at the start of each line in the tasks? Super important! Goose looks for these to understand what steps it needs to take. To run Goose with this plan:

goose session start --plan plan.md

Using Jinja Templating in Plans
Jinja is a templating engine that allows you to embed variables, loops, and conditionals directly in your text files. With Jinja, you can make plan.md files dynamic and adaptable.

Key Jinja Syntax

Variables: {{ variable }}
Loops: {% for item in list %}...{% endfor %}
Conditionals: {% if condition %}...{% endif %}

Remember our plan.md file, here’s what an enhanced version using jinja templating would look like.

# Design System Setup Plan for {{ brand_name }}

## Goal
Set up a fresh design system for the {{ project_name }} app's redesign.

---

## Steps to Follow

### 1. Create Folders
Organize design components into well-structured folders:
- **Buttons:** Include all button components and their states (default, hover, active, disabled).
- **Forms:** Include inputs, dropdowns, checkboxes, and radio buttons.
- **Colors:** Store primary, secondary, and accent color palettes.

### 2. Set Up Color Palette
Define a consistent color palette adhering to the brand guidelines:
- **Primary Color:** {{ primary_color }} 
- **Secondary Color:** {{ secondary_color }}
- **Accent Colors:** {{ accent_colors | join(", ") }}
- **Neutral Colors:** Add greys, whites, and blacks for backgrounds and borders.
- **Accessibility:** Ensure color contrast meets accessibility standards (WCAG).

### 3. Create Typography Styles
Define text styles for the app:
- **Headings:** {{ heading_styles | join(", ") }} 
- **Body Text:** Include base styles, captions, and links.
- **Font Guidelines:** Use {{ font_family }} with font sizes ranging from {{ font_sizes | join(", ") }}.

### 4. Design Button Components
Design the following button states:
- Default
- Hover
- Active
- Disabled

Ensure all buttons are:
- **Responsive:** Scalable across device sizes.
- **Accessible:** Incorporate clear focus states for keyboard navigation.

### 5. Create Form Elements
Design essential form components:
- Input Fields (default, focused, error)
- Dropdowns (expanded, collapsed)
- Checkboxes and Radio Buttons (checked, unchecked, disabled)
- Submit Buttons (loading, error)

---

## Additional Notes
- Test designs for usability and accessibility before finalizing.

Passing Arguments to Plan
Arguments can be passed into a plan.md file during execution. For example, to make our design system setup plan dynamic and reusable, we use Jinja templating, which allows us to pass arguments that customize the content based on specific projects, brands, or design requirements. By passing different sets of arguments, we can easily generate personalized plans for any redesign or product.

Example: Passing Arguments with Jinja

Define the Data: The first step is to prepare the data you want to pass into the template. This includes values like the brand name, colors, typography styles, and other design-specific details.

{
    "brand_name": "AwesomeApp",
    "project_name": "AwesomeApp Redesign",
    "primary_color": "#3498db",
    "secondary_color": "#2ecc71",
    "accent_colors": ["#e74c3c", "#9b59b6", "#f1c40f"],
    "heading_styles": ["H1 (32px)", "H2 (24px)", "H3 (20px)"],
    "font_family": "Roboto, sans-serif",
    "font_sizes": ["12px", "14px", "16px", "18px", "24px", "32px"],
}

To run Goose with this plan and arguments, you would run the following command:

goose session start --plan plan.md --args brand_name=AwesomeApp,project_name="AwesomeApp Redesign",primary_color="#3498db",secondary_color="#2ecc71",accent_colors="#e74c3c,#9b59b6,#f1c40f",heading_styles="H1 (32px),H2 (24px),H3 (20px)",font_family="Roboto, sans-serif",font_sizes="12px,14px,16px,18px,24px,32px"

Goose will populate the placeholders in plan.md with these values.

# Design System Setup Plan for AwesomeApp

## Goal
Set up a fresh design system for the AwesomeApp Redesign app's redesign.

---

## Steps to Follow

### 1. Create Folders
Organize design components into well-structured folders:
- **Buttons:** Include all button components and their states (default, hover, active, disabled).
- **Forms:** Include inputs, dropdowns, checkboxes, and radio buttons.
- **Colors:** Store primary, secondary, and accent color palettes.

### 2. Set Up Color Palette
Define a consistent color palette adhering to the brand guidelines:
- **Primary Color:** #3498db
- **Secondary Color:** #2ecc71
- **Accent Colors:** #e74c3c, #9b59b6, #f1c40f
- **Neutral Colors:** Add greys, whites, and blacks for backgrounds and borders.
- **Accessibility:** Ensure color contrast meets accessibility standards (WCAG).

### 3. Create Typography Styles
Define text styles for the app:
- **Headings:** 
  - H1 (32px)
  - H2 (24px)
  - H3 (20px)
- **Font Family:** Roboto, sans-serif
- **Font Sizes:** 
  - 12px
  - 14px
  - 16px
  - 18px
  - 24px
  - 32px

### 4. Design Button Components
Design the following button states:
- Default
- Hover
- Active
- Disabled

Ensure all buttons are:
- **Responsive:** Scalable across device sizes.
- **Accessible:** Incorporate clear focus states for keyboard navigation.

### 5. Create Form Elements
Design essential form components:
- Input Fields (default, focused, error)
- Dropdowns (expanded, collapsed)
- Checkboxes and Radio Buttons (checked, unchecked, disabled)
- Submit Buttons (loading, error)

---

## Additional Notes
- Test designs for usability and accessibility before finalizing.

Best Practices and Tips

Define Clear Goals: Ensure each plan starts with a clear objective.
Use Reusable Templates: Create general templates that can be customized for different projects.
Document Assumptions: Add comments or notes to explain placeholders and structure.
Test Small Changes: Validate each change in the plan.md file to ensure correct rendering.

Conclusion
The plan.md file is a versatile tool for guiding Goose's execution in achieving your goals. By combining clear objectives, structured steps, and dynamic Jinja templating, you can create reusable and highly customizable plans. Whether you're improving a mobile app's UX or tackling a complex project, plan.md empowers you to provide clarity, adaptability, and precision to Goose.

My Hacktoberfest Experience Contributing to TBD

Fortune Nabhel Harmony — Sat, 26 Oct 2024 13:08:31 +0000

You know that feeling when something seems completely out of reach?. That's exactly how I felt about open source for the longest time. Every time someone mentioned "open source contributions," my mind would immediately jump to scenes of developers hunched over their keyboards, typing away in different programming languages. I use to think, "Open source is mainly for developers" - because let's face it, contributing to open source as a designer isn't clear cut as it is for a developer 🫠.

The Day I Decided to Jump In 🤾‍♂️

Here's the thing about comfort zones - they're comfortable until they start feeling like cages. One day, I found myself thinking, "What if?" What if I could contribute to open source as a designer? Instead of just wondering, I decided to do something about it.

I opened GitHub (feeling a bit like a tourist in a tech city) and typed in probably the most straightforward search term ever: "designer needed." 🤣

Little did I know that this simple search would lead me down such an interesting path. As I was scrolling through the results (and trying to make sense of all the technical jargon), I spotted something that caught my eye - a tag labeled "Hacktoberfest." I'll be honest, my first thought was, "Is this some kind of tech-themed Halloween party?". A quick Google search later, and I found myself on the Hacktoberfest website, absolutely intrigued by what I was seeing.

Discovering TBD 👀

After signing up for Hacktoberfest and linking my GitHub account (feeling pretty tech-savvy at this point), I went back to searching, this time with a bit more purpose and using the hacktoberfest tag. While I was initially hunting for design-related issues - you know, my comfort zone - I stumbled upon an opened issue on TBD with the following tags: good-first-issue, hacktoberfest, no-code, small. This piqued my curiosity, so I clicked to learn more.

I discovered this incredibly well-documented issue on TBD. Sure, it was about fixing some typos - not exactly the design work I had imagined - but something about the way they had laid out their documentation made me think, "Hey, I could actually do this!". 😏

From the moment I opened their repository, it was clear that this team had put serious thought into making newcomers feel welcomed. Their documentation wasn't just good; it was like having a friendly guide holding your hand through every step of the process.

The Technical Adventure Begins 👩🏽‍💻

Now, this is where things got real. The project guidelines mentioned installing things like Node.js and pnpm - words that honestly sounded more like keyboard smashes than actual tools at first 🙁. But here's what I've learned, sometimes the best way to grow is to embrace feeling completely out of your depth.

When I hit a wall trying to install pnpm, I swallowed my pride of always wanting to figure out things myself and reached out to my friend who is a front-end developer.

You should have seen me trying to explain what I was doing - "So, there's this thing called Hacktoberfest, and I'm trying to fix a typo, but first I need to install something that sounds like it's missing some vowels…🤦‍♀️" Thankfully, he was patient enough to guide me through the terminal commands, explaining each step as we went along.

My First Pull Request 🤭

Imagine designing in Figma with everyone in the company you work at, including your boss, watching your every move. That's exactly the level of nervousness I felt.

I must have triple-checked every step: creating a new branch (which felt like starting a new design project, but with VS code), making my edits (finally, something familiar!), and documenting my changes. I Submitted my request but forgot to fill out the description 😥.

But here's the beautiful part of this story - the TBD team. They weren't just nice; they were incredibly supportive in a way that made me feel like I belonged there.

They'd send messages that felt less like technical feedback and more like friendly guidance. It was like having a team of mentors who genuinely wanted to see me succeed.

What started as a simple typo fix turned into a genuine connection with the TBD project. After my first pull request was merged, I found myself coming back to their repository, looking for more ways to contribute. The confidence I gained from that first experience led me to take on more issues.

The TBD Community 💛

There was this moment that really stuck with me. Another contributor tried to take on the issue I was working on. I felt a flutter of panic when I checked their profile and saw they were an experienced developer with a solid track record in open source contributions.

You know, the "oh no, someone more experienced is going to do this task" kind of feeling😞. Instead of letting it become awkward, the community manager stepped in with such grace to help clarify everything.

It wasn't just about managing contributions; it was about making sure everyone, especially newcomers like me, had a fair shot at participating. Additionally, the TBD maintainers made every contribution feel valuable. It wasn't just about the fixes; it was about making people feel seen and appreciated for their efforts.

No matter how small, they didn't just merge pull requests; they took the time to thank contributors and even offer to help guide you if you're stuck or have questions.

My Hacktoberfest Badges 🎖️

Contributing to Hacktoberfest 2024 had five unique holopin badges, each awarded for registering and successfully merging 4 pull request. I proudly collected all five, adding them to my Github profile. Each one represents a significant milestone in my journey - from my initial nervous pull request to confidently submitting my fourth contribution.

Now, as I look at my complete collection, I feel a profound sense of pride. These badges aren't mere participation trophies; they are symbols of real contributions, valuable lessons learned, and personal growth.

The Plot Twist 😎

What started as an attempt to contribute design work to open source ended up teaching me so much more. Yes, I'm still a designer at heart - my UX/UI skills aren't going anywhere. But now I have this whole new set of skills and knowledge that makes me feel like I'm part of something bigger.

While I've tried contributing to other open-source projects since then, my experience with TBD holds a special place in my heart. It's like that first great teacher you had in school who made you believe you could do anything - they didn't just teach me about contributing to open source and Web5; they showed me that the tech world has room for everyone, including designers who are just crazy enough to try something new.

To the TBD team - "Saranghae", thank you for making my Hacktoberfest experience unforgettable 🫶🏽.

To all the designers out there who think open source is not for them - trust me, I've been there. Sometimes the best design contributions come from simply being brave enough to step into unfamiliar territory. Who knows? You might just find yourself loving the command line (okay, maybe "loving" is a strong word, but you'll definitely stop fearing it) 😉.

And remember, every expert was once a beginner who was just curious enough to try something new. Even if that something new involves occasionally having to ask what "pnpm" stands for 😁.

This is a submission for the 2024 Hacktoberfest Writing challenge: Contributor Experience

Understanding Web5: Your Guide to the Decentralized Web

Fortune Nabhel Harmony — Sun, 13 Oct 2024 14:30:19 +0000

Evolution of the Web

The way by which people interact with digital content is very different in each of the phases of web evolution.

Web 1.0 - also known as the Static Web started in the early 1990s. When web 1.0 was in the fold, it involved static HTML pages with very little interactivity - users were not participating on a large scale; they could only engage passively by viewing content but interacted less. Older platforms like Geocities and directory services such as Yahoo! are key examples of the web 1.0 era which offered very simple websites with basic navigation.

Web 2.0 - also called the Social Web was introduced 2004; propelled the concept of consumer-generated content and interactive websites with social media sites such as Facebook, YouTube & Twitter as the pioneers. This time heralded a move toward an ownership-driven digital culture that valued personal creation and online socializing with the advent of new models for human connection, sharing information, or collaborating on creative projects.

Web 3.0 - also referred to as the decentralized web began in the early 2020s. Leveraging blockchain technology, web3 allows peer to peer interactions and reduces the need for intermediaries. The shift in paradigm has given rise to decentralized finance (DeFi) applications, where Ethereum-based platforms conduct a range of financial transactions removing the need for intermediaries so users can benefit from superior control and transparency over their digital assets.

What is Web5?

Web5 is a decentralized platform and was built by TBD, a Bitcoin arm of Block (formerly Square) under Jack Dorsey's leadership. Web5 aims to address concerns related to privacy and data ownership.

Web5 is considered a combination of the centralized web where applications are owned by companies (Web 2.0 ) and the decentralized web built based on blockchain (web 3.0).

Key Components of Web5

1. Decentralized Identifiers (DIDs)

Decentralized Identifiers (DIDs) are a new type of identifier that enables verifiable, self-sovereign digital identity. Unlike regular IDs like email addresses or social media accounts that are created and maintained by third-parties like government bodies or tech companies, DIDs belong entirely to the user. The decentralized nature of DIDs not only increases privacy, security and control but also grants individuals the power to take charge of their identity across services without ceding that authority to a single entity.

Beneifts of Dencentralized Identifiers (DIDs)

User Control: DIDs eliminate the need for multiple logins or accounts by giving users the ability to manage their identity across various platforms.
Privacy and Security: DIDs do not require central databases to manage them, users can maintain their privacy and lower the risk of identity theft and data breaches.
Interoperability: DIDs can be used across various applications and services, making it easier for users to interact online without being tied to a single provider.

2. Decentralized Web Nodes (DWNs)

A Decentralized Web Node (DWN) is a robust data storage and message relay system. It enables entities to efficiently access public and private permissioned data linked to a specific Decentralized Identifier (DID). DWNs facilitate safe and smooth user-application communication by employing a decentralized architecture. This guarantees accurate data retrieval that is pertinent to the context. DWNs also improve data interoperability between different platforms, giving users more control over their data and promoting a more robust, user-focused digital ecosystem.

Significance of Decentralized Web Nodes (DWNs)

Data Sovereignty: Users retain complete control over their data, determining who can access it, thereby ensuring robust privacy and security.
Reduced Risk of Data Loss: With data distributed across multiple sources, the risk of loss from server failures or cyberattacks is significantly reduced.

3. Verifiable Credentials

Verifiable Credentials (VCs) are secure, digital statements issued by one party about another, which can be verified using cryptographic techniques. They enable trusted claims, such as confirming a person's identity or qualifications. For instance, a university could issue a VC to a graduate certifying their degree, and this credential can be instantly validated by others without needing intermediaries. VCs offer a more reliable and efficient way to verify information, providing stronger security and privacy compared to traditional credentials like paper certificates.

Improtance of Verifiable Credentials (VCs)

Trust and Authenticity: Verifiable credentials enable users to authenticate their identity or qualifications without disclosing sensitive information.
Reduced Fraud: The use of cryptographic verification makes it difficult to forge credentials, effectively minimizing identity fraud and enhancing trust in online interactions.

4. Self-Sovereign Identity (SSI)

Self-Sovereign Identity (SSI) is a decentralized system of digital identity management that enables the users to control their own personal data rather than depending on an intermediary (like Facebook, Google etc). This approach removes the requirement for third-party validation systems, allowing individuals to control and provide their personal accreditation directly using blockchains or distributed ledger technology.

Benefits of Self-Sovereign Identity (SSI)

Empowerment: Users have full ownership of their personal data, choosing what to share and with whom, significantly reducing dependence on external parties for trust.
Accessibility: Self-sovereign identities simplify authentication across platforms, enabling seamless access to services without the complexity of handling multiple credentials.

Why is Web5 Important?

Empowering Users with Data Ownership: Instead of big tech companies controlling and owning user data (as it is today in the web 2.0 world) Web5 intends to give users full control to store their data in what is known as "Decentralized Web Nodes". This in turn provides independence from third-parties that own, trade and make malicious use of data over which a user will have full rights to controlling it's usage for his/her privacy.
Self-Sovereign Identity: One key feature of Web5 is its emphasis on self-sovereign identity, allowing users to maintain a single identity across multiple applications. This also eliminates having to log in separately on various applications, providing a consistent experience across devices. By removing the dependency on third-party services like Facebook or Google for authentication, web5 not only makes it much more secure but also gives the control back to you the user. Imagine your own decentralized passport, a mobile ID that is accepted wherever you go on the web and where no one takes custody of your credentials for staying online.
Decentralized and Private Applications: Web5 aims to change the role of user data in applications by doing away with centralized servers entirely. Because of the decentralized architecture of this model and the distributed ownership of the data across a network, every user has complete autonomy over their own personal data. Instead of apps accessing or storing data automatically, users ensure that their privacy is always protected by granting permission to apps only when needed.
Reducing Reliance on Intermediaries: The modern Internet is dominated by intermediaries such as social media platforms, cloud providers and technology giants that act as gatekeepers to data and identity. Web5 is aiming to shake up this industry, bypassing these middlemen so users can take more control over their personal data and actions online. This system is decentralized, which increases individuals' sovereignty in the digital sphere and enhances privacy while also making censorship more difficult.

Use cases of Web5

Web5 drives several use-cases including digital identity management, facilitating secured peer-to-peer transactions, enabling decentralized applications (dApps), reinforcing data privacy and ownership whilst simplifying online interactions across platforms.

Digital Wallets: Web5 can enable users to control their digital wallet, which securely stores all of an individual's decentralized identifiers and personal data. Users are given full control over their identity and other information using this digital wallet, making it possible for seamless transactions between various platforms.
Data Privacy: Applications in the Web5 framework can request specific access to users decentralized data stores rather than relying on central servers. In doing so, this method guarantees the user protection of private data and control over their personal information thereby reducing dependencies that can lead to potential data breaches or misuse.
Simplified Logins: Web5 facilitates simplified login processes by allowing users to authenticate themselves with their decentralized identity (DID). This eliminates the need for traditional sign-up methods, such as email or social media logins, streamlining access to applications while enhancing security and user experience.

Conclusion

Web5 marks a giant leap in the evolution of the internet, focusing on decentralization and user empowerment to revolutionize digital interactions through owning data with self-sovereign identity & privacy. Web5 allows users to re-establish control over their digital identities, promoting an environment that is both safe and transparent for all while user-centric features such as self-sovereign identity becomes possible. Yet the adoption of Web5 faces a future that combines promise with uncertainty: how far and when it will be embraced by society is difficult to forecast, given challenges in terms of regulatory frameworks (laws), popular awareness,and infrastructure readiness. Its course will be decided by the education of users, and how much old-tech heavyweights react to what is possible digitally now - in that sense it could reshape everyone's interactions on web or mobile with profound impact upon digital freedom for end-users.