<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Zed Labs - Medium]]></title>
        <description><![CDATA[Zed works with blockchain companies to build out their mobile software while also maintaining their own products put out into the market. - Medium]]></description>
        <link>https://medium.com/alice-dapp?source=rss----c6a649507552---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Zed Labs - Medium</title>
            <link>https://medium.com/alice-dapp?source=rss----c6a649507552---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:37:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/alice-dapp" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How a Consensys Grant blessed our Alice journey]]></title>
            <link>https://medium.com/alice-dapp/how-a-consensys-grant-blessed-our-alice-journey-9c717b37cd99?source=rss----c6a649507552---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c717b37cd99</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[consensys]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[super-apps]]></category>
            <dc:creator><![CDATA[Mark Pereira]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 01:17:44 GMT</pubDate>
            <atom:updated>2020-04-20T20:28:36.151Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a ConsenSys Grant blessed our Alice journey</h3><p>A summary of our ConsenSys Grants journey.</p><p>Our journey into the ConsenSys Grants program started in ETHBerlin upon being referred to Dani Osorio and Scott Moore from the ConsenSys Grants team. A few conversations and e-mails later found us talking to a few members in the ConsenSys Network to evaluate our tech. We had the privilege of talking to Michael Godsey of Infura and then went into a final interview with the ConsenSys Grants team. Overall was super anticipatory but the absolute icing on the cake was going to Devcon V in Japan. 👇📸😁</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4PY0SFMRhRUUQsuV9qTaw.jpeg" /><figcaption>The Alice Team - Hao Fu and Mark Pereira 🔥</figcaption></figure><h3>Grants announcement at DevCon 5</h3><p>Why was this the icing on the cake? Unbeknownst to us this is where the reveal of the ConsenSys grantees was unveiled and we were rubbing shoulders with some of our most respected peers in the Ethereum ecosystem!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqmmoxTRXC0u696s19NxLw.png" /><figcaption>Devcon 5 Grant receivers — Alice, Sigma Prime</figcaption></figure><h3>How do we think we got in?</h3><p>We’ve been hard at work on Alice since May 2019. Almost a year now!<br>Always at the helm of our vision is how can we bring more mobile apps and users into the Ethereum ecosystem. This is for us a super crucial pain point for the ecosystem because more users are on mobile platforms. We believe our unique solution, and how we’ve cleverly engineered Alice to be as open to developers and users as possible, is what got us in. Apparently Mr. Lubin really liked the “Mobile App Store for Ethereum” vision.</p><h3>TLDR;</h3><p>Below we will state the milestones we were chasing with Alice, that thanks to the ConsenSys Grant we were able to smash</p><h3>Our Journey</h3><p>Upon receiving the grant we had these tasks to complete. These are goals we’ve been working super hard at completing but because we’ve been bootstrapping Alice. It’s been hard balancing external work and Alice at the same time. ConsenSys allowed us unaltered, complete focus on these visions. We set forth with Functional and Aspirational Milestones.</p><h3>Functional Milestones</h3><h4>1. Get Alice on the Apple App store</h4><p>Due to organizational and legal costs we were struggling to get Alice on the App Store. This was our most important milestone to date as people were skeptical. ConsenSys Grants helped us get there, Alice is available on the App Store! Check it out <a href="https://apps.apple.com/au/app/alice-browser/id1472818028">https://apps.apple.com/au/app/alice-browser/id1472818028</a></p><h4>2. Have at least 2 functioning mini dapps using Alice’s SDK on launch in the App Store.</h4><p>We have built out 4 mini apps in Alice, 1 is fully functional however the next 3 are still in development. If you’re looking to build games and mini apps in Alice give us a shout. We’ve got some fun apps to build :) Think “Tinder for Cryptokitties” kind of fun 😻</p><h4>3. Add a full featured user’s wallet so that he can manage his digital assets across multiple accounts</h4><p>To be able to utilize some of the most crucial features that blockchains offer we’ve listed out these features in high priority.</p><p>Via public addresses and ENS usernames: -<br>- A user can send and receive ETH and ERC-20s.<br>- A user can view the details of his NFTs.<br>- A user can send and receive NFTs.<br>- A user can view the prices of his assets in multiple country’s currencies.<br>- A user can switch his addresses derived from his mnemonic phrase.</p><p>We were able to complete all these features and for the mainnet and test networks!</p><h3>Aspirational Milestones</h3><h4>1. Create a fully functional Android application, which would be on par with the iOS application</h4><p>We have had resounding success getting our Android app to where it is at the moment. It is not on par but definitely on the way to being completed this year!</p><h4>2. Acquire 1000+ weekly active users</h4><p>A key result of this Aspirational Milestone was listed as “A good tweet from Vitalik”. We are still hunting these aspirations and are determined to get there. Along the way we’ve picked up a few dedicated fans of the Alice app.</p><h4>3. Add multiple blockchain support.</h4><p>This was one of our biggest aspirational achievements. We are now able to support multiple blockchain transactions because of our integrations with Trust Wallet’s WalletCore. At the moment we support Ethereum, Bitcoin, and Binance’s blockchain.</p><h3>How ConsenSys Grant helped us reach these goals</h3><p>To keep Alice ticking we’re bootstrapping the company and product. So when we’re not hustling, we’re building and when we’re not building, we’re BUIDLing. So any opportunity for us to gain some funds and fully focus on the product is a win! <strong>The ConsenSys Grant was a big win!</strong> We not only got awesome connections, great publicity, validity, and advice from the ConsenSys Network throughout the process but we were able to take a break from external hustles to focus full time on development and build a marketing team to help get the product out there.</p><p>So far the support and feedback on Alice has been incredible. We haven’t done any marketing and are super excited for this next marketing push as we rebrand and do an official launch campaign for the Wallet.</p><p>If we were to do it differently we would have definitely used more of the ConsenSys Network to get more feedback and eyes on the product but we definitely feel like we haven’t utilised this opportunity yet. We’re super excited to launch it into a network such as ConsenSys’.</p><h3>Our contribution — let’s get Ethereum into mobile</h3><p>Our contribution is helping to get the Ethereum network into mobile. We have created a boilerplate for Ethereum dapps that want to build out a mobile app that utilizes the Ethereum blockchain and has it’s own wallet. We also fully support all networks, mainnet, rinkeby, ropsten, kovan, goerli, and custom RPCs for EVM compatible chains. It’s a mobile developer’s dream!</p><p>We’ve been extremely blessed to have received this opportunity through ConsenSys Grants our journey has just started but we are extremely excited for this year as we will now start to push Alice into the Ether!</p><p>Huge thank you to the entire ConsenSys Grants team and for ConsenSys support throughout our journey in Ethereum!</p><p>Forward Ever! ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c717b37cd99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alice-dapp/how-a-consensys-grant-blessed-our-alice-journey-9c717b37cd99">How a Consensys Grant blessed our Alice journey</a> was originally published in <a href="https://medium.com/alice-dapp">Zed Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alice’s Technical Proposal]]></title>
            <link>https://medium.com/alice-dapp/alices-technical-proposal-532143f1a589?source=rss----c6a649507552---4</link>
            <guid isPermaLink="false">https://medium.com/p/532143f1a589</guid>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[super-apps]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Mark Pereira]]></dc:creator>
            <pubDate>Thu, 02 May 2019 23:26:20 GMT</pubDate>
            <atom:updated>2019-09-08T18:08:27.984Z</atom:updated>
            <content:encoded><![CDATA[<p>TLDR; we’re changing the world as we know it.</p><p>How are we going to build crypto super apps?</p><p>On the road to a better <strong>User Experience</strong> there are a few hurdles to get over, and processes to iron out but we’ll go over a few major ones.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tp8hWFLtpoJ28sGoRXVE2Q.png" /><figcaption>An overview of our architecture</figcaption></figure><h4>React Native Mini Dapps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uf8SF_qrlNL43EMrS8shYw.png" /><figcaption>Mini dapps on top of the Alice architecture</figcaption></figure><p>Through a survey we’ve identified that 70% of cryptocurrency applications are written in React. To make the transition from web to mobile as easy as possible, and to prove the theory that mobile is where companies should focus their attention. We are making it super easy for companies to move most of their React application’s logic into a mobile app. Then the focus would be on bringing an engaging mobile experience through their interface (front-end) code as the view elements for React Native are different from the React html elements. <br>Also, what’s the added benefit of building your app in React Native? Build it once and it runs on both iOS and Android.</p><h4>Building your app into Alice</h4><p>The model we are focused on in the beginning is working closely with the first applications wanting to build into our platform so they are shipped with the release of Alice. This is so that while building out our SDK, we can work closely with developers to address their pain points and needs so that the next wave of developers can have as painless an experience as possible. To start off building into Alice, fork our repo in github then start building your app into the /Apps folder. Submit your pull request, we’ll review it, then we’ll push it to our App. We’re also working on some magic open sauce (source) code that doesn’t require the app to update in the app store to add mini dapps to a user’s phone.</p><p>3 main things are required to make the platform fully open:</p><ol><li>A distribution mechanism for applications building mini dapps so that they don’t ship with the Alice app but a user can choose to download it.</li><li>An Alice SDK which has the basic features needed for a mobile crypto app.</li><li>A fully functioning mobile wallet for iOS and Android.</li></ol><h4>Alice SDK</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bDKrCi612n4L8lAzRtS7og.png" /><figcaption>Our Alice SDK overview</figcaption></figure><p>If you’ve built a <strong>crypto</strong> app in React Native, you’re probably bald by now. It becomes extremely painful. As you can probably tell, I stopped before I tore all my hair out. But we’ve got the <a href="https://www.rogaine.com/">rogaine</a> you’ve been waiting for. (The stuff Elon Musk used). <strong>The Alice SDK.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*q6su2SDSzHfuPlXdTLnUUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*lOQjzS_tkAbreaRDIIrxKw.png" /></figure><p>In the Alice SDK, we’re building out a react-native-web3 library that bridges javascript code to native crypto threads. Avoiding all the hacky, React Native architectures out there and adding a painless, more secure solution for mobile development. This means that applications can build their apps using React Native without the stress of having to build out the entire wallet architecture for their apps or have to worry about building out complicated crypto libraries. You’re welcome.</p><p>There are many other components to the Alice SDK which developers will be able to access to bring super engaging, mobile experiences to their users. These come in the form of : —</p><ul><li>React Native Web3 Bridge</li><li>Camera Access</li><li>Push Notifications</li><li>Location features</li><li>Smart Contract Wallets</li><li>Layer 2 networks</li><li>More to come…</li></ul><p>Yes, for both iOS and Android!</p><h4>iOS / Android Wallet</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pn0GhW8NoQvZgIU_yQQkkQ.png" /><figcaption>An Android / iOS native wallet to build atop</figcaption></figure><p>We will be building out our wallet in native iOS and Android codebases (iOS: Swift/Objective-C, Android: Kotlin/Java).</p><p>This is because of 3 main reasons:</p><ol><li>Performance</li><li>Security</li><li>Access to mobile features and extensions offered by iOS and Android</li></ol><p><strong><em>Performance</em></strong></p><p>If we want this app to truly be a super app we have to maximize performance wherever we can. To push the app to the extremes in both the first world’s demand for innovative bleeding edge features, this is needed. To have this app run on low end smartphone devices which are performance poor, to access the people who need it the most, this is needed.</p><p><strong><em>Security</em></strong></p><p>If we want developers to roam freely with their React Native code, there needs to be a decoupling of interface level code from code prompting users to sign messages, send transactions or interface with smart contracts. We also want user’s to feel as secure as possible by utilising the secure enclaves that exist within smartphones.</p><p><strong><em>Access to mobile features</em></strong></p><p>This is the part where as a company we would love to become super creative. At ETHDenver, Franky Aguilar and myself built out an iMessage extension app called BattleBombers. The idea was to start expanding crypto wallets’ capabilities into native mobile features. This opened up whole new ideas for us to explore within Alice as we progress. Imagine NFC payments, payments from your smart watch, ERC721 tokens in your Apple Wallet, iMessage games, iMessage payments, widgets in Android.</p><p>We understand this is no easy task but nothing worth building ever is. Hence, this article was written to open a dialogue between myself and developers in the space to totally envision the product. So please, comment, highlight, poke holes, add criticisms, add valuable insights or even help contribute snippets of code to our <a href="https://github.com/alicedapp/alice">github</a> repo! I hope this article finds interested people and I’m so excited to continue building out Alice with all of you. <br>You can also reach me or Alice at:</p><p>telegram: <a href="https://t.me/markper">@markper </a><br>twitter: <a href="https://twitter.com/markpereir">@markpereir</a><br><a href="https://twitter.com/heyaliceapp">@heyaliceapp</a><br><a href="https://www.alicedapp.com/">alicedapp.com</a><br><a href="https://github.com/alicedapp/alice">Github</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532143f1a589" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alice-dapp/alices-technical-proposal-532143f1a589">Alice’s Technical Proposal</a> was originally published in <a href="https://medium.com/alice-dapp">Zed Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crypto #Superapp UX — Preparing for Mass User Adoption]]></title>
            <link>https://medium.com/alice-dapp/crypto-superapp-ux-preparing-for-mass-user-adoption-908769976ec5?source=rss----c6a649507552---4</link>
            <guid isPermaLink="false">https://medium.com/p/908769976ec5</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[super-apps]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Daniel Bar 丹尼尔‍]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 04:44:07 GMT</pubDate>
            <atom:updated>2019-04-29T04:44:06.939Z</atom:updated>
            <content:encoded><![CDATA[<h3>Crypto #Superapp UX — Preparing for Mass User Adoption</h3><p>This post is based on a talk I’ve recently gave in <a href="http://edcon.io/">EDCON</a> 2019 Sydney.</p><h3>UX in digital native environments</h3><p>Today, if people want to try out a crypto application, or how the cool kids call it dapp (decentralized application). The typical user journey goes along the following lines:</p><ol><li><strong>KYC: Know Your Customer — </strong>A person needs to verify their identity to a 3rd party cryptocurrency exchange provider using a government issued documents such as a passport or a drivers license. Most times they would also be required to provide a copy of a utility bill or their bank statement displaying both the matching names as well as the place of residence.</li><li><strong>Fiat to Crypto:</strong> After the person’s chosen exchange has processed the KYC of step 1 (which quite often takes a few business days), the person would typically transfer central bank issued currency from their nominated legacy bank account to their exchange account, only then will they be able to exchange bank currency into cryptocurrency (e.g. ETH ).</li><li><strong>Web3 browsing: </strong>Once steps 1 and 2 are completed, the persistent and diligent person can prepare their browser (e.g. <a href="https://www.mozilla.org/en-US/firefox/">Firefox</a>) to include a web3 browsing extension such as <a href="http://metamask.io/">Metamask</a>.</li></ol><p>All the cumbersome steps above are merely to prepare the environment so that one can ‘play’ with web3 supported dapps. Once All this is completed, they can proceed to the magical decentralized world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iKAnkQtTUrU4h2c4hrn1xA.png" /><figcaption>Typical onboarding journey: 1. KYC with crypto exchange 2. Transfer fiat and exchange to cryptocurrency 3. Install browser extension to be able to use web dapps.</figcaption></figure><p>But hang on, all that was done so that we can use this dashboard? I mean, it’s nice, but, this is 2019 and it’s way too painful and complex, it’s hard to actually envision mass user adoption of decentalized web at this state. And this <a href="https://medium.com/u/2c93ae43ac7a">Radar Relay</a> dashboard is pretty much state of the art product in today’s crypto environment.</p><p>Now, many entrepreneurs are making an effort to move from web to mobile as people carry their phones with them and use them for many applications in life. But, here’s how many things look like for dapps on mobile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2e5GkI4SwAFieMdwoJjywg.png" /><figcaption>Left: <a href="http://localethereum.com/">LocalEthereum</a>’s trades list screen. Right: Radar Relay not supported on mobile.</figcaption></figure><p>One of today’s most used dapps is <a href="http://localethereum.com/">Localethereum</a>. <a href="https://www.altcointrading.net/localethereum-venezuela-crypto/">Localethereum is supporting Venezuelans</a> in their struggle with the country’s hyperinflation by facilitating peer to peer fiat to crypto trades (shout out to <a href="https://twitter.com/LocalEthereum">Michael Foster and the LE team</a>). However, LE’s mostly suitable for use on a web3 supported browser rather than on a mobile at this point, and this particular use case is screaming for a mobile native experience as many people need in person cash transactions. The other example shown in the image above is the decentralized exchange (DEX) Radar Relay which is not even supported on mobile. Basically, the current level of dapps from product and UX perspective is really really primitive. This is a problem which goes beyond only affecting the entrepreneurs who are dedicating their best years to provide those services, <strong>it hinders the industry as a whole!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txW7TfKJ7HYD0q8X44_LdA.png" /><figcaption>💩 user experience 😿</figcaption></figure><p>OK, now we are on the same page, the state of the industry is really nascent, we’re still at an infantile stage of the industry, but lets understand how can we change the narrative and make progress.</p><h3>Lets take a step back, where do we actually live?</h3><p>As UX people, often when we prepare for product design, wire-frames and all the backstage jazz we start with the question of: where do your early adopters ‘live’, where do they spend their time? When I asked that question to many of my friends the answers range from: Berlin and Toronto to Shenzhen, Sydney and Wellington, but, with taking into account how much time we’re spending using our mobile phones and other computing devices, I’d argue we’re already living as digital species in the cyberspace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tfW_w0SM6lnBoGWA2VG5QA.png" /><figcaption>Where do you live? Berlin? Toronto? Wellington? 🤔, instead of connecting to earth through trees, I connect to the cyberspace through the phone.</figcaption></figure><p>Here’s a glimpse into recent time I was really busy working with other crypto communities on putting together the <a href="http://edcon.io/">EDCON</a> Sydney 2019 event and the pre-event <a href="https://www.edcon.io/hackathon">#EDCONHACK</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FH8xwlL6xOnstKB1ccbXRw.png" /></figure><p>Observing Apple’s screentime feature snapshot, we can see that a very decent chunk of time is invested online in the cyberspace, in the past we used to interact in-person in a club or at the office, nowadays we’re interacting in Twitter, Instagram, WeChat and Telegram. Now, since so much of what we think of as “self” is channeled through this device, through chats, browsing, social, FinTech, it’s effectively an extension of our being. As it seems today, on the one hand, we’ve benefited tremendously from the fact mobile apps became so ubiquitous, but, we’ve also started being channeled through curated, surveilled and controlled environments where we’re constantly subjected to hooks, manipulations and tricks that product developers set for us. We are effectively at the mercy of product developers if we want to enjoy the advents of the modern digital lifestyle where we’re separated from many things by just a couple of swipes or clicks. How can we fix that?</p><h3>How do we achieve decentralization at the UX/product level?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUq5rLRR6IqNJglPzxO7iA.png" /><figcaption>Yay, the great firewall of China is supporting decentraliztion!!! wait what?</figcaption></figure><p>I’d like to offer one rather controversial point of view that is probably mostly relevant for UX people and product managers: One of the most powerful forces that decentralized the digital products ecosystem from UX perspective is the great firewall of China. Because China is virtually forked the internet and established itself as a rather closed environment, the interfaces that were built there that aren’t influenced by the western world and manifested with entirely different UX paradigms. The reason being that with the amount of hours we netizens use products wires our brains in the way we relate to the cyberspace. People who are designing the products are following different product philosophies and this means that we and up with a vastly different UX school of thoughts we can learn from.</p><h3>Diversity of Digital Species</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDuqx5ORhpVVc1aKJycO6Q.png" /><figcaption>Let a thousand flowers blossom!</figcaption></figure><p>OK, now that we’ve established the concept of diversity of digital products, lets examine some of the differences in *how* UX and products evolved in the Chines context vs. the western school of thoughts.</p><h3>People’s ‘Wants’</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ElhwMeqLhWgRIYPZNLyuhQ.png" /><figcaption>What does a user want and expects in China?</figcaption></figure><p>In China, when someone is opening an app, they’re expecting an experience that will complement the lifestyle and culture that matches the way their digital self is wired. There are various hypothesis for where the differences between China and the west stem from, such as the fact that Chinese is an ideographic language (as my friend <a href="https://medium.com/@zhangweiwu">Weiwu Zhang</a> suggests) or the fact that Asian urban lifestyle is a constant encounter with flux of randomness as you simply walk out in the street. Anyone who lived in China/SEA would know what I’m talking about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*b3FlShMZFYgY_O_x82AqGg.png" /><figcaption>What does a user want and expects in the west?</figcaption></figure><p>In western countries, when someone opens an app, they are expecting a clear, focused and simple way of using a product. This has been historically how Steve Job’s has set the tone with Apple’s design philosophy for minimalism and simplicity. And it could also stem from the fact that western countries tend to be structured and administered in a very templated, repeatable and organized manner. I mean, look at how well European and particularly the English administration methods and culture has been spreading all over the world.</p><p>The examples above are a showing the stark contrast in the approach product developers take when working in western markets vs. Chinese/Asia ecosystems.</p><h3>Integration above everything!</h3><p>In China, developers attempt to give an end to end integration akin to the Apple approach with the logic behind it being:</p><blockquote><strong>Integration</strong> leads to <strong>reduced friction</strong> and thus <strong>increased usability.</strong></blockquote><h3>Divide and conquer, or is it?</h3><p>Meanwhile, in the west, the mentality of a product developer is prioritizing minimalism and ease of management which results in fragmentation. take a look at an example of a folder in iOS that is entirely dedicated to Google products:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*m3y-6tySxOsbZCRrf9fMIg.png" /></figure><p>The reasoning behind the fragmenting products is to help teams manage products efficiently without constantly interfacing one giant app. thus allowing each app have it’s own independence. Another ‘advantage’ in that approach is the seemingly more focused and efficient interaction that users get out of the product, however, in the process of dividing the services into many apps, we’ve increased the number of steps users take when navigating between different apps and often clunky redundancy is introduced in the process. As you can see in the image I ended up having both “Meet” and “Hangouts”, it’s unfathomable and completely backwards IMHO.</p><p>Now that we’ve touched on the differences between east and west, to understand the product philosophy behind one of the most successful Chinese Superapps, lets take a look at principles laid out by WeChat’s creator Allen Zhang 张小龙 and <a href="https://a16z.com/2019/02/05/allen-zhang-wechat-product-principles/">covered really well here</a> by <a href="https://twitter.com/conniechan">Connie Chan</a> (GP of <a href="https://twitter.com/a16z">a16z</a>)</p><h3>WeChat as the world’s greatest Superapp</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1XO8f8yVR353k74qAM6UA.png" /><figcaption>Four Key Product Principles from WeChat’s Creator Allen Zhang 张小龙</figcaption></figure><p>These principles in the way they are laid out can be rather counter intuitive for a western product manager.</p><ol><li><strong>“User is your friend”</strong> — mostly it refers to the fact that for Allen Zhang, the priority you should have as a PM is that the user’s experience will be treated as sacred, if an advertisement or banner is popping to increase profitability and it hinders the experience, then it must not be there in the first place.</li><li>Technology is for efficiency — This means, that the user should be able to get what they need in the most efficient way possible and get out of the app, that is despite the dogmatic narrative often product managers hold: maximize user engagement/time on the platform.</li><li>KPIs are secondary — Zhang’s product management style suggest that tracking data is to help teams be informed, but, they should not be driven by data based on isolated KPIs. Everything has to feed back to the first principle which prioritizes the user’s experience above everything else.</li><li><strong>Decentralized ecosystem</strong> —This principle may sound like an oxymoron given the level of centralization WeChat as an app has. But, Zhang’s reference to decentralization is mostly in terms of the products UI, UX, and distribution. It does not address the protocol or infrastructure layers. Quite often westerners mistake WeChat to simply be a Chinese version of WhatsApp, that is because when you’re opening the WeChat app, there’s ‘chats’, ‘contacts’, ‘discover’ and ‘me’. Nowhere in the app there’s the mini-programs AppStore or a ‘trending publications’ section, however, these exact invisible items are what differentiates WeChat from WhatsApp or any other seemingly similar western messaging app. That means that all mini-programs developers or subscription accounts publishers enjoy a leveled playing field and no particular priority is given to bigger or more funded product teams. This is what Zhang refers to when he means decentralized ecosystem, because the experience difference users have across the ecosystem can be significantly different.</li></ol><p>Lets take a look at the most interesting aspect of a Superapp:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*IF6y2lvwOZGg0nNlqs7yJg.jpeg" /></figure><h4><strong>Mini-programs</strong></h4><p>We’re familiar with the idea of opening an in app one tab browser to read an article, mini-programs extend that to a far deeper level of integration and introduce a very powerful concept: each mini program is effectively a native mobile app that can be opened within WeChat and offer rich functionality without forcing the user to get out of WeChat. One of the reasons this is so powerful is because WeChat has payment integration through WeChat Pay and social features with your contact list. This allows mini programs developers to use WeChat’s API and build for example an eCommerce service without having to develop their own standalone payment channels. A notable example is one particular social eCommerce mini program called Pinduoduo (though quite notorious at the moment): Leveraging the social features of WeChat as well as the WeChat Pay payment channels. It allows users to participate in group purchase straight for the manufacturer for more competitive price than the products would otherwise sell on the market. Pinduoduo as a mini-program on WeChat became the <a href="https://walkthechat.com/pinduoduo-close-look-fastest-growing-app-china/">fastest growing eCommerce platfrom in China in 2018 and IPO’d for over $1B</a>. This example showcases the power of integration that WeChat offers, this is why some people refer to WeChat not as merely an app but rather as a mobile OS!</p><p>The design philosophy of a superapp is a natural fit for open systems like public Blockchain ⛓🥳🚀</p><h3>Crypto + Superapps are a natural fit!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Rk00teHsGcQHw3N4S4XAQ.png" /><figcaption>Koalas riding ETH floating on 8bit rainbow fart</figcaption></figure><p>There are several good reasons why crypto superapps are the solution to bring mass consumer adoption. The fact public Blockchains can be accessed in a permissionless fashion, dapps and services are typically built for integratability and the global nature or crypto are among the major reasons. My cofounder <a href="https://medium.com/u/6183bc726482">Mark Pereira</a> covered more architectural tech consideration of our crypto superapp project Alice in another <a href="https://medium.com/@markpereira17/532143f1a589">post here</a>. Lets take a look into one cool example of project that took integration of #DeFi products as their north star <a href="http://zerion.io/">Zerion.io</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SaMTEDEoXQBHlX2IPqJkTg.png" /><figcaption>Zerion.io interface, integration of #DeFi dapps as a decentralized banking product</figcaption></figure><p>The team at Zerion does amazing work integrating various dapps into one interface: <a href="http://uniswap.exchange/">Uniswap</a> decentralized exchange, Maker’s CDP to borrow stablecoin Dai and more products coming soon. What’s exciting about Zerion’s work is seeing how integration has the potential to reduce friction and make the experience a lot easier. There are still some crucial elements missing in such an interface model:</p><ol><li>📱 The interface isn’t en par with modern slick mobile native apps as it is a web3 supported interface at the moment.</li><li>👛 There isn’t a native wallet as a part of Zerion’s interface because it’s a web3 supported interface rather than wallet. That means that users go through additional steps (friction) when they need to connect an external wallet.</li></ol><p>The 2nd point touches on a really challenging problem every dapp team get to when they want to develop a standalone mobile native app. They would need to build a dedicated wallet just for that one app, this would hinder the user’s experience as their crypto assets will be spread across multiple apps. In addition it adds a lot of development overhead for the dapp team that suddenly needs to develop a full flesh wallet just to support their typically single use case dapp.</p><h3>Alice — Crypto superapp to achieve mass adoption</h3><h3>👱🏻‍♀️📲🕳🐇😺🎩🐛🍄🃏👸🏻♦️♠️♣️♥️</h3><p>My co-founder at Alice Mark Pereira wrote a great introductory piece about Alice already. We see the solution to crypto mass consumer adoption being a mobile crypto superapp because of the following factors that make crypto + superapp a natural fit:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*lUPvVvMd5rRs0RUNTxIrFg.png" /><figcaption>Alice minidapp list interface</figcaption></figure><ol><li>Crypto dapps are unstoppable and accessible to everyone on the Blockchain.</li><li>Integrating between dapps/protocols is adding more ways to use them and reduces the friction of having a dedicated wallet + app for each dapp following Allen Zhang’s product philosophy.</li><li>Introducing minidapps into a mobile superapp will unleash all the power mobile has to offer: 📸 camera access, 🧭 location features, 💬👭 Chat and social features.</li></ol><p>More on the that will be covered in following posts we’ll release as Alice develops.</p><h3>How would the transition from web to mobile dapps look like?</h3><p>The ability to give dapps full advantage of the mobile features means that an application like LocalEthereum which currently offers browser interface, would look and feel like the applications we use everyday to make our lives easier. In this particular example, the user base demographics of LocalEthereum is predominantly Venezuelans affected by the hyperinflation crisis. They would benefit tremendously from location features, camera access, smooth chat that will allow them to engage in trades in person with much more convenient coordination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Z9dl2UI_4CLisl58YvWIQ.png" /><figcaption>Left: Current LocalEthereum web interface. Right: LocalEthereum as a minidapp in Alice.</figcaption></figure><p>Hope you’ve enjoyed the read and let us know if you’d like to get in touch! Stay tuned for updates about Alice.</p><h3>Socials for Daniel</h3><ul><li>Twitter: <a href="http://twitter.com/danieltbar">@danieltbar</a></li><li>LinkedIn: <a href="https://www.linkedin.com/in/dtbar/">https://www.linkedin.com/in/dtbar/</a></li><li>Instagram: <a href="https://www.instagram.com/danieltbar/">https://www.instagram.com/danieltbar/</a></li><li>GitHub: <a href="https://github.com/dtbx">https://github.com/dtbx</a></li></ul><h3>Learn More about Alice</h3><ul><li>Website: <a href="http://alicedapp.com/">Alicedapp.com</a></li><li>Twitter: <a href="http://twitter.com/heyaliceapp">@heyaliceap</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=908769976ec5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alice-dapp/crypto-superapp-ux-preparing-for-mass-user-adoption-908769976ec5">Crypto #Superapp UX — Preparing for Mass User Adoption</a> was originally published in <a href="https://medium.com/alice-dapp">Zed Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alice — Once Upon A Time…]]></title>
            <link>https://medium.com/alice-dapp/alice-once-upon-a-time-d27afc3779d7?source=rss----c6a649507552---4</link>
            <guid isPermaLink="false">https://medium.com/p/d27afc3779d7</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[super-apps]]></category>
            <category><![CDATA[wallet]]></category>
            <dc:creator><![CDATA[Mark Pereira]]></dc:creator>
            <pubDate>Thu, 25 Apr 2019 10:59:48 GMT</pubDate>
            <atom:updated>2019-04-26T01:19:08.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>Alice — Once Upon A Time…</h3><p>What I’m going to introduce you to is a solution with the power to rapidly increase mass adoption in the cryptosphere, Alice.</p><p>Project Alice’s journey began after Daniel Bar and myself started an accelerator in Sydney, Australia. The accelerator (<a href="https://www.founders.unsw.edu.au/programs/10x-accelerator">10x Founders program</a>) is run out of The University of New South Wales. We started off with a few theories and went off into the crypto wilderness, interviewing people building crypto applications and also crypto users. The feedback we got was phenomenal. Thank you to all who took the time out to answer questions and surveys as we were able to solidify our first proof of concept for Alice.</p><p>An idea was born for a crypto super app, the idea of a super app became apparent to me on the launch of wechat mini programs. This idea has been iterated and emphasized upon by Connie Chan from a16z in <a href="https://a16z.com/2018/01/13/super-apps-china-product-innovation-wip/">this article</a>. This is the solution that ticked off the most problem/solution criteria.</p><p>So Super Apps, what are they? They are mobile applications which have a feature rich platform, then, in the form of mini applications within the super app, offer up different services built atop this platform. Examples of these platforms are WeChat’s payment channel and social app, GoJek’s transport/ride sharing services, or AliPay’s payment gateways. <br>Some platforms are closed so that only the creators of the platform choose the apps they want inside their super app. However, in some cases the app is completely open for any entity to build in, like WeChat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W_7EujlXlq6loBgqCkpIeQ.jpeg" /></figure><p>There are concerns with apps like AliPay and WeChat because of their entanglements with the <a href="https://www.theverge.com/2018/2/1/16721230/wechat-china-app-mini-programs-messaging-electronic-id-system">Chinese government</a> and infringements on user’s privacy. However, what we’ve seen through our time in the blockchain/cryptocurrency realm is the ability to build out applications that are privacy focused and entirely concerned around a user’s privacy.</p><p>This is why we created Alice, a crypto mobile, super app. So that user’s can feel free to roam and explore their digital spaces and express themselves digitally without feeling like they’re being limited or restricted or even surveilled on the platform. The ultimate freedom in a connected world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O01AWoRv-_8MJMDgVzNJfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Pr7wzkfwaTcleyPzvsegQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yu1QXPcVD2AbI5weoIDFPw.png" /><figcaption>Cryptokitties native mobile prototype</figcaption></figure><p>Imagine having all of your favourite crypto apps on mobile all within your wallet. The things you could accomplish in just a few clicks rather than navigating through clunky mobile web interfaces. Also having all your crypto in one mobile app, giving you access to all your funds in the palm of your hand while browsing the decentralised web.</p><p>A fundamental product concept we’re keeping at the heart of Alice is a foundational principle of design and product evolution. People use solutions that make their lives easier and more efficient, and this is at the helm of our design thinking. We want to make crypto a solution that is easier to build solutions for any business on and easier for any user to exchange value, worldwide.</p><p>Where are we up to now? Luckily the <a href="https://coinlist.co/build/0x/votes">0x + Coinlist hackathon</a> was taking place at the time we were doing research. We entered the hackathon and received the community choice award for Alice entry. I then flew to ETHDenver to explore more mobile first solutions and finished runners up with Franky Aguilar with the <a href="https://kauri.io/article/ce805bf2e6664b919b6a8eb150462d06/v2/battle-bombers">BattleBombers</a> mobile app.</p><p>We’ve built out a proof of concept using a fork of the Balance/Rainbow wallet and are now building native iOS and Android apps with the ability to build React Native mini dapps into. We’ve had the amazing opportunity to present Alice on the main stage at <a href="https://www.edcon.io/">EDCON Sydney</a> and at the <a href="https://www.youtube.com/watch?v=3Zp4bXob-o8">Web3 UX Unconference</a>. We’ve received great reviews from the Ethereum community so far and are moving full steam ahead with the build!</p><p>For the technical spec: <a href="https://medium.com/p/532143f1a589/">Alice technical proposal</a></p><p>To follow our journey, keep an eye on Alice at:<br>Twitter: <a href="https://twitter.com/heyaliceapp">@heyaliceapp</a><br>Website: <a href="https://www.alicedapp.com/">alicedapp.com</a></p><p>My Socials:<br><a href="https://twitter.com/markpereir">@markpereir</a><br><a href="https://www.linkedin.com/in/markspereira/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d27afc3779d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alice-dapp/alice-once-upon-a-time-d27afc3779d7">Alice — Once Upon A Time…</a> was originally published in <a href="https://medium.com/alice-dapp">Zed Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>