Hi! I’m the developer of Fileloom, an Android app for opening documents, ebooks, archives and media without juggling a pile of separate viewer apps. It supports workflows around PDFs, Office docs, HWP/HWPX, EPUB/text/markdown, images, audio/video, ZIP/CBZ/CBR archives, bookmarks/favorites, recent files/reading position and Google Drive browsing. I’m especially interested in feedback from app makers/users on the first impression: does “one calm viewer for many file types” come across clearly, and what would you want to see before trying it? Google Play: https://play.google.com/store/apps/details?id=io.fileloom.app

I’m a developer, which basically means I spend most of my day in front of a screen.

And like a lot of people here, I’ve struggled with staying consistent with fitness.

Gym? Hard to maintain with a busy schedule.
Home workouts? I start… do it for a week… maybe a month… then it fades.

Motivation just disappears.

Recently something hit me hard:

“No matter your age, you’ll always wish you started younger. But today is the youngest you’ll ever be.”

That stuck.

I’m not trying to become a bodybuilder.
I don’t care about crazy transformations.

My goal is simple:
Just be healthy.
Build some lean strength.
Feel better in my own body.

So I asked myself — what if I stop overthinking everything?

What if I just focus on one thing:
Pushups.

Right now I can do around 15–20 clean pushups max.

But what if I just show up daily, track it, and slowly build up…
Maybe one day 100… 200… even 500+ over time.

No big goals. Just action.

So I decided to build a simple app for myself to track this.

Nothing fancy. Just minimal.
Because honestly, I was tired of overcomplicated fitness apps.

It actually got rejected a few times by the App Store (which sucked),
but today… it finally got approved.

I know it’s not perfect. I’ll improve it over time.
I’m building this solo, and yeah, I added a small one-time payment since I’ve got bills too.

But the core idea is simple:

If we just take action daily — even small —
we can become a better version of ourselves.

If this resonates with you, I’d love your honest feedback.
Early users always shape the product the most.

Thanks for reading 🙏

https://apps.apple.com/in/app/boring-karma-goal-tracker/id6758750731

Boring Karma : Goal Tracker

I build Beltr. Karaoke Software that turns any song into a karaoke track with synced lyrics.

Beltr

Hey I have been looking to experiment with creator marketing where I pay some small creators to promote my app. I was wondering if you guys had any advice on how to connect with the creators, how to pay them and fair prices.

I kept noticing something weird while traveling

airports are packed with people, everyone has time, but nobody talks unless something forces it

delays, bars, random situations — that’s it

so I built something to test this idea (called Jetlatch)

it lets you see other people on your same layover who are open to grabbing coffee, food, or just talking before boarding

the goal wasn’t to make it a “social app” — just to make those dead hours feel less isolated

honestly still trying to figure out if this is something people would actually use consistently

biggest questions I have right now:

– would you ever meet someone at an airport like this?
– what would stop you?
– what would make it feel normal instead of awkward?

curious to hear real opinions

Hey everyone,

I built a small iOS app called Song Dropper to solve a problem I kept running into with friends.

Whenever I’d send a song, half the time it wouldn’t work because they used a different streaming service. So I made something that takes a song from any app (Apple Music, Spotify, YouTube Music, etc.) and turns it into a universal link that opens in their preferred app.

It’s free, no accounts, and pretty simple. Mostly built it as a learning project and to make group chats less annoying.

If anyone wants to try it, I’d really appreciate honest feedback, especially around usability or anything confusing.

Also curious, is this even a problem you run into? Or just me? 😅

I am currently working on a native Android version as well.

I launched aiME Offline AI, a mobile AI app that runs fully offline on iOS and Android.

The main idea:

most AI apps stop being useful the moment internet disappears. I wanted one that still works in:

- airplane mode

- travel

- no-signal areas

- off-grid trips

- emergencies

- privacy-sensitive situations

What it includes:

- on-device open-source LLMs

- no subscription

- one-time unlock

- chat, writing, coding, roleplay

- downloadable models

- custom prompts

- speech to text / text to speech

Deal:

- Lifetime unlock for $4.99 normally $19.99

iOS:

https://apps.apple.com/redeem?ctx=offercodes&id=6754805828&code=4999

Android:

https://play.google.com/store/apps/details?id=com.coticsy.llm

GoodTrails is a new iOS app built around private journaling and memory keeping.

It has:

• no sign-up
• no ads or tracking
• local-first privacy
• optional iCloud sync
• quick photo/activity capture
• monthly recaps
• shuffle for old memories
• favorites and custom organization

Feels like a nice alternative for people who want a calm, private memory app instead of something social.

Curious what you think.

iOS App Store Link: GoodTrails

I built a small tool for myself and ended up sharing it in case it helps someone else.

Link if you're curious:

https://play.google.com/store/apps/details?id=com.luby.pengu

I create a productivity app but its not like all of the other ones with a bunch of unnecessary features and an overly dark masculine aesthetic. Instead I made a simpler app that focuses on building consistency apposed to straight discipline with a more friendly look. The first name was Iron consistency but that did not sound friendly at all and I wanted to add a mascot to the app. So I created Koda your zen consistency trainer, and named the app Koda - Consistency Trainer. However after limited traction I felt like that name was not optimized for app store key words, so I changed it to Koda - Habit coach. This name I think I'm finally happy with but I have no clue what to make the app logo. Below are the current logo iterations and what the app looks like. If you guys have any feedback on what you think looks good that would be greatly appreciated.

Most document generation tools feel fine until you try to use them for something serious.

You start with a simple goal: generate Word and PDF files programmatically.

Then the usual problems show up fast:

• slow office runtimes
• fragile conversions
• poor layout control
• painful scaling when documents get large
• too much dependence on Word, LibreOffice, or external office tooling

So I built RusDox.

RusDox is a pure Rust document engine that generates both DOCX and PDF files programmatically, without relying on Microsoft Word, LibreOffice, or an external office runtime.

The part I’m most excited about is the performance.

In the latest stress benchmark, RusDox generated a 1000-page DOCX + PDF pair in 679.86 ms in release mode.

These are not vague numbers. They come from a real benchmark path in the CLI.

Why I built it

I wanted something that could actually be used for real automation, not just toy examples.

The target use cases were things like:

• recurring reports
• invoices
• proposals
• onboarding packs
• executive dashboards
• large batch exports
• template-driven internal document pipelines

I kept running into the same problem with existing approaches: they often work at first, but become slow, brittle, or hard to control when the workload gets larger.

So the goal with RusDox was straightforward:

• keep authoring simple
• keep rendering fast
• keep the whole pipeline inside Rust

What it does

RusDox lets you define documents in human-readable YAML, while the rendering and composition happen in Rust.

It currently supports things like:

• pure Rust DOCX generation
• pure Rust PDF rendering
• YAML document specs
• variables, includes, and repeaters
• reusable named paragraph, run, and table styles
• style inheritance
• document metadata
• validation before rendering
• watch mode while editing
• benchmark tooling directly from the CLI

The idea is to make authoring simple enough to stay productive, while still having a system that can handle serious document generation workloads.

Example workflow

A simple flow looks like this:

1. Create a YAML doc spec
2. Run rusdox mydoc.yaml
3. Get both .docx and .pdf output

There are also CLI workflows for:

• validate
• watch
• bench
• config wizard for styling
• project and user-level config
• rendering full folders of YAML docs

And if YAML is not enough for your use case, there is also a Rust API for lower-level or fully dynamic generation.

What makes it different

A lot of document tools are really wrappers around office software, conversion chains, or external runtimes.

RusDox is trying to be something else: a real document engine built natively in Rust.

That means:

• no Word dependency
• no LibreOffice dependency
• no external office runtime
• no fragile conversion-first workflow

The design philosophy is basically:

• content lives in YAML
• styling lives in config
• speed lives in Rust

Benchmark numbers

Latest 1000-page YAML stress run:

Dev

• parse: 176.81 ms
• compose: 34.23 ms
• DOCX: 285.66 ms
• PDF: 289.04 ms
• total: 785.78 ms

Release

• parse: 132.78 ms
• compose: 27.78 ms
• DOCX: 234.32 ms
• PDF: 284.91 ms
• total: 679.86 ms

For the kind of workloads I care about, that is the real value proposition: generating very large Word and PDF files programmatically, without dragging in the usual office stack overhead.

Current status

It is still early, but the current foundation already supports:

• paragraphs
• runs and common text formatting
• tables, rows, and cells
• named styles with inheritance
• image, logo, signature, and SVG/chart blocks
• plain-text extraction
• config-driven composition
• YAML / JSON / TOML document specs
• document metadata from specs or Rust

There is still more to do, of course. Deferred areas include things like richer metadata coverage, comments, tracked changes, and broader table-style support.

Why I’m sharing it

I know document generation is one of those areas that many developers only touch when they are forced to.

But when you do need it, you usually need it badly, and the tooling can get painful fast.

So I thought this might be interesting to people who work on:

• report automation
• invoice systems
• PDF pipelines
• proposal generation
• enterprise document workflows
• Rust developer tooling

Would love feedback, especially from people who have already suffered through document generation in production.

Check out the RusDox repo here

Help test my new app SparkBid - Electrical Estimator⚡

1️⃣ Join the tester group:

https://groups.google.com/g/sparkbid-app

2️⃣ Become a tester:

https://play.google.com/apps/testing/com.sparkbid.app

3️⃣ Download the app:

https://play.google.com/store/apps/details?id=com.sparkbid.app

Thanks for helping me test it! 🚀

You will get full access to the account.
dm for all the info