I don’t think an Arena-style open world is out of reach with this engine.With more dev time,a fully embeddable web-native 2.5D RPG feels doable.Using my engine. We could see a wave of boomer shooters/RPGs on the web.
#gamedev #javascript #indiedev #raycaster #2D5D #RPG #FPS #webnative #opensource

Thanks @daniel2color for having @expede & I as part of the IPFS Apps 201 track for #IPFSCamp

I’ll be talking about @FISSIONcodes #Webnative SDK - what works today and where we’re heading with private & encrypted edge apps for everyone https://x.com/daniel2color/status/1580830955727884290

This is hard stuff!

And our expectations from centralized cloud providers and proprietary silos like Google Docs makes us think that this surely must exist.

But it doesn’t. So we’re helping to build it.

Check out @FISSIONcodes and the #webnative stack, get involved!

We're not changing EVERYTHING: we're just sticking a secure identity, file system, and data storage in your browser, in a way that lets user own their data, and developers ship #webnative apps with lots of cool features!

cc @OriPekelman @robertDouglass @expede https://t.co/oa6tNkAqdw

We shipped v1 of the Fission publishing platform a few months later, in Oct 2019, and hackathon participants built a Netlify clone on top of it using their docker build image.

Then we focused on going fully #webnative - identity, storage & compute at the edge, in browser. (...)

Two things are happening:

1) making a TiddlyWiki community app on Fission, so with one click anyone can have a hosted TiddlyWiki -- great for #secondbrain, digital gardens, etc.

2) Integrating #webnative into TiddlyWiki, so people can load/save content anywhere

Starts in 25 minutes, not too late to grab a ticket.

Kick back, pour yourself a beverage, and have @expede walk you through 234 slides of awesome #webnative concepts. https://x.com/FISSIONcodes/status/1352716927710466049

Funny story, for a brief moment this week, it looked like a new user had uploaded 98TB over 3 days.

Nope, that's our new versioning #webnative file system, that would count the storage for every single version. 😅

The new @inkandswitch release of Project Cambria is part of the puzzle of how we can potentially make user data much more portable between #webnative apps, and to allow for forking and remixing of apps.

https://www.inkandswitch.com/cambria.html

Postscript: We're very inspired by the work that @inkandswitch is doing (and @pvh is an advisor to @FISSIONcodes).

Their "Local first software" is very much in line with #webnative

https://www.inkandswitch.com/local-first.html

I'll quote @tmcw again:

> "There was a time when we could install applications, give some sort of explicit agreement that something would run on our computers and use our hardware."

#webnative is more like installing an app.

On native mobile apps (and newer desktop OS as well), users get asked for permission.

By building and executing client side, and adding identity + files into the browser, #webnative can follow this same pattern.

So #webnative: Web native apps are designed to run on the web, taking advantage of all the capabilities your browser has to offer, as well as native, local capabilities like identity, storage, and computation.

I wrote a first post about how @FISSIONcodes thinks about #webnative apps https://blog.fission.codes/intro-web-native-apps/

Here's the blog post on introducing #webnative: https://x.com/FISSIONcodes/status/1313858383943028738

I'll screenshot the part where Kevin describes @figmadesign as "browser-first" and what that means.

Tomorrow, I'm going to introduce you to what @FISSIONcodes means when we talk about #webnative apps. Stay tuned!