u/derdak

https://preview.redd.it/8s1mswoqgr9h1.png?width=1080&format=png&auto=webp&s=c553097d81a565e09264a6a8ec49871cbe969cb1

Disclosure: I'm the developer.

App Name: Wallety

What it does: Wallety is a private, offline personal finance app for Android — track expenses, budgets, savings goals, debts, and recurring bills, all stored on your own device. No account, no cloud, no bank linking, no ads, and your data is never sold.

Key Features:

1. Private & offline — everything stays on your device (no account, no cloud, no bank linking, no ads).
2. All-in-one — multiple wallets, category budgets, savings goals, debts & IOUs, recurring/subscription tracking, split transactions, and 8 charts.
3. Home-screen widgets, CSV import, PDF reports, full backup & restore, 5 languages, and your own choice of currency.

Goal: Launch — sharing it and genuinely welcoming feedback (especially on the home-screen widgets).

Pricing: free 7-day trial with the full app, then an optional subscription. No ads.

Link: https://play.google.com/store/apps/details?id=net.orbitapps.wallety

https://preview.redd.it/bwxhlyqldh9h1.png?width=1080&format=png&auto=webp&s=2685357492ca477d845d322ae2011810986e96b2

Disclosure: I'm the developer of Wallety. 👋

A — Answer: the problem it solves Most finance apps make you hand over your bank logins and sync your financial life to their servers, and your spending ends up scattered across budgeting apps, spreadsheets, and notes. Wallety fixes both: a fully private, offline spending tracker where your data never leaves your iPhone — no account, no cloud, no bank linking, no ads — that also brings wallets, budgets, savings goals, debts, and recurring bills into one place. 2.0 is a ground-up rebuild adding debts & IOUs, split transactions, custom categories, tags, photo attachments, 8 charts, CSV import, PDF reports, backup/restore, widgets, and 5 languages.

B — Better: how it compares

• vs bank-syncing budgeting apps: most popular trackers link your bank accounts and store your financial data on their servers (typically ~$100/yr). Wallety is fully offline and manual-entry — nothing leaves your device, no account — and costs less.
• vs ad-supported expense trackers: similar offline/manual approach, but usually ad-supported with dated interfaces. Wallety is ad-free and modern, with savings goals, debt tracking, recurring catch-up, and home/lock-screen widgets.
• vs cloud aggregators (incl. ones that have since shut down): a privacy-first, no-account alternative for people who don't want their finances in the cloud.

C — Cost

• Pricing model: Subscription (auto-renewing).
• 7-day free trial (full app, no charge during trial).
• Then $59.99/year — currently 50% off → $29.99/year through June 30.
• IAP: the only in-app purchase is Wallety Pro, the subscription that unlocks full access after the trial. No free tier, no one-time/lifetime option, no ads.
• App Store: https://apps.apple.com/app/id6756968738

Happy to answer questions in the comments.

Just wanted to share my experience upgrading an Expo app from SDK 54 to SDK 56 in case it helps someone else.

My first attempt was upgrading directly from:

• SDK 54 → SDK 56

That ended up being unsuccessful and introduced a lot of issues that were hard to untangle.

What finally worked was doing it incrementally:

• SDK 54 → SDK 55
• then SDK 55 → SDK 56

That process was much smoother and easier to debug.

I also used:

• Claude Code
• the Expo upgrade/migration agent recommended in Expo Skills

Both helped a lot with dependency alignment and identifying breaking changes.

The biggest time sink ended up being a Swift 6 + Expo JSI issue on iOS. That was the main blocker during the migration and took much longer than the actual package updates.

Curious if others had similar experiences going to SDK 56.

Solo dev here working on a React Native + Expo side project and trying to figure out a folder structure and code organization that won't bite me later.

I've looked at clean architecture applied to React Native and it makes sense conceptually, but it feels like way too much overhead for a side project. Separate layers for domain, data, presentation, use cases... it adds up fast when you're building alone.

But I've also been down the "just wing it" road and ended up with a codebase I dreaded opening after 3 months.

What I'm after:

• A simple, intentional structure that scales without a full rewrite
• Easy to navigate solo, no hunting for where things live
• Works well with Expo's file-based routing (using Expo Router)
• Enough separation to avoid logic leaking everywhere, without going full enterprise

Questions for the RN community:

1. What folder structure are you actually using in your Expo projects right now?
2. Do you separate concerns (hooks, services, components, etc.) strictly or keep things colocated by feature?
3. Is clean architecture worth it at solo/side project scale, or is there a lighter pattern you prefer?
4. Any Expo-specific quirks that affect how you organize things (routing, native modules, etc.)?

