If you want to know what the 2nd generation of frames will support in the future, you should check this out.

This frame supports fully native 3D rendering based on WASM technology in C++.

This means that FC supports a very exciting revolution that the developer community will bring... 

In this experiment, I used C++ and the Qt framework. Build mode is on debug with the least efficiency (only for test concept).

We are still very early... 😎🫡🔥

@dwr.eth  @horsefacts.eth 

https://genyframe.xyz/wasm/qt3d

Nice but I’m starting to get Java applets vibes

Blogger at ribbonfarm.com, running summerofprotocols.com, host of /gloom ☀️

The opportunity is app + reliable mobile crypto transactions + social context + distribution. 

Will be a while before Apple and Google have an OS level crypto wallet. And if you expect users to connect an app on each page, conversion is going to be low.

So now it’s a browser-session-level wallet auth?

Yes. That meets you in an app you're already using daily.

If Apple and Android had seamless wallets would you do frames UX substantially differently 

What’s the thesis statement independent of current practical constraints? Something like an “everything app” a la WeChat and one-time X aspiration (seems to be abandoned)

I think frames would still exist but it would make the value prop less compelling (since opening a normal link in the feed -> browser) would work well enough.