A
Your side
Feeds, retailer partnerships, crawl strategy, the market and language. cijene.me has its own catalogue; a custom app is not a clone with a flag swapped.
Consumer commerce
A price comparison app is useless if search is slow and the comparison table is three taps away. Users need to find an offer, filter the noise, and act. CodeLoop Studio built cijene.me as a mobile-first comparison product: search, compare, decide — with Flutter on both stores.
Case study
cijene.me
A live price-comparison app, not a Dribbble shot. Search-first home, filters that narrow the set, comparison layouts so shoppers decide instead of bouncing to a random tab. Flutter on both stores.
A price comparison app is useless if the table is three taps away. Users need to find an offer, filter the noise, and act. CodeLoop Studio in Sarajevo built cijene.me as a mobile-first product: search, compare, decide. We are not a coupon-clipping content farm. We engineer the app and the comparison logic.
Feeds and freshness come first. Stale prices destroy trust. Categories, tags, and product information architecture have to stay honest when the catalogue grows — otherwise you shipped a pretty empty state. We plan for missing prices instead of pretending every SKU is live. You bring feeds, partnerships, or a crawl strategy; we engineer ingestion, ranking, and the mobile UX around it.
Another country is a new product with its own retailers and language — not a sticker over cijene.me. The stack that made this class of app ship on both stores is Flutter app development. A sharp first version is MVP development. Typical studio projects take 3–9 months from idea to launch; a vertical MVP (one category, one market) can be faster. Written estimate within 24 hours via the online estimate.
Shoppers open a comparison app to answer one question: is this cheaper, and can I trust the number. If query-to-result is slow, nothing else matters. If the table is three taps behind a magazine layout, they bounce to a random tab. cijene.me is built around search UX, practical filters, and comparison-first screens so time is spent on the offer. Facet rules have to match how people shop in that market — not a generic e-commerce sidebar copied from a theme.
We do not provide a secret worldwide price graph. cijene.me has its own catalogue and comparison logic. For a custom app, you bring feeds, partnerships, or a crawl strategy. We engineer ingestion, ranking, missing-price states, and the mobile UX. Stale prices destroy trust faster than an ugly icon. We plan for empty and outdated rows instead of pretending every SKU is live.
Flutter is the usual stack because the work is search, lists, and comparison — not a platform-specific camera pipeline. Native if a device API forces it. A single-category MVP in one market is how you learn; “every retailer in Europe on day one” is a cathedral. Web comes later when SEO and sharing matter: crawlable categories on Next.js, still the same studio. Another country is a new product with its own language and retailers — not a flag sticker over cijene.me. Feeds and ranking dominate the 3–9 month band. Say where prices come from, or the estimate will be fiction. Studio in Sarajevo. English with EU and US teams. We do not invent retailer counts. A vertical MVP in one category is how you learn whether shoppers come back — not a homepage that pretends the catalogue is already complete.
Find an offer
Search-first home. Shoppers do not browse endlessly. Query-to-result is core, not a plugin.
Narrow the set
Filters and tags that match how people shop in your market — not a generic e-commerce sidebar.
Decide
Comparison layouts. Less bounce to a random tab. The table is the product, not three taps away.
Trust the number
Freshness rules. Missing prices shown as missing. A fake “in stock everywhere” is how you lose the next open.
Both stores
Flutter because the UX is shared: search, lists, comparison — not a platform-specific camera pipeline.
Web when SEO matters
cijene.me is mobile-first. Many comparison products later need a Next.js surface for landing pages and crawlable categories.
A
Feeds, retailer partnerships, crawl strategy, the market and language. cijene.me has its own catalogue; a custom app is not a clone with a flag swapped.
B
Ingestion, ranking, search UX, Flutter on iOS and Android, store listings, a plan for stale and missing data. Native only if a device API forces it.
Where prices come from
API, partners, crawl. Freshness SLA you can defend. Without this, the app is a shell.
One category, one market for v0
A vertical MVP is how you learn. “Every retailer in Europe” is a cathedral.
Whether you need crawlable web
Mobile-first can wait on SEO. If sharing and Google matter on day one, say so. Estimate form.
Related