Would love to see real examples if you're willing to share, even a rough folder tree in the comments would be super helpful.

Working on a side project and trying to find the sweet spot for code organization.

I've looked into clean architecture and it makes sense at scale, but it feels like overkill for a solo side project: too many layers, too much boilerplate, and honestly too much to maintain when you're moving fast.

At the same time, I've been burned before by projects that had zero structure and turned into a mess after a few months.

What I'm looking for:

• Minimal but intentional folder/file structure
• Easy to maintain solo
• Room to grow without having to refactor everything
• No over-engineering, but also no spaghetti code

A few things I'm wondering:

1. Are any of you actually using clean architecture in React projects, and is it worth it at a small scale?
2. What's your go-to folder structure for a side project you plan to maintain long-term?
3. Any patterns or conventions you swear by for keeping things sane without a heavy architecture?

Not looking for the "enterprise" answer. Just what actually works for lean, maintainable React code as a solo dev.

Wallety - Spending Tracker

Hey everyone,

Over time, I realized that most people don’t quit expense tracking because they don’t care about money.

They quit because the apps become too complicated, overwhelming, or annoying to use consistently.

That’s the main reason I built Wallety.

A — Answer

Wallety is a simple, private, and easy-to-use spending tracker focused on everyday consistency instead of complexity.

You can:

• track expenses, income, and transfers
• organize money with wallets
• set goals
• view clear spending insights
• use it fully offline

No account required. No data sharing. Everything stays on your device.

B — Better

For many people, existing finance apps can feel overwhelming for simple daily tracking.

With Wallety, the focus is different:

• faster daily input
• cleaner UI
• privacy-first approach
• no account/signup
• lightweight experience
• works offline
• flexible “wallet” concept for organizing money
• setting and tracking goals
• clear insights

The goal isn’t to become a giant finance dashboard.

The goal is to make tracking simple enough that people actually keep using it every day.

C — Cost

Wallety is free to download and try.

Optional premium upgrade:

• Weekly: $1.99
• Yearly: $59.99
• Lifetime: $29.99 one-time purchase (limited-time offer)

Play Store Link: https://play.google.com/store/apps/details?id=net.orbitapps.wallety

I’m trying to choose analytics tools for my micro SaaS and honestly the amount of hype online is making the decision harder.

Every YouTube video, Twitter thread, or blog post feels affiliate-driven, so I’d rather hear from actual founders/builders running real products.

• What are you using today?
• What made you choose it?
• At what stage did you feel you needed “serious” analytics?

Would especially love feedback from solo founders and small teams trying to stay lean.

I’m trying to choose analytics tools for my micro SaaS and honestly the amount of hype online is making the decision harder.

Every YouTube video, Twitter thread, or blog post feels affiliate-driven, so I’d rather hear from actual founders/builders running real products.

• What are you using today?
• What made you choose it?
• At what stage did you feel you needed “serious” analytics?

Would especially love feedback from solo founders and small teams trying to stay lean.

I’m trying to choose analytics tools for my micro SaaS and honestly the amount of hype online is making the decision harder.

Every YouTube video, Twitter thread, or blog post feels affiliate-driven, so I’d rather hear from actual founders/builders running real products.

• What are you using today?
• What made you choose it?
• At what stage did you feel you needed “serious” analytics?

Would especially love feedback from solo founders and small teams trying to stay lean.

I’ve been seeing a lot of YouTube videos lately about developers moving from Next.js to TanStack Start. As someone still relatively new to the JS ecosystem, it’s hard for me to tell what’s real technical improvement versus YouTube hype/content monetization.

I’d love to hear from people who actually use these frameworks in production or have serious experience with them.

• What problems with Next.js are pushing people away?
• What does TanStack Start do better in practice?
• Is this mainly a DX trend, performance thing, architecture preference, or just “new shiny tool” energy?
• Would you recommend a beginner/indie developer learn TanStack Start today, or is Next.js still the safer/default choice?

Looking for honest opinions from experienced devs rather than influencer takes.

I’ve been seeing a lot of YouTube videos lately about developers moving from Next.js to TanStack Start. As someone still relatively new to the JS ecosystem, it’s hard for me to tell what’s real technical improvement versus YouTube hype/content monetization.

I’d love to hear from people who actually use these frameworks in production or have serious experience with them.

• What problems with Next.js are pushing people away?
• What does TanStack Start do better in practice?
• Is this mainly a DX trend, performance thing, architecture preference, or just “new shiny tool” energy?
• Would you recommend a beginner/indie developer learn TanStack Start today, or is Next.js still the safer/default choice?

