Developers, this talk is for you! In case you missed it, here’s a chance to learn all about card schemas. They are essential, as they define what a card is and its relationships with other cards, plus they allow these cards to move around!
https://youtu.be/xL7opLril_4

Here you have a link to the article: https://medium.com/cardstack/cardstacks-development-frontier-a72d3d73c279

The team are looking into an updated roadmap! The team recognise the need for interoperability between chains and are working on it!

What is a token pool?

In the Cardstack Network, customers will usually deal with more than one service provider. To enable frictionless billing of mutual customers, we use a smart contract called a “reward pool”. This is like waiters pooling their tips by putting them inside a jar. At the end of the night, they determine what portion of this tip jar goes to each person, just like we figure out what portion of this reward should go to each service provider, based on some usage accounting.

To know how much that reward pool is worth, especially when it contains multiple fluctuating tokens, we need Tally—our accountant or bookkeeper. Tally knows which transactions are happening on-chain and can access cryptocurrency-to-fiat exchange rate services, to calculate the current market rate of the reward pool.

Hear more about the token pool: https://youtu.be/FwO_ZGCk410?t=1070

Introducing the Card Makers

Users, developers, engineers, back-end, front-end, with or without framework-level experience—whichever category you fall into, you can play an important role in the Cardstack Ecosystem! By utilizing your individual skills, you can actively contribute to the making of cards, thus to the Card Catalog. The inverse pyramid of card makers tells you how that works. In the next few days, we will introduce each type of card maker, with the corresponding skill sets that are needed in each layer of this pyramid.

Learn more about our pyramid of card makers: https://medium.com/cardstack/who-are-the-card-makers-504f784881fb
Check out our early-access guides: https://docs.cardstack.com/release/

The Product Team

The SDK and APIs provided by the framework team are used by the product team to create experiences—by building environments.

Here’s an analogy: There's a home screen, volume control, and camera on your iPhone, which a developer of an iOS app doesn't have to build from scratch every time, since those are standard environments that already exist. That's what the product team at Cardstack is working on; and we want to grow this team to 100+ people. There are many new things coming (workflows, spaces, libraries, etc.), all of which will be standard. Every single card that is built using the Card SDK benefits from these sharing or zooming controls. Product developers are the ones who build these standard experiences for mobile or desktop, so they’re all part of the product.

Since the Cardstack Framework is built on top of Ember, this layer requires a deeper understanding of the Ember ecosystem.

Learn more:
https://www.youtube.com/watch?v=zrGLmAYYpqQ&t=563s

Front-end engineers

By creating common cards, front-end engineers put front-ends on top of our back-ends. Take an event card, for example. Anyone who wants to build an event catalog can start with the basic event card. Not only does it have all the schema.org language already defined; it also comes with an editing form, because the card is a mini-application. These common cards have built-in dropdowns and design systems, to guarantee a great standard experience for customizing cards.

We use common cards as a starting point to build this decentralized ecosystem, to allow back-end providers, integrations, or even new blockchains (like a calendar or event blockchain) to get into the user experience of the system.

Learn more:
https://www.youtube.com/watch?v=zrGLmAYYpqQ&t=948s

And more from the team

Coming up: The Cardstack Builder! Watch out for our next video, where Chris introduces Cardstack’s unique card building tool. Running on Cardstack Space, it will enable users of all skill levels to make their own cards.

Thank you for the suggestion, the report is supposed to be a round up of development over the last period, any partnerships etc, that are established will of course be announced! Development is of course the most important part of ecosystem growth that can be analysed before main launch!

What is this Githereum? Something like Github but for Daaps? Why people should use this if everyone use Github nowdays (even for blockchain development code and daaps)