First Edition of "Advice Nobody Asked Me For" for the Polkadot Ecosystem

Nobody asked for this advice. I’m writing it because I have some free time and, for some strange reason, I’d still like to see Polkadot succeed.

That said, I’m not even sure who I should be addressing here, Parity, W3F, or PCF? I just hope that at least one of the ideas I’m sharing reaches someone who has the ability to make things happen.

Lately, I’ve noticed the same pattern repeating itself with the launch of Polkadot Products Devnet (and, by the way, congratulations on this milestone).

I see new applications being launched. Developers are experimenting. There are already websites where we can discover these apps (which, by the way, reminds me of those directories that used to list every parachain).

But do you know what I don’t see?

The one thing I need to see, as desperately as someone stranded in the desert needs a drop of water.

Real use cases.

The next part is best described as a dream.

In my dream, every app creator has a small community, a handful of followers, or at least that childhood friend who never leaves their side. They show people what their app does, why it’s useful, what makes it special, and how to get the most out of it. They encourage others to experiment. They explain everything, every button, every click, every step of the process.

Then those people go out and do the same for others because the app helped them build something interesting or solve a real problem.

Suddenly, everywhere I look in Web3, people are talking about the incredible things they’re building with Polkadot Products Devnet. Everyone is experimenting because they’re constantly seeing examples from other users who have already shown them exactly what to do.

But wait…

I just woke up.

None of that is happening.

The applications exist. They’re being built.

Yet not even their own creators are telling me what I can actually do with them, what problems they solve, or why I should spend even five minutes trying them.

So I do what most people probably do.

I keep scrolling.

Your thoughts align with mine…
I’m not a programmer—not in the slightest. I’ve been watching people on X who aren’t programmers either, yet they’ve launched small apps on the Devnet using Claude. As far as I can tell, none of the apps have smart contracts yet—which is unusual for crypto. It doesn’t make much sense anyway, since it’s a testnet and no token value is meant to be transferred. You could potentially implement it experimentally using testnet tokens, but what for?
Anyway, after using AI to compose music, create short videos, and write a book, I thought: why not? And sure enough, programming an app turns out to be almost easier than any of the other things. I’ve created two so far.
But now, regarding my thoughts: even if we had thousands of these apps, who would use them? And more importantly, where does the value creation come from? Sure, creation will likely be paid for in DOT later on. But will interest persist once experimenting suddenly costs money? We’ll see.
@lilymendzdev What kind of app do you feel is missing? What would be a genuine use case? And what’s stopping you from bringing the idea to life? It’s actually quite simple.

I’ve been looking through the published dev net apps, as well. On the surface, they’re mostly experiments, placeholders, and existing projects deployed to a new location.

I’ve been playing with a NetHack clone that had existing Asset hub integration and a manual webRTC connection for P2P co-op and trying to add context-aware rails for polkadot app game sessions and event signing. Nothing immediately ‘useful’ but a learning opportunity, nonetheless. Other projects I’ve been toying with may be decidedly more useful, but I’m trying to be more critical of the privacy exposures

My immediate takeaway so far is not that there needs to be a reason to spend tokens, or that there’s a lack of products selling things, but rather the opposite.

I deployed a codebase onto an outwardly facing, accessible network that is able to provide a non-token-holding service without the need to register an email or sign up for anything. And it will stay there as long as I renew the lease. That’s meaningful, although maybe not exciting.

PAS is still needed under the hood, and it seems there’s a lot of new tools which each do something interesting, but there seems to be a purposeful step away from paradigm of needing tokens to interact with the systems as a user.

Perhaps in a way we are so conditioned in the need to buy something, we need to re-appreciate the act of using something. Just my thoughts.

I’m not sure if I’m understanding you correctly, but regarding what I wrote earlier:
Of course, it is excellent—and indeed special—to be able to operate as a user here without a token. That specific Web2-like feel was the goal.
My question concerns the following scenario on Polkadot: As a developer, it ought to be possible to use a paid service that generates value for me, even if the end user doesn’t pay for it directly. Otherwise, I’d be paying for something that offers me no benefit. That isn’t the case with the current apps I’ve looked at. Alternatively, I suppose I could publish apps that provide conventional blockchain applications via smart contracts. I’m not sure how—or if—it’s possible to derive value here without a native token serving as a mechanism for value creation. The ideal scenario would likely be for DOT (or stablecoins) to serve as a universal vehicle for representing any form of value—benefiting the ecosystem through token burning, the developer who receives a share, and the user through smart interaction. In any case, I’m eager to discover the first app that generates value for the creator, appeals to users, and—as a side effect—creates value for Polkadot.

I think I understand your point, that you would be interested in using products which create value for you. That might be monetary value through purchasing or trading, or non-monetary value through a service like facebook/twitter/google maps/whatsapp.

I believe an initial starting point might be in providing alternatives to existing services on Polkadot. Two potential value-generating projects I’ve been tinkering with on Asset Hub are:

Fare - a p2p open DoorDash clone to mitigate trust requirements between customers, venues, and delivery providers. (Please note, currently registering as a venue places GPS coordinates on chain to be publicly available) I’m currently exploring retooling with some of the products shipped with the dev net for better integration and enhanced security (e.g. statement store topic subscriptions for localized order queues instead of per-venue public order logs). I think being able to privately set your own delivery fee rate for cryptographic proof of delivery of food/parcel is valuable, especially if necessary system costs can be minimized.

DATUM - ad network to connect advertisers’ products, on publisher websites, to end users and provide a clear value flow of the advertiser spends to the users. Imagine using a website or application with banner ads or sponsored content, acknowledging that you saw the ad, and receiving compensation for your attention. It acts as an extension of the Brave Rewards model to be controllable and configurable by publishers and users who host and view the content. In theory, a product could generate ad revenue without being a user data harvester or otherwise provide anything other than website which users visit without being filtered through Brave as the global approver.

I might be inclined to use or pay for transaction fees for a product if I knew I was also rewarded for simply visiting that product, i.e. social media/message boards.

It is also possible to monetize systems without directly charging the general public. On my list of things to do is integrating a mock manufacturing execution system/SCADA via Ethernet/IP, CIP, OpenProtocol, Modbus, and OPC. This could be sold to businesses and manufacturers as a service package, annual subscription, or integration support to provide persistent material tracking and quality reporting. In effect, a client with smoldot could become an alternative to a SCADA dashboard system like Ignition or DeltaV which could run either on the public blockchain, or an internally managed system.

I intend to experiment with these ideas further and see how they might fit within the unified environment. I’m not looking to extract maximum value from anything, so if any of these or other services were to pick up traction then a minimal dynamic service fee to cover operating costs may be sufficient. I like the idea of optimizing intangible value of stakeholders rather than maximizing value for stockholders.

Yes, I understand that everything is experimental right now, and that’s exactly the point of my post.

I don’t want us to repeat the same story, a cycle of endless experimentation and launching applications (or, in the past, parachains) without ever building a real user base.

The idea I hope resonates is simple: when the time comes to launch your app, invest time in educating your community. Show them how to use it. Walk them through every feature. Give them a reason to come back.

Don’t expect every potential user to figure it out on their own.

Because the moment they have to leave your app to research how it works, you’ve probably already lost them.

This question wasn’t directed at me, but I’d still like to share my perspective.

Lately, I’ve been thinking about how AI applications have made life much easier for crypto projects. When we use AI products professionally, we consume tokens that we pay for with real money, and we do it without hesitation or complaints because those products solve real problems for us. In return, they help us generate value, whether that’s financial or professional.

So I think the idea that users are unwilling to pay has largely been disproven. People are perfectly willing to pay when they believe a product is genuinely valuable.

In the current crypto landscape, I think the most practical approach is to put stablecoins first because of their massive adoption, while implementing a mechanism (smart contracts, for example) that also benefits the ecosystem’s native token, all without the user even noticing.

To me, that’s where the real opportunity lies.

I also think the key to success is making everything as simple as possible for users. People don’t want unnecessary complexity anymore, they want solutions they can adopt quickly without facing a steep learning curve. After all, that was one of the things that pushed away the first wave of people who came to Polkadot.

I may have drifted a bit from your original question, but I think it’s closely related.

one word. visionaries looking ahead for the next 15 years, I have dev a mobile app that can potentially serve a big market, and compit with the billion $ competitors, and that takes time and huge efforts, we are building it so it doesnt needs much marketing and it is solving real world needs, not trading or texting or NFT distribution.