Looking for honest opinions from experienced devs rather than influencer takes.

I’m currently exploring tech stacks for building both web and mobile apps, and the Rails philosophy aligns strongly with my values: end-to-end freedom, ownership, simplicity, and having a complete vision of what we deliver.

For the web side, I honestly found Rails superior by far in terms of developer experience and overall coherence.

On the mobile side, Hotwire Native feels like a huge achievement. I also find it more natural to build two minimal native apps while keeping Rails responsible for most of the business logic and overall product flow.

What I’m wondering about is the offline/local-first aspect.

In many real-world mobile apps, users still need the app to function while offline, even if the backend database remains the central source of truth.

How are experienced Rails developers approaching this with Hotwire Native? Curious to hear how Rails teams are thinking about this in practice.

For people building landing pages for products (micro SaaS, mobile apps, indie products, etc.), what stack/framework are you actually using today with React?

I’ve heard a lot about Astro lately, but I’m curious what people are using in real production landing pages.

Things I care about:

• fast loading
• good SEO
• easy deployment
• simple content updates
• animations/components when needed
• not overkill for a mostly static site

Would love to hear the reasoning and tradeoffs from people shipping real LPs.

What would you recommend as the simplest and most enjoyable way for a 12-year-old to learn JavaScript today?

I’m looking for resources/platforms/projects that are:

• beginner friendly
• interactive
• fun to build with
• not overly academic
• suitable for kids/young teens

The goal is not just learning syntax, but actually enjoying coding while building small things and practicing regularly.

Could be:

• websites
• YouTube channels
• project ideas
• anything that worked well for younger learners

Would love recommendations from people who taught kids or started young themselves.

I’m building a React Native app in the personal finance space, and I’m exploring on-device AI/LLM solutions.

Offline mode is a hard requirement, so I’m specifically looking for libraries/models that can run locally on the device (iOS + Android).

The use case is helping users better understand:

• expenses
• income
• budgets
• spending habits
• financial insights

Examples:

• categorizing transactions
• answering finance-related questions from user data
• generating spending summaries
• detecting unusual spending patterns

I’d love recommendations for:

• React Native compatible libraries
• lightweight local models
• good inference runtimes
• real-world experiences/performance tradeoffs

Curious what people here are using today for on-device AI in RN apps.

I recently posted on r/SaaS asking founders about their tech stacks, and I noticed several Rails developers mentioning a setup using Rails + InertiaJS + React.

That caught my attention.

So I wanted to ask here:
Is using InertiaJS with React becoming a rising trend in the Rails ecosystem, or is it mostly a preference among some indie hackers/solo founders?

Curious to hear from people actually using it in production:

• Why did you choose it?
• What are the biggest advantages/disadvantages?
• Would you recommend it for new Rails projects?

Hey everyone,

I’m an indie developer building mobile apps for iOS and Android.

I help startups, SMBs, founders, and professionals turn ideas into real products — from concept to a fully shipped app on the App Store and Google Play.

What I can help with:

• MVP development
• iOS & Android apps
• UI implementation
• Backend/API integration
• App Store & Play Store publishing
• Fast iteration and long-term improvements

I mainly work with React Native, which allows me to build high-quality cross-platform apps quickly and efficiently.

If you have an app idea you want to bring to life, feel free to reach out. Happy to discuss ideas, validate concepts, or help you launch fast.

Hey everyone,

I’m an indie developer building mobile apps for iOS and Android.

I help startups, SMBs, founders, and professionals turn ideas into real products — from concept to a fully shipped app on the App Store and Google Play.

What I can help with:

• MVP development
• iOS & Android apps
• UI implementation
• Backend/API integration
• App Store & Play Store publishing
• Fast iteration and long-term improvements

I mainly work with React Native, which allows me to build high-quality cross-platform apps quickly and efficiently.

If you have an app idea you want to bring to life, feel free to reach out. Happy to discuss ideas, validate concepts, or help you launch fast.

I’m a solo indie developer building both mobile and web apps.

From an SEO and long-term branding perspective, I’m wondering what’s the better approach:

• Separate domain for each product
• Subdomain per product (product.mydomain.com)
• Folder under main domain (mydomain.com/product)

My main goal is to grow traffic efficiently while keeping things manageable as a solo builder. Some products may stay small, while others could become standalone brands later.

Would love to hear how SEO people and indie hackers usually approach this, and what tradeoffs I should consider.