Everything in one private wallet

• Loyalty cards at the till. Scan a card once and show it full screen when you pay. Stowly recognises around 130 store brands with their logo text and colours.
• QR codes you want to keep. Wi-Fi access, tickets, payment codes and anything else, saved with a suggested title so you can find it later.
• Documents and receipts. Scan multi-page documents with automatic cropping and on-device text recognition, then export a clean PDF.
• Shopping lists. Add items with quantities, tick them off, and link a loyalty card to a list so it is ready when you reach the checkout.
• Reminders for expiry dates. Give a card or document an expiry date and get a local notification before it runs out.

Private by design, on iPhone too

Stowly for iOS has no accounts, no ads, no analytics and makes no network calls at all. Your wallet stays in a local database on the device, and the only things that ever leave it are the exports and shares you start yourself. You can lock the app with a PIN or Face ID.

Native, not a port

The iOS app is written in Swift and SwiftUI rather than wrapped around the Android code, so it looks and behaves like an iPhone app should. It speaks the same 24 languages as the Android version, including Slovenian.

Backups travel between platforms. Export your wallet to a ZIP on Android, optionally encrypted with a password only you know, and import it on your iPhone with everything intact. It works the other way round too, so switching phones never means starting over.

Stowly runs on iOS 18.6 or newer. Screenshots and the full feature list are on the Stowly page, and the privacy policy explains exactly what the app stores.

What you get

• 26 designer themes. Professional, modern, classic, minimal and bold looks, each one a tap away, with your own accent colours, fonts, spacing and page style on top.
• One or two columns. A classic single column or a full-height sidebar for your photo, contacts and any section you like.
• A live preview that matches the export. The same engine draws the page on screen and in the file, so what you see is exactly what you send.
• An ATS-optimised mode. One clean column and plain, readable text, so screening software can follow your CV.
• Export the way you need. A multi-page PDF with selectable text, a Word (.docx) file, an image of the first page, or a portable .cvm file.
• A language per CV. The app speaks English and Slovenian, and each CV sets the language of its own headings.

Made for iPad too

On iPad the editor keeps the left half of the screen and the live preview the right, so the page updates in front of you as you type. The library spreads into large previews of every CV you have made.

Your CV stays yours

KeptCV works entirely on your device. There is no account, no backend and no network code in the app. Your CVs, your photo and your settings stay on the phone or tablet, and nothing is uploaded anywhere.

The iOS app is written natively in Swift and SwiftUI, and it shares the document format with the Android app. A .cvm file exported on Android opens on iPhone with its content, design and photo intact, and the other way round.

KeptCV runs on iOS 17 or newer. Screenshots and every feature are on the KeptCV page.

Two platforms, two specialists

2MAD Labs is literally two Mobile App Developers: one writes Android in Kotlin and Jetpack Compose, the other writes iOS in Swift and SwiftUI. Each of us works in the language, tools and design conventions of one platform every day. Splitting the work this way means neither of us is translating between platforms in our head, and each app feels at home on the phone it runs on.

What native buys the people using our apps

• Platform-correct behaviour. Navigation, gestures, text sizes and system settings work the way people already expect on their phone, because we use the platform's own building blocks.
• Performance. A price map with more than a million deals, like the one in Cenilko, has to scroll and zoom smoothly on an ordinary phone.
• Everything the system offers, on day one. Widgets, Wear OS and Apple Watch, Android Auto and CarPlay, TV apps and foldable layouts are available as soon as the platform ships them, without waiting for a wrapper to catch up.

The layouts that make the difference

Big screens are where native pays off most visibly. On a tablet, Cenilko turns its bottom bar into a side rail and opens a building's report next to the map. On a foldable, half-fold the phone into a tabletop and the map moves above the hinge with the details below it. On iPad, the SwiftUI app gives the map its own half of the screen. None of that is a stretched phone layout.

Where we make an exception