what is being developed now in polkadot is kids play, simple apps, to develop a full fledged app, well, things can get quite complicated so that is why you can observe this mickey mouse apps popping up with 0 traction. Complicated solutions being able to disrupt the incumbents takes huge amounts of time and $, so if I don’t get any financing for this to be implemented on this network i will go full Web2, and use cryptography only when needed and through channel partners. so Parity and w3f need to get real, and put the $ where is needed, but even that I can not see happening.

What do I have to learn to create apps that solve problems on Polkadot?

Hi CryptoJoe - There’s a quick start guide to developing apps here on the docs website - Quick Start with RevX | Polkadot Developer Docs

Lily is right about what she’s pointing out. Lately Polkadot lacks users who actually want to try the Polkadot App on the Devnet. If you look at it, since Products Devnet launched up to now, there aren’t many applications with real, essential utility. There are a few good ones, but user activity testing them is very low, since it’s really just a handful of us interacting with them.

What I can say from my own perspective is that the barrier to entry for the average developer has come down with the AI era, compared to how complex the ecosystem used to be, from building “on the metal” to signing with Polkadot.js. That’s still essential for certain use cases, but with the Polkadot App that complexity has dropped noticeably. We now have a much friendlier app, both mobile and desktop, and I’ve personally been able to deploy a few applications with Claude’s help from the terminal. Even so, there needs to be an education plan, and that focus should come from both Parity and W3F.

At least in Mexico, we’ve focused since day one on bringing the idea of Polkadot down to the everyday user. One of the barriers that made it hard for people with no blockchain background was the complexity Polkadot had around wallets and the user experience in general. Today, some parachains no longer exist, or aren’t focused on a friendlier public anymore, they’re aimed at people already inside crypto or Web3, and that’s a factor that limits adoption for the ecosystem.

As I mentioned in a post I wrote a few months ago about why users already in crypto will probably never see Polkadot as something worth using (https://x.com/w3nerick/status/2043750189928702463), that ultimately comes down to whether each person wants to try something new or not. Still, Polkadot can absolutely reach new adoption without depending on people already in Web3, but it needs an education plan, both online and in person.

Over the past few years, Spanish-language education in general wasn’t well executed, and that weak point showed up through the parachains, since they were the only ones responsible for building the final product using Polkadot’s technology. Many projects shut down or migrated to Ethereum, and that negativity ended up affecting a lot of things, the token price being a clear example.

Even so, things can still be done right, and that’s exactly what we, at least here in Mexico, want to propose with the idea we have in mind, taking advantage of the Polkadot App and the fact that building is now much easier, without the friction Polkadot had from the start.

If it’s useful context, we recently submitted Ref #1929 along these exact lines, happy to share more details or hear feedback from anyone here.

I have mentioned this before; it comes down to need. However, it also is about proof. This industry as we already know has a bad reputation due to difficulty for all to use and then relevance. Many know this is tied to the token aspect of its nature. It is also different countries are more comfortable exchanging in tokens verse others, so this push pull exists based on where your feet are planted. I am hoping that what is being developed we can get buyin that fulfils the need for these products. I have several need products from real people in real industries that could make lives better, because this should be our goal, right!!! Hopefully after this test net stint, we can get to a place of production ready and work on integration and sales. Milestones have been hit here, even if in some cases my phone blocks entry.

Lily it was lovely getting to meet you in person!!! I hope we come out on the other side of all of this being able to make things better overall for people. Hoping you’re well!

Thank you for writing this. Someone needed to.

You’ve put your finger on the core problem. After ten years here, and three years of TwoPebbles investing in this ecosystem, I’ve reached the same conclusion, and it’s why I’m stepping away.

Apps don’t find real use cases on their own. Solutions become decentralized because of the problems they solve, and getting there takes incubation, guidance, and tracked progress, not just launches and directories. We’ve seen this cycle before: wallets, then a payments app, then paying people to build community. That created incentives, not users. The experienced builders never came, the small able groups we had are gone, and the incubators active seven months ago have produced nothing (concentrating on DeFi and not dicovering new usages for the tech).

The community you dreamed about doesn’t appear by itself. Someone has to help founders find a real problem, a first group of users, and a reason for them to tell others. TwoPebbles proposed exactly that in Referendum 1752: $108K to design an incubator with clear KPIs, including products launched and active users, with unused funds returned. It was rejected with ~31M DOT against 272K for.

So I share your frustration. Until the ecosystem funds the work of turning apps into real use cases, we’ll keep launching things, and people will keep scrolling.

Jose no name