u/apoorvcode

I made Verceltics, a native iOS app for people who use Vercel and want quick project checks from mobile.

It lets you check:

• Web Analytics
• deployments
• domains
• projects
• multiple Vercel accounts

I built it because I kept opening Safari/Chrome just to check one deploy or one analytics number, and the full web dashboard felt too slow for that on mobile.

The app is open source too.

App Store: https://apps.apple.com/us/app/verceltics/id6761645656 GitHub: https://github.com/apoorvdarshan/verceltics Website: https://www.verceltics.com

I made Verceltics, an iOS app for people who use Vercel and want quick project checks from mobile.

It helps with:

• Web Analytics
• deployments
• domains
• projects
• multiple Vercel accounts

The main reason I built it was simple: opening Safari/Chrome just to check one deployment or one analytics number felt slow on mobile.

It is built for quick checks, not replacing the full Vercel dashboard.

App Store: https://apps.apple.com/us/app/verceltics/id6761645656

I made an iPhone app called Quit All for breaking habits like smoking, vaping, alcohol, porn, social media, weed, gambling, overspending, and caffeine.

Most habit trackers feel useful after you already mess up. I wanted something that helps during the craving itself.

So the main feature is SOS mode:

• start a craving timer
• swipe through GIFs and prompts
• see consequences and reasons to wait
• log relapses without losing all context
• track streaks, savings, milestones, and danger times
• use Home Screen and Lock Screen widgets to keep the streak visible

The app is free to download. Premium is optional: monthly, yearly with a 3-day trial when eligible, or lifetime.

App Store: https://apps.apple.com/us/app/quit-all-break-every-habit/id6760978934

I’m looking for honest feedback, especially on whether “SOS for cravings” makes sense as the main hook.

Small build-in-public update.

I’ve been building Verceltics, a native iOS app for checking Vercel analytics, deployments, domains, and projects from mobile.

It started as a personal itch because I kept opening Safari/Chrome just to check one deploy or one analytics number.

This week someone bought the lifetime unlock.

Not a huge number, but it felt different because it was a very narrow developer tool and a real person still decided it was worth paying for.

Current focus:

• making analytics easier to scan on mobile
• improving project/detail navigation
• keeping the app fast with cached states
• better onboarding
• keeping the repo open source

Curious how other builders think about tiny niche tools. Is it better to stay extremely focused, or keep expanding until the product feels more complete?

I built Verceltics, an open-source native iOS/iPadOS app for Vercel users.

It lets you check your Vercel projects from mobile without opening the web dashboard every time.

Current features:

• Web Analytics
• projects
• deployments
• domains
• multi-account support
• native SwiftUI interface
• StoreKit/RevenueCat purchase flow

The repo is here: https://github.com/apoorvdarshan/verceltics

I’m still polishing the app and would love feedback from people who like checking out small open-source projects.

I’ve been building Verceltics, an open-source SwiftUI app for checking Vercel projects from iPhone/iPad.

Most of the work ended up being less about the first UI and more about making the app feel native:

• SwiftUI navigation across projects, deployments, domains, and analytics
• StoreKit + RevenueCat purchase flow
• multi-account switching
• secure token storage
• loading and cached states for Vercel API data
• charts that stay readable on smaller screens
• keeping project/detail views from refetching unnecessarily

The app started as a personal tool because I kept opening Vercel in Safari/Chrome just to check one deploy or analytics number.

Code is here: https://github.com/apoorvdarshan/verceltics

Curious how other SwiftUI devs handle state restoration and API caching when moving between list/detail screens. That part took more polish than I expected.

[ Removed by Reddit on account of violating the content policy. ]

I’ve been building Fud AI, an iOS calorie tracker focused on quick food logging.

The main idea is: take a food photo, scan a nutrition label, speak/type what you ate, or add a note with the photo, then the app estimates calories/macros and logs it. It also supports BYOK, so users can bring their own Gemini/OpenAI/Claude-compatible API key instead of being locked into my backend.

A few iOS-specific things I worked on:

• Apple Health macro writing
• StoreKit subscription flow for optional Fud AI Plus
• photo + note logging
• barcode logging
• widgets / app polish
• privacy-friendly BYOK mode

I’m posting here mostly for iOS dev feedback: anything you’d improve in the onboarding, AI flow, StoreKit setup, or App Store positioning?

I’ve been working on a landing page for a small developer tool and I’m trying to make the copy less vague.

The product is for people who host on Vercel and want to check analytics, deployments, domains, and project status from their phone.

I’m unsure whether the page should lead with:

• “Vercel analytics on iPhone”
• “a mobile dashboard for Vercel”
• “check your Vercel projects from your phone”
• something more general like “developer analytics on mobile”

The narrower version is clearer, but I’m worried it may feel too small. The broader version sounds more flexible, but it also starts to feel generic.

For a niche website like this, would you rather make the first screen extremely specific, or keep it broader so more visitors understand it?

I recently shipped a small SwiftUI app for Vercel users.

The app itself is niche: it lets me check Vercel analytics, projects, deployments, and domains from iPhone/iPad. But the Swift side was the more interesting part.

Things I had to figure out:

• StoreKit + RevenueCat without making the paywall annoying
• keeping navigation state from refreshing too often
• multi-account token storage
• async API loading without making the UI feel jumpy
• charts that still feel readable on small screens
• App Store metadata, screenshots, sandbox testing, and review

The biggest lesson was that the code was only half the work. Making a narrow developer tool feel polished enough to charge for took much longer than the first working prototype.

Curious how other Swift devs handle the “small paid app” side of things. Do you usually ship subscriptions, lifetime unlocks, or keep projects free?

I’ve been building Verceltics, a small native iOS/iPadOS app for Vercel users.

The problem I started with was simple: I often wanted to check analytics, deployments, domains, or project status from my phone. The Vercel dashboard works in mobile Safari, but it felt slow for quick checks.

So I built a focused mobile dashboard instead.

Current features:

• Vercel Web Analytics with date ranges
• project, deployment, and domain views
• multi-account support
• cached analytics state when moving between screens
• open-source SwiftUI app

The part I’m still figuring out is positioning.

Should this stay focused on analytics, or does “mobile dashboard for Vercel” make more sense?

I’ve been building Fud AI, an AI calorie tracker for iOS.

The app started as BYOK: users bring their own Gemini, OpenAI-compatible, OpenRouter, or Anthropic API key, so the core app can stay free for technical users. It logs food from photos, nutrition labels, text, and voice, then estimates calories/macros.

Current App Store numbers:

• 3.6K total downloads
• 14.6K impressions
• 6.5K product page views
• 41.5% App Store conversion rate
• Around 230 active last 30 days daily average
• Day 1 retention around 32%
• Day 7 retention around 5%

The hard part now is monetization. I added an optional Plus plan for users who do not want to set up API keys, while keeping BYOK free.

Pricing I’m testing:

• $9.99/month
• $89.99/year

I’m curious how other iOS devs would position this. Should the App Store page lead with “AI calorie tracker”, “BYOK/open-source”, or “no manual food logging”? My gut says most users care about speed, not BYOK, but BYOK helps with trust and dev adoption.

Would appreciate blunt feedback on positioning, pricing, and whether this kind of app should push subscription early or stay mostly free until retention improves.

I built Fud AI, an open-source calorie tracker that uses Gemini for meal logging from photos, nutrition labels, text, and voice.

The main idea is BYOK: users can bring their own Gemini API key instead of being locked into a hosted AI subscription. The app also shows setup steps during onboarding for people who do not already have a Gemini key.

Gemini is used to turn messy food input into structured nutrition data: calories, macros, serving size, grams, and editable food details. The app keeps grams as the source of truth, but can show user- friendly serving units like slices or pieces when the model returns them.

I’m curious what people here think about Gemini for this kind of practical daily logging use case, especially around accuracy, food labels, and multilingual voice input.

I built Fud AI, a free BYOK calorie tracker.

It logs meals from photos, nutrition labels, text, or voice, but instead of forcing a hosted AI subscription, you can bring your own Gemini or OpenAI-compatible API key. Onboarding includes the steps to create a Gemini key if you do not already have one.

Features:

• Photo and nutrition-label food logging
• Text and voice meal logging
• BYOK support for Gemini, OpenAI, OpenRouter, Anthropic, and other compatible providers
• Optional paid mode for non-technical users
• Apple Health sync
• Macro tracking and AI Coach
• Custom theme colors

I know this is not a traditional server app, but the BYOK/open-source angle may be useful to people here who prefer owning the AI/API layer instead of sending everything through a closed subscription service.

I built Verceltics because I kept opening the Vercel dashboard just to check small project analytics from my phone.

It’s a native iOS app for Vercel users:

• projects
• Web Analytics
• domain quick links
• multi-account switching
• open-source code

It’s free to download, with optional Pro features. Curious if anyone here uses Vercel and would actually want this kind of mobile dashboard.

I’ve been building a small iOS/iPadOS app for a very specific problem: checking Vercel Web Analytics without opening the dashboard on a laptop.

The product is called Verceltics. It started as a personal utility because after shipping projects I usually check the same few things: visitors, page views, routes, referrers, countries, devices, browsers, and bounce rate.

What I’ve built so far:

• Native SwiftUI app
• Swift Charts for interactive analytics
• Project search
• Pull to refresh
• iPad layout
• StoreKit 2 subscriptions + lifetime option
• Vercel token stored locally in Keychain
• No backend server between the app and Vercel

The harder parts were not the UI, but handling Vercel’s analytics endpoints cleanly, keeping the token flow simple, and making the paywall not feel aggressive. Right now you can browse projects for free, and analytics are gated when you open a project.

I’m trying to build this in public instead of only posting launch updates, so I’d be curious how other builders think about pricing for small dev tools like this: subscription, lifetime, or both?

GitHub: https://github.com/apoorvdarshan/verceltics

I built a small paid product around a narrow developer workflow: checking Vercel Web Analytics from iPhone/iPad.

It’s called Verceltics. The idea is simple: if you already use Vercel Web Analytics, you can open the app and quickly check traffic, top pages/routes, referrers, countries, devices, browsers, OS, events, flags, and query params without going through the web dashboard.

Current model:

• Free: browse projects
• Paid: open project analytics
• Monthly: $4.99
• Yearly: $34.99 with trial
• Lifetime: $59.99

Tech-wise it’s native SwiftUI, uses StoreKit 2, stores the Vercel token in Keychain, and talks directly to Vercel. No backend server in between.

I’m still figuring out whether this behaves more like a small dev utility or a micro-SaaS. The main question I’m working through is pricing: for a niche developer tool, would you keep subscription + lifetime, or simplify to lifetime only?

GitHub: https://github.com/apoorvdarshan/verceltics