Coinmarketview

Coinmarketview is an information portal with a mobile application created for those investing in the cryptocurrency market in 2018. Our client commissioned us to design and implement this challenging task.

The key goal of the Coinmarketview portal was to gather information about cryptocurrencies, provide information about their prices, and provide information about cryptocurrency-related events. It was intended to become an information hub that organizes the extensive knowledge about cryptocurrencies and presents it in a user-friendly format. The planned mobile app would pull information from the portal and present it in a more accessible way for people primarily using mobile devices.

• We conducted a persona analysis – we distinguished several personas, including: 1. Amateur investor, a group of people investing small amounts of their savings, working remotely 2. Rentier investor, treating investments in cryptocurrencies as a supplement to their investment portfolio (aggressive part of the portfolio)
• we have developed a description of the specific functions and operation of the Portal – after a thorough analysis of needs, it turned out that the user paths are uniform
• We prepared a preliminary design of the portal’s home page in 2 graphic lines to show the assumptions and obtain the client’s initial approval

During the design phase, we prepared low- and high-fidelity mockups for both the portal and the mobile app.

The main goal of building the management panel was to simplify the portal’s administrator experience, allowing content to be entered and published from a shared management panel.

During the prototyping and design phase, we developed:

• event publication management system with advanced search criteria:
  • Search by date (selected date range from the calendar) + ranges (today, tomorrow, 7/14, 30 days ahead)
  • by keyword
  • by coin type (2,000 coins published)
  • by exchange (200 items) / with suggestions based on the first 3 letters
  • by category (flexible addition of new categories)
  • sorting by date, last added, rank
• Event rating and ranking module
• Event information building with integrations with social media and partner websites/portals
• Google Calendar integration
• Ad management module on the portal (defining publication locations, formats, publication times, linking to the advertiser database, and managing the advertiser panel)

Each event box can be shared on FB, Twitter, etc. (how to solve this issue), we want to sign the given box with the name of our website and name.

The pre-implementation documentation consisted of:

• Clickable prototype mockups in Figma (desktop and mobile portal versions, and a separate mobile app)
• Content specifications – for the development of event descriptions and information subpages
• User manuals – for content introduction rules (primarily for events) and advertising module management

Due to the portal’s primary nature as an application (the application was powered by data from the portal), we implemented the portal first.

The portal implementation work lasted two months and was divided into four sprints (each sprint lasting 10 business days), including: 8 business days for developer work, 2-4 hours for QA testing by the tester, 2-4 hours for corrections, and 4 hours for client-side testing. Due to the relatively small scope of work, we planned a short period for corrections in each sprint; if the work was completed faster, we started another sprint.

Management and progress control:

• In the Monday.com system, we maintained a board accessible to the client and the team, where we monitored project progress
• The client reviewed a given sprint and provided feedback in sprint comments
• Sprint closure, acceptance protocol, and work settlement were all handled entirely remotely

After completing the portal implementation, we moved on to implementing the mobile app. From a process perspective, it was practically the same, but it ran in a different technical environment: Flutter. The app implementation took approximately three months.

Before moving to LIVE, both the portal and the application underwent a process of supplementing content and rigorous testing.

• We implemented the test events, and the client implemented the rest.
• Manual testing in the test environment – we performed testing according to the client’s scenarios.
• Load testing – our server administrator performed speed and load tests, including those for information exchange between the portal and the application.

We provided technical support and development activities for both the portal and the application.

During development, we maintained high standards of work culture and knowledge continuity, including:

• Development work is conducted in a 1:1 test environment compared to the LIVE version, integrated with the SAP test environment
• All graphic changes are first implemented on clickable mockups in Figma, known as masters, and checked for their impact on e-commerce UX
• We run application test environments on Browserstack
• We maintain a code repository