Ethos Unified App Development
Type: OATH Improvement Proposal (OIP)
Proposal Author: Everett Holcomb
Date: November 27th, 2023
The Oath ecosystem is falling behind in capturing market share. I propose a budget to fund the restructuring of all Byte Mason/Oath Ecosystem domains in order to remedy this. The objective is to give users (new & current) a more defined and intuitive way to interact with/discover the ecosystem, reduce user-facing complexity, and bring light to the value of the Oath token.
The current products/services suffer from severe fragmentation and lack features of a modern web app. New users aren’t presented with an intuitive product, nor do they have a funnel that guides them through their desired feature/function.
All of the following domains are required to understand & use the Oath ecosystem.
Landing Page: oath.eco (no product on this domain)
Ecosystem Docs: oath.eco/documentation
Oath Token Information: oath.eco/documentation/#tokenomics
Governance Discourse: forum.oath.eco
Governance Voting: https://snapshot.org/#/oatheco.eth
Loan Landing Page: ethos.finance
Loan Docs: ethos.finance/documentation
Loan App: app.ethos.finance
Yield Landing Page: digit.xyz
Yield App: app.digit.xyz
2nd Yield App: reaper.farm (no landing page)
2nd Yield App Documentation: docs.reaper.farm
At first glance this may seem (somewhat) organized. As soon as you experience this funnel, the user journey becomes disorientating.
OATH has no clear value when interacting with anything besides Ethos Reserve, nor is it clear that these products are within the same ecosystem.
Managing that many domains is both expensive and inefficient. The complexity of each product is not high enough to justify separation.
The goal of this proposal is as follows:
- Consolidate all products/services into one domain and rebrand it as Ethos (ethos.fi)
- Create a new landing page that highlights the various use cases of the app
- Design a new user journey that is both exciting and easy to digest
- Deliver market leading UI/UX
- Add critical features such as notifications (can be forwarded to TG and Discord)
- Provide an intuitive dashboard that allows the user to quickly see their positions and manage them with ease
- Create a dedicated page within the app for interacting with OATH (ethos.fi/oath)
Potential Conflicts of Interest
None identified at this point. Continuous disclosure will be discussed with the community should any arise in the future.
As an outside party, this initiative can be very complicated to execute due to the unknown technical challenges that may present themselves. The following is an outline on how this problem would be approached.
Part I: Testing the Waters
The initial phase would be to overhaul a single product, such as borrowing. This speeds up development and reduces the initial cost significantly. A temporary domain would be set up (reserve.ethos.fi) to act as a standalone service while all features/products are being built. As a complete app, the domain would become (ethos.fi/reserve). This allows each product to be focused on individually. During this process, the design and execution will be evaluated. If all parties are happy, an extension to this proposal (new governance vote) can be added to continue development.
Part II & Beyond: Full Overhaul
Now that the infrastructure for a new app design is in place, each product would be rebuilt and deployed following the same process (earn.ethos.fi, trade.ethos.fi, etc.). A lot of heavy lifting will be done during phase one, making development of additional products much faster. Once all products are deployed and fine-tuned, they would be consolidated to a single domain (ethos.fi/…), completing the unification process.
Once obligations are met, the front-end would become the responsibility of the Byte Masons to maintain. This is mainly a formality, we’re always happy to help with any issues.
Devoux is a new initiative started in 2023 by my brother and I. He is a senior front-end developer while I am a brand designer & strategist. Each of us have 10+ years of experience creating unique products and concepts. We operate very lean, but also have a network of talent that we can bring on when timeframes are short.
Our responsibilities entail:
- Getting to know a brand from the inside-out. This includes dissecting the audience, understanding company goals, and defining values.
- Creating a foundation and approach based on this research to position the product within its market.
- Carefully planning visuals, language, tone, and voice to deliver a product that is both visually stunning, and easy to use.
- Developing a lightweight component library with clear documentation on its flexibility and use cases.
- Creating the code that produces these assets: Source code, build scripts, images, etc.
- Provide developer tooling: dev environment, docs, mocks, and tests.
Notable Companies we’ve done work for: Nike, Under Armour, Puma, Vuori, Linksoul
A demo has been created to showcase the general approach we’d take to create this web app. It’s pretty basic in its current form, and most of the interactions are disabled, but hopefully it can get you excited for the future of Byte Masons products. Click around and see what you can find!
To make the demo experience better, I suggest going into the options bar in the top right of the interface and unchecking “Show Figma UI”
Key Objectives & Success Metrics
The objective is to create software that presents a clear value of the product to the user. Additionally, we want it to be an enjoyable and repeatable experience. It’s paramount to deliver a product that allows users to accomplish their goals with as little friction as possible.
Success would be measured by new user retention, increased user interaction, and growth in total OATH participants.
Length of Engagement & Budget Breakdown
Phase One scope of work is estimated at 3 months, with a budget of 10,000 USDC and $5,000 in OATH, per month. Phase Two would be discussed upon completion of Phase One.
The risk involved is that this effort becomes ineffective. Both time and money are being used to restructure user-facing products. If done incorrectly, this could yield no ROI.