Jinius Marketplace

Search, category navigation and checkout for Cyprus' largest B2B and B2C marketplace.

Jinius (Bank of Cyprus) · UI/UX Designer · Jul 2024 to Jun 2025 · Responsive web (Salesforce Commerce Cloud), native iOS app, Android progressive web app.

Context and team

Jinius is the Bank of Cyprus digital marketplace: multi-vendor, 500K+ SKUs across 14 categories, built on Salesforce Commerce Cloud. I was the lead UX designer in a product team of a product owner, a data analyst, a second UX designer and the engineering team, plus a small iOS team for the native app. During the twelve months I was on the platform it reached 4M+ visits, +124% average monthly visitors and a 60% monthly return rate.

My remit

Interaction and interface design for the homepage, search, category navigation and the end-to-end checkout on web, and for the native iOS app, which I designed with a small team of iOS developers and launched during the engagement. For Android we shipped a progressive web app rather than a native build. I was involved from requirements gathering: hard requirements (the two shipping modes, gifting, the SFCC constraints) were fixed by the business; the soft requirements were shaped with the product owner and data analyst, and design had its input there from the start. From that point I owned how each flow worked and looked on every platform, and I ran the behavioural analysis in Microsoft Clarity and GA4 that fed friction points back into the backlog.

One decision: keeping checkout single-flow while adding two shipping modes and gifting

The business needed home delivery, ACS pick-up point or locker, and a gifting option. The obvious approach adds steps, and returning customers pay for that on every order. I kept checkout as one step-by-step flow and made shipping mode a single choice inside the existing shipping step, with an ACS location finder (nearest points by distance and opening hours) appearing only when pick-up is selected. Gifting became a flag in the order summary rather than its own screen, so the primary path stayed the same length for everyone who didn't need it.

Native iOS and Android PWA: one product, two mobile strategies

The iOS app was a native build with a small iOS team; Android was served by a progressive web app. Opted for the PWA due to tech stack limitations and time to market. We wanted to ship something as fast as we could during the same time when we were going to launch the iOS app. Designing both for the same product meant deciding screen by screen where the iOS app should follow platform conventions and where it should carry the web pattern across so the experience stayed recognisable.

Result

The platform's growth figures above are team outcomes; my contribution was the search, navigation and checkout experiences shown here, on web and iOS.