Games are a different kind of project. When one game should run the same on both platforms, a single Unity codebase can be the right fit, and we use it when it is. For everything else, which is most of what we build, we write each app natively.

What it costs, honestly

Building natively does mean writing core features twice and keeping two apps in step. We accept that trade because the result is better for the person holding the phone, and because a shared plan, a shared design and shared data formats keep the two versions close. It is also why a new app sometimes reaches one platform before the other.

The same approach applies to client work. If you have a project for phones, tablets, watches, cars or TVs, write to us and we will give you a straight answer about fit and timeline.

Who is writing

2MAD Labs is short for two Mobile App Developers. One of us writes native Android in Kotlin and Jetpack Compose, the other writes native iOS in Swift and SwiftUI. Every app on this site was designed and built by the two of us, and we still maintain all of them, so the posts come straight from the people doing the work.

What you will find here

• Releases. New apps, apps arriving on a new platform, and the updates worth knowing about.
• Behind the build. How we approach architecture, offline data, accessibility and design, including the things that did not work the first time.
• Studio news. What we are working on next, and the occasional look at how a two-person studio actually runs.

Every post appears in English and in Slovenian. The Slovenian versions are written rather than translated, so the two can read a little differently.

How to follow along

There is no newsletter and nothing to sign up for. The blog has an RSS feed that works in any feed reader, and like the rest of this site it sets no cookies and runs no analytics. We would rather you read the posts than we count you.

If a post raises a question, or you have a project in mind, write to us at info@2madlabs.com. We read every message.

Designed for clarity first

We designed Gremo especially for older travellers, without making it feel clinical. The controls are large, the contrast is strong, the type is Lexend and the app follows your system text size. The whole trip is on one screen, and Gremo never presents an invented direct route: if you need to change, it shows you where and flags a tight transfer.

What it does

• Bus and train together. Search the official national timetable with up to two transfers. Comfortable routes keep train, bus and mixed options apart and flag short transfers.
• Live context. Published delay estimates, cancellations, vehicle information and operator notices, whenever the live feed has them.
• Routes you repeat. Save your frequent journeys, reopen them in one tap and set a local reminder about 15 minutes before departure.

Useful without a connection

The timetable is built into the app, so you can search it offline. Gremo goes online to check for timetable updates and to add live delays and notices, and when live data is not available it says so plainly. There are no accounts, no analytics and no ads. Your saved routes, recent places and reminders stay on your device.

Gremo is in Slovenian, runs on Android 8 or newer and iOS 18 or newer, and is written natively in Kotlin with Jetpack Compose on Android and in Swift with SwiftUI on iOS. Screenshots and details are on the Gremo page.

What it does

• A price map of every deal. More than a million recorded sales and rentals since 2007, coloured by euro per square metre and filtered by year and property type.
• Estimates you can defend. Enter a size and an area and you get a value with a price range, a confidence level and every comparable deal behind it. No black box.
• The full file on a parcel. Tap a building to see zoning and actual land use, its units and past deals, plus seismic, flood and radon attention, heritage protection and the energy certificate.
• Area analysis. Median prices, market premiums, a repeat-sales index, rental yield and local affordability, with two places on the same charts.

Built on public registers

Everything in Cenilko comes from public sources: the Surveying and Mapping Authority (GURS), the Water Agency, the Ministry of Culture, the national statistics office (SURS) and a few more, eight in total. The data refreshes every seven days. The database downloads once, and after that search, statistics and estimates run on your device.

Cenilko cleans, links and aggregates that data, which is what makes one map and a fair comparison possible. It also means a figure can differ from the official record.

Native on both platforms

The Android app is written in Kotlin with Jetpack Compose, and the iOS app is a native SwiftUI build of the same tool rather than a port. On tablets and iPad the extra width goes to work: the map keeps its own half of the screen and the analysis becomes a dashboard with every chart in view. On a foldable, half-fold the phone into a tabletop and the map moves above the hinge with the details below it.

The full feature list, screenshots and data sources are on the Cenilko page.