nft-storefront VS iaNFT

In fact, almost every smart contract leverages composability in some way or another. Composability is like those plants or fungi that scientists find to be the size of a city yet also a single organism with the same DNA from end to end (World's biggest plant, humongous fungus). The Flow team's NFTStorefront contract deployed to mainnet address 0x4eb8a10cb9f87357 illustrates this idea well. Let's say you want to host an NFT marketplace in your app. You don't even need to fork and deploy your own version of NFTStorefront to make that happen. You simply integrate into your app the transaction code that processes the buy/sell orders via NFTStorefront. All of the logic of creating and processing orders is taken care of for you via that contract as opposed to having to create your own marketplace contract. A whole ecosystem of smart contracts can use NFTStorefront in this way.

Today on Flow, we can already embed meaningful amounts of metadata and assets inside of an NFT. We can design it so that its content can be useful as a building block when taken to another NFT experience. It’s up to the owner of the NFT to allow other NFT experiences to modify the metadata and add assets. In this sense private composability patterns on Flow are just waiting to be crafted by us builders. With iaNFT, I’m creating tools that will allow us to embed Cadence analogs to the common SVG file format inside of the NFT. The Cadence analogs are serializable to SVG and back to Cadence at any time. What this unlocks is the ability to modify the properties of an SVG like changing its colors, shape or animation. We can also composite the artwork on-chain and do so safely across unrelated NFT projects if we choose. From the iaNFT GitHub repo: