
React Native
React Native Desktop
React Native UI Kitten
React Native Paper by Callstack
React Native Elements
Flutter
Shoutem UI toolkit
Experience the awesomeness of React Native without the pain

Year/Make/Model fitment search for Shopify. 8 verticals, Smart Parse, and your data in Shopify metaobjects — not a vendor database. Free tier, Pro at $49.

Which is more popular?
Based on our record, NativeBase seems to be more popular. It has been mentioned 22 times since March 2021.
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | nativebase.io | normalview.pro |
| Pricing | ||
| Platforms | — | |
| Company | — | Startup from the United States · 1 - 9 employees · 2026 |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of NativeBase yet.
ViewForge is a Year Make Model (YMM) parts finder for Shopify. Shoppers pick their vehicle, machine or device from cascading dropdowns and see only the parts that fit. Fitment search works across eight verticals — auto, motorcycle, tractor, marine, power equipment, bicycle, printer and...
What each product offers, as listed by its team.


Possible disadvantages
Walkthroughs and reviews on video.
NativeBase Market Purchase Flow
ViewForge: YMM Search & Filter
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing NativeBase and ViewForge.
ViewForge's answer:
Three things. (1) Data ownership: ViewForge writes fitment as Shopify metaobjects native to your store — most competitors store fitment in their own database. (2) 8 verticals out of the box: auto, motorcycle, tractor, marine, power equipment, bicycle, printer, electronics — most competitors are automotive-only. (3) Smart Parse: extract fitment automatically from your existing product titles and descriptions instead of re-typing everything.
ViewForge's answer:
Data ownership. Fitment lives in your Shopify metaobjects, so uninstalling does not take your compatibility data with it. Convermax, EasySearch and PartFinder all keep it in their own databases, and getting it back depends on their export tooling on the day you cancel.
Cost at the low end. The search widget, the compatibility table on the product page and the saved-vehicle garage are all on the free tier, up to 50 products, with no expiry. EasySearch puts the table and the garage behind its $75/month Premium plan. Convermax starts at $250/month.
Automotive and non-automotive coverage. Eight built-in templates, and fully custom templates from $19/month, for catalogs that do not decompose into Year/Make/Model at all.
ViewForge's answer:
Shopify merchants whose customers need to know whether a part fits before they will buy it — and who do not have an engineer on staff to build that themselves.
Concretely: auto and truck parts retailers, powersports and motorcycle dealers, tractor and agricultural parts sellers, marine and outboard suppliers, small-engine and power equipment stores, bicycle and e-bike component shops, printer supply merchants, and electronics accessory sellers.
Catalog sizes run from a few dozen products on the free tier up into the tens of thousands; it is running in production on a catalog of roughly 40,000 SKUs. The common thread is not the industry — it is that "does this fit my thing" is the question deciding the sale.
ViewForge's answer:
ViewForge came out of agency work. Normal View was building for a parts retailer running roughly 12,000 SKUs who needed fitment search, and every app we evaluated stored the merchant's compatibility data in the vendor's own database.
That is a strange trade when you look at it directly. Fitment data is genuinely expensive to produce — it is weeks of work — and the merchant would not own the result. It would belong to whichever app happened to be installed that year.
Shopify metaobjects made a different answer possible: write fitment as native structured data inside the merchant's own store. The theme reads it, the Storefront API queries it, Admin GraphQL exports it, and it is still there after an uninstall. That decision is what the rest of the app is built around.
Everything else came from real catalogs rather than a roadmap. Eight verticals exist because a tractor catalog is not Year/Make/Model. Smart Parse exists because that retailer had already written fitment into 12,000 product titles, and nobody was ever going to retype them.
ViewForge's answer:
Share your experience with using NativeBase and ViewForge. For example, how are they different and which one is better?
Recommendations tracked on public social media and blogs since March 2021.


Gluestack, like any other customizable UI library, is built to make styling less cumbersome. It comprises a set of themed and unstyled components easily integrated across different platforms and devices. Originally, Gluestack was a part... - Source: dev.to / over 2 years ago
Just like the other libraries mentioned in this article, Gluestack is another unstyled component library. Originally a part of NativeBase, the developer team created this library to prevent bloat and enhance maintainability of the project. - Source: dev.to / almost 3 years ago
KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla... - Source: dev.to / about 3 years ago
Tracking ViewForge since Aug 2026.
When comparing NativeBase and ViewForge, you can also consider the following products.

A framework for building native apps with React
Compare React Native to NativeBase or ViewForge:

Build OS X desktop apps using React Native
Compare React Native Desktop to NativeBase or ViewForge:

Customizable and reusable react-native component kit
Compare React Native UI Kitten to NativeBase or ViewForge:
Material Design for React Native (Android & iOS)
Compare React Native Paper by Callstack to NativeBase or ViewForge:

Cross-platform React Native UI Toolkit
Compare React Native Elements to NativeBase or ViewForge:
