Veyra Medical.
Make technical information easier to explore.
A completed personal equipment-catalogue website with structured product information, category navigation and a considered business-enquiry experience.
- Project type
- Independent personal build
- Project focus
- Medical equipment catalogue website
- Presentation
- Two representative interface visuals
- Viewing mode
- Portfolio case study
A clear purpose.
A considered build.
The challenge
Technical catalogue visitors need a consistent way to compare product information. Dense specification copy and disconnected documents can make that harder, while unsupported clinical claims create a different and unnecessary risk.
The approach
Veyra separates category discovery, product information and the enquiry step. The case study focuses on the catalogue's content structure and visual hierarchy, using fictional equipment illustrations instead of manufacturer material or real diagnostic displays.
Who the experience is for
An equipment-distributor website use case. The items illustrated in this portfolio are specimens, not approved medical devices offered for sale.
Real development experience. Independent projects.
I have built client websites and web applications as part of an agency team. Those deliveries are separate from the independently branded projects shown here; client code, screenshots and private data are not reused.
A closer look at the project.
Explore the next screen below, or open the gallery to browse all project previews.
Product information layout
Illustrative interface · Sample content
The journey,
step by step.
The key experiences and information decisions covered by this case study.
Browse a product family
Category navigation creates an entry point into the catalogue without relying on clinical outcome claims.
Read the essentials
The product-information layout groups overview text and supporting detail in a repeatable structure.
Prepare a business enquiry
The enquiry context stays tied to the product being considered, rather than asking visitors to submit patient information or payment details.
More than a
different colour palette.
Ice blue and navy give the catalogue a precise identity. Original device illustrations sit beside consistently grouped information so the product story remains readable. Clear boundaries between an overview, supporting detail and the next action avoid one continuous specification wall.
Original product artwork
The illustrated devices establish a coherent catalogue style without implying a manufacturer relationship or showing patient results.
Consistent information groups
Repeating the same content hierarchy across product pages helps readers compare like with like.
Claims stay bounded
No regulatory marks, device approvals or clinical performance numbers are used as portfolio proof.
The work.
And its context.
This case study presents the project's purpose and interface decisions without requiring a public demo or account access.
These describe the work's subject and design priorities, not a list of unverified technologies or integrations.
- 01SCOPE & CONTEXT
Completed personal catalogue website, not an operating medical-device retailer.
- 02SCOPE & CONTEXT
Original specimen product artwork; no client or patient data.
- 03SCOPE & CONTEXT
Real specifications and documents need approved content owners before commercial use.
- 04SCOPE & CONTEXT
No ecommerce, regulatory approval or medical advice is implied by this portfolio.
About this project.
Personal implementation, representative visuals and live access are separate things. The case study makes that distinction explicit.
Is this project completed, and can I open the live site?
This is a completed personal project. The public page is a case study, not a live application demo. Live-site URLs, account logins and source-code links are intentionally not published.
How is the project credited?
This is an independent personal implementation by Ali Rehman, presented as a personal case study rather than a client engagement.
What do the project visuals show?
Representative interface artwork with illustrative content, retained from the design process. These visuals are not screenshots of the finished application or evidence of production results.
Can we discuss a similar project?
Yes. Use the contact page to describe your requirements. Any new work would have its own scope and original implementation; client code, confidential data and proprietary assets are not shared.
Planning something similar?
Explore the relevant service scope and a practical planning guide before describing your requirements.
Keep exploring.
All personal projects
Have a project in mind?
Let's discuss an original build around your requirements—not reuse an employer's work.
All previews stay inside this portfolio.