Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
[Use case 1]
Artists are not getting paid directly per song (or piece of content) bought.
Piracy. It is easier to download a copy of the album than to purchase it via a 3rd party. Not knowing how much of the money spent purchasing actually goes to the artist and if at all. There isn’t much incentive to directly reward the artist.
Lack of funds to make real art. There isn’t a robust funding or payment system for artists.
[Use case 2]
Saas usage is skyrocketing and internet users are seeing product subscription fatigue.
With many subscriptions to various services it is hard to track how much a month you are spending on cloud services, apps and SaaS in general. This leads to reduced efficiency with regards to your dollar spend's return on value as you might not be utilising the maximum usage based on your chosen subscription tier to the service you are subscribed to or that you would like to use.
[Use Case 1]
Fractional payments for artists. Artists and contributors to the creation of the content or digital item will get rewarded everytime a piece of content gets bought.
Instant transfer of funds to artists and contributors when content is bought (cascading payments) & the reverse (crowd funding).
A world where artists can fund and receive $ for content fairly.
[Use Case 2]
Imagine being able to as a user have access to a pool of applications without having to sign into all of them individually, where you can control data sharing on a granular level + with time permissions and more. Imagine not having to subscribe to services and just be able to 'pay' for exactly what you use.
Now as an app creator or business, imagine now having a new pool of customers to tap on who don't need to sign up for your service as that is solved by another mechanism altogether. Imagine having access to user preferences and other data on day one and them being able to access your SaaS's full suite of features whenever they want to (and 'pay per use', avoiding subscription burnout which equates to lost customers) or on the flipside, being able to only access particular functions when certain criteria are met through the use of creative NFT engineering.
[Use Case 1]
A marketplace where art/songs/content/items can be listed and sold.
Each digital item bought will get contracts executed which will send payments instantly to parties listed as recipients on the contract.
If a recipient has other recipients listed for that digital item, the contract also sends payments for that recipient to the other listed recipients and so forth. This ‘tree-like list of recipients is infinite in nature.
The nature of the payments/actions is much like a rain cascading downwards through the top of the tree to the bottom (roots) and hence is called a cascading payment mechanism.
[Use Case 2]
A SaaS or IOT app gallery that users launch their tasks from which enables pay per use business models as well as creative funding through a sort of crowdfunding for features model, powered by NFTs.
Through Microdosh's AIM (access and identity) system, users can share time-expirable tokens (amongst the many other myriad uses of tokens) of exactly what they want to share (of their entire dataset) to apps as requested and program configurable data rights as they wish. This level of control in a easy to use UI will enable a new slew of thinking in terms of app and business design and empower users with the granular permissions control they deserve. Your profile that you choose to share is an NFT with data and smart contracts embedded into it which interact with the applications involved to a level you are comfortable with and that have full view of. As a user you can terminate the data NFT if so desired from wherever you are remotely.
Through the use of a new kind of database I term the 'single instance database', there is only one instance of a record, with applications calling that record instead of the traditional model whereby multiple instances of an original record are created and then shared with multiple apps or businesses and then are very hard to individually modify when so required amongst all instances. Think of how many address updates you need to give various parties (and the authentication hoops required) when you move homes or offices. Imagine just being able to update a single 'master' record of this instead, with all parties requiring access to this data referencing this master record every time they need that data. It's not the data they need to manage and take care of (hello sensitrve data), it's the bridge instead. As a user you can set it up in a way that you are able to burn that bridge at will.
From a UX perspective, users will just be able to use the entire internet's library of apps without having to sign up, sign in or register to new apps and having to make financial decisions like choosing a subscription tier which adds to the stress of managing internet 'spend'. All users will see, thorugh a UI, exactly how much they are utilising apps through an 'micro expense tracker' for apps and SaaS functions.
Through combining IOT devices like smart doors, users can now pay for one off entry to gyms or spas for example when travelling.
All in all it is just a much better experience for everyone using the internet.
One feature of Microdosh is the ability to create, using a graphic user interface (GUI), tokens and smart contracts. A simple use-case is the concept of a smart will. This smart will can be applied to living persons or entities as well. They can be as simple as bank balance transfers to another account upon completion of a specific deal or variable/parameter-change within a database or be reliant on a multitude of factors programmed into the smart intelligent, living contract, involving IOT sensors and more (think “transfer ½ my wealth to my 10th descendant if country A is not at war with country B in the year 30XX and if earth’s weather is not above 42 degrees so forth and so on”). The immediate scenario is the creation of tokens that can be named and used (perhaps even disposably) for a multitude of scenarios.
An example application that is created with the help of Microdosh’s suite of technologies is PingoPongo, a de-centralised local exchange trading system and community focused bartering exchange, which fosters the growth and discovery of communities around the world (in real life and online). What PingoPongo is, is a showcase to the world that alternate economic systems that are complementary to the current monetary and economic system can positively augment quality of life and form micro-economies (or mega-economies) which are critical to sustained growth.
Humanity is at a critical point in its evolution and Microdosh, PingoPongo and the upcoming systems are here to provide a technological, ideological and socio-economical platform for current and future generations to grow and thrive on.
The ability to incorporate micropayments into an application, SaaS or business provides many benefits for the customer and business. Instead of ‘subscription burnout’ being experienced by heavy users of online services for example, they are now able to access a wider array of applications and/or functions on a ‘pay per use’ basis instead of the tiered subscription model approach. This leads to a phenomenon which we call ‘interface familiarity’ which is basically one where the user of an app becomes accustomed to the basic features of the app and can be nudged to try the more advanced features of the app. This concept can be scaled from app to products and can be applied to real world situations as well things such as Internet-of-Things (IOT) sensors, where the use-case might be as simple as per per use entry to gyms or spas and be as complex as smart car tolls on privately owned roads or estates. With the advent of the metaverse, the possibilities and use-cases can be expanded/extended even further.
By offering your app’s users a chance to experience your app without having to create a new account with you (as they have already logged on into Microdosh’s application store & browser) and have access to all your app or business does using a micropayments model is advantageous. The ability for other apps in the eco-system to share data with your business is also another economy in itself. This is all done of course with full consent from the user/customer in the form of smart privacy contracts that they can revoke at will, if so programmed, at the granular level and also automatically if breaches occur or are detected.