# Browsers & SP 2022 Plan

* [Weekly meeting notes, and Q1 goals status](https://hackmd.io/4ZCEejaoSmatn8Vgct_3CQ)

## Browsers

Objective: IPFS is available natively or through an extension in all top tier browsers for reading, publishing, NFTs and archiving (DRI - Dietrich, David)

KR: Chromium has IPFS protocol support, and a build option for enabling an IPFS node, and a Chromium-based browser ships protocol support in a release channel
* Size: Large
* 2022ness: Y
* External: Y (Igalia)
* Metrics
* PR for build option available in Chromium repo
* Build option merged
* A top browser vendor shipped it (in any channel)
* A top browser vendor put it on a roadmap
* (TAM)

KR: IPFS Companion is available in the top two web extension stores using the manifest V3 architecture
* Size: S - M
* 2022ness: Y
* External: N
* Metrics
* Published in Chrome and Mozilla extensions stores

KR: A prototype of a mobile IPFS "light" node (leveraging CARs and Public Gateways) is shipped, solving the battery problem on mobile without compromising trustless nature of content addressing, and also providing an implementation alternative to "need a full IPFS node"
* Size: Large
* 2022ness: Y
* External: Y/N (hire/grant - Fission)
* Metrics
* Spec and compliance test suite
* Implemention available for Swift/Kotlin

KR: A mobile browser ships an option to enable a "light" IPFS node
* Size: M
* 2022ness: Y
* External: Y (Puma, Agregore)
* Metrics
* Number of mobile browsers w/ the feature

KR: A browser ships an IPFS/Filecoin feature to support an NFT use-case
* Size: M
* 2022ness: Y
* External: Y (Brave, Edge)
* Metrics
* They didn't fail in trying because of stuff we did or didn't do

KR: A browser ships a one-click save-web-page-to-IPFS/Filecoin feature
* Size: M
* 2022ness: Y
* External: Y
* Metrics
* GBs stored on Filecoin

KR: A mobile app for handling IPFS protocol redirects. iOS and android (chrome pwa share reciever)
* Size: S
* 2022ness: Y
* External: ?
* Metrics
* Android/iOS app store install metrics

## HTTP Gateways / Browser DX

* Gateway specification and implementation exists such that exposing legacy RPC API at /api/v0 is no longer necessary (think https://github.com/ipfs/go-ipfs/issues/8234 and https://github.com/ipfs/in-web-browsers/issues/180)
* Size: ?
* 2022ness: ?
* External: ?

* IPFS Gateways are a viable option for decentralized distribution of PWAs (think https://github.com/ipfs/go-ipfs/issues/7392 + https://github.com/ipfs/go-ipfs/pull/8074#pullrequestreview-645196768)
* Size: ?
* 2022ness: ?
* External: ?

* Self-hosted IPFS gateway become viable alternative for kv/document-based databases (mongo, redis) (think https://github.com/ipfs/go-ipfs/issues/8234 allowing people to read dag-cbor as dag-json via JS on a web page – fantastic for demos, entry drug for onboarding web2 people into web3 ecosystem)
* Size: ?
* 2022ness: ?
* External: ?

## Standards

* KR: Web3/NFT/crypto companies have a forum, initiated by PL, for working on NFT and dapp technical interoperability issues and at least ten PL collaborator companies actively participate
* Size: L
* 2022ness: Y
* External: Y

* KR: Three companies shipping dapp browsers or launchers, are all using an interoperable dapp manifest
* Size: M
* 2022ness: Y
* External: Y

* KR: Three NFT platforms are using a shared convention for NFT metadata
* Size: M
* 2022ness: Y
* External: Y

## Special Projects

* KR: A draft IPFS architecture for space-based communication and a proof-of-concept implementation built in collaboration with a potential customer
* Size: M
* 2022ness: Y
* External: Y/N

* KR: PL demos a Web3-native mobile device based on an open web and Web3 OS stack, with IPFS built-in (REWRITE)
* Size: L
* 2022ness: Y
* External: Y/N

* KR: A PL collaboration demos a Web3 AR/VR/MR OS stack on an open hardware device
* Size: L
* 2022ness: Y/N
* External: Y