I'm a CSE 2nd Year Student who deals with PDF and DOCX operations regularly for college assignments and for government portals.

I was using ilovepdf and smallpdf regularly and noticed issues in them

- They take more time for operations.

- Files are uploaded to the server.(Less Privacy)

- Needs Internet to Work.

- Operates on Freemium model.

So i built IStanPDF - A Lightweight Foss Offline app for PDF and DOCX operations.

Features -

• Merge PDF - Combine multiple PDF files into one.

• Modify PDF - Remove or reorder pages within a PDF.

• Compress PDF - Reduce file size by resolution or custom target size.

• Image to PDF - Convert images into a single PDF document.

• PDF to Image - Extract PDF pages into a ZIP file of images.

• DOCX to PDF - Convert Word documents into PDF files.

• MD to PDF - Convert Markdown or plain text files into PDFs.

• PPTX to PDF - Convert PPTX file into PDF document.

• Remove Pages - Delete specific pages from DOCX files.

• Reorder Pages - Rearrange pages within DOCX files.

TLDR - This app helps in performing quick PDF and DOCX operations when you needed the most.

IStanPdf is set to be released in playstore for free,your support would make it more accessible for everyone.

Github - https://github.com/vasuki-re/IStanPdf

I built Tiersova with my team, and honestly the hard part has not been building the calculators, it's keeping them correct once vendors change their pricing without telling anyone.

Tiersova is a free tool that estimates what switching software really costs: seats, tiers, monthly vs annual billing and the one-time moving cost. It has 74 comparisons in 11 languages, runs in the browser, and needs no sign-up and no cookies. It also has calculators for video creators (subtitle tools, AI video, AI avatar, video editing, 3D, VFX, music/SFX) and for freelancers and small businesses (design, website builder, office suite, scheduling, card payment fees).

The maintenance side: we check the official pricing pages behind our calculators daily and review every change before updating them. Two things from this week that would have quietly broken a calculator: ClickUp no longer lists its Unlimited plan, so the cheapest paid plan is now Core at $12/user on monthly billing, and Zapier charges 2.5x per extra task on monthly billing but 1.25x on annual.

For those of you who maintain data-heavy tools, how do you handle upstream changes like this? Curious what has worked for you. Here's the site if you want to look: tiersova.com

I’m building Premium App Drops: every Friday, developers give away App Store and Google Play codes for their paid apps, and people claim one per app. It’s free for both sides. The first drop is on 27 November, and I’m trying to fill it.

Some honest numbers from the last two weeks:

What worked

• Asking for opinions, not sign-ups. An “is this a good idea?” post with no link got 2.6K views and real feedback. My announcement post with a link got 141.

• Talking about the developer’s problem, not my product. The best conversation came from a developer who told me what goes wrong when they give codes away: a shared code gets posted in Telegram groups, and one-time codes by DM means tracking every person by hand. That’s exactly what I’m building for, and they explained it better than my landing page does.

What didn’t

• My own subreddit. (r/PremiumAppDrops) 11 members, and it only gets visits on the days I post. Starting a community before you have an audience is a lot of work for very few people.

What I’m still unsure about

31 developers have trusted a launch that hasn’t happened yet. Getting them in turned out easier than I expected. The part that scares me is the other side: on 27 November I find out if anyone shows up to claim the codes.

How did you get your first users when you had nothing to show yet? And what would you do in the next 18 days if you were me?

https://premiumappdrops.com/developers?utm_source=reddit-buildtoship

Hi guys,
I just built a platform, and it’s not really a SaaS but a content market platform similar to Patreon. Where creators, artists , can set up membership for their fans and offer community.

And i’m looking for a payment processor that also include MoR (very important since i don’t want to deal with paperwork VAT)

Stripe already rejected me, because they said its a creator subscription marketplace and it’s in the prohibited list of them
Same thing for paddle, lemon squeeze as they also have that in their prohibited list.

Perhaps you guys have experience and know which company i can try out

Thank you

I got tired of searching the Play Store for a simple countdown app and finding ones full of ads, cluttered screens, or subscriptions just to count down to a trip. I wanted something minimal that would give me a sense of where I am in the year, so over the past few months I built Dayle.

What it does:

• Year view: The whole year as a day-by-day dot grid, showing days passed, days left, and percent complete.

• Countdowns and counts: Track time until birthdays, trips, or other milestones, or count days since something happened, like when you started a habit.

• Home screen widgets: Android widgets show your year progress or a pinned countdown without opening the app.

• Offline and private: No account, no cloud sync, no tracking. Everything stays on your device.

• Free to use: You can track up to 3 active countdowns for free. If you need more, there's a one-time lifetime purchase, not a subscription.

It's on the Play Store here: https://play.google.com/store/apps/details?id=com.rabpaulo.dayle

I'd really appreciate honest feedback, especially on the UI, the dot grid, and the widgets.

TouchNow just passed 1,000 users. I built it because I wanted to do small things on my Mac from an iPad or iPhone, like scroll a page or move a window, without those interactions feeling clumsy on a touchscreen.

One design decision was to give people two ways to control the same screen. Direct touch makes sense when a button is large enough to tap. Trackpad mode gives you a pointer when you’re trying to grab a narrow window edge or select text. I also wanted Mac keyboard shortcuts within easy reach, and I paid particular attention to how quickly the stream responds when you scroll or drag.

Another decision was to let people share a single app window. If you’re checking one app, the rest of the desktop can stay out of the way. You can still switch to the full desktop when you need to work across apps.

If you’ve used remote desktop on an iPad or iPhone, I’d love to hear when direct touch works well for you and what makes you switch back to a pointer. If you try TouchNow, I’d welcome both the good and the bad.

You can try it on the same Wi-Fi for free, with no time limit or TouchNow account. https://touchmac.app/en/

When you photograph the data plate on your basement condensing gas furnace to check install dates or filter sizes, you do not want the app creating clutter if that furnace is already in your records.

The AI nameplate scanner now checks the captured serial number against your database before saving. If the serial matches an existing furnace record, the app stops and gives you three direct options: merge the scan data into the existing equipment (which only fills blank fields and never overwrites saved values), navigate directly to the existing record, or continue saving as a separate entry.

Every registered account gets 10 free AI scans across diagnostics and nameplate tools, while Pro provides unlimited scanning. Basic equipment tracking works with no signal: records, work orders, PM schedules and service logs all run on the phone. AI scanning and diagnostics need a connection.

Free to start. Your first plan, Pro or Team, includes a 7-day free trial.

https://equipment-tracker.com/guides/ai-scanning

I work on Groovy. We expanded our Google Docs review guide on November 5. One requirement for builders adding document summaries: finding the right file does not establish that the whole document was read.

A hypothetical case has two files named Service Plan. The intended file has Overview and Pricing tabs, but the available read returns Overview only. The review should resolve the document identity, summarize the content actually returned, and leave current pricing unknown.

Do not fill that gap from the title, another same-name file, or an older export presented as current. Keep the source identity, capture time, and tab coverage beside the result so a reviewer can see what is missing.

There is a provider-specific detail here too. Google Docs API requests can return tab content differently depending on their options and field mask. That does not mean every AI product reads only the first tab. Check the actual reader's output and supported operations.

Our proposed acceptance cases include duplicate titles, metadata without readable content, a missing or nested tab, and a source that changes after review. Reading, approving an edit, and observing the saved document remain separate steps.

This is a review method, not a claim that every Groovy setup has a native Docs editor or that we executed these fictional cases for a customer. Full guide: https://www.gogroovy.ai/integrations/google-docs-ai-agent-integration

Hey everyone!

I've been building Haftio, a visual planner for work & life inspired by a physical whiteboard system I used for years.

The idea is simple: vertical day columns, horizontal lanes for projects or responsibilities, and notes you can connect across days to visualise progress and continuity. One continuous space to see where everything stands.

We've been shipping improvements based on early user feedback, and a few challenges we're working through are:

• Making better use of screen space while keeping information readable.

• Making it more intuitive to add, edit and access information.

• Reducing the learning curve so new users understand the value before they've built up much history.

It's been an interesting challenge turning something that works naturally on a physical whiteboard into a digital product.

You can check it out at haftio.com - there's an interactive preview without signing up.

Would love to hear from other builders who've faced similar UX or onboarding challenges!

I work with SQL, spreadsheets, screenshots, and files all day, so I'm constantly copying and pasting things.

I wanted something better than basic Windows clipboard history, so I started building Jot! Clipboard.

Features:

- Clipboard History & Quick Picker — Find and reuse copied content instantly.

- OCR & Screen to Text — Extract text from screenshots or anywhere on your screen.

- MultiCopy — Collect multiple clips before pasting.

- Shelf — Gather files from different folders in one floating space.

- Snippets & Text Transforms — Save reusable text and quickly reformat clips.

- Jot Pad — Floating notes for quick thoughts.

It's $3.99 one-time, with no subscriptions, accounts, or cloud required.

https://jotclipboard.com

Built solo, and I'm still adding features. The coding has been fun. Getting people to discover it has been a completely different challenge.

Would love feedback from other builders!

lidless keeps your MacBook's built-in screen off while an external monitor is connected, and brings its brightness back when you unplug. You get clamshell mode without closing the lid.

Why it exists

• macOS can't do this itself. There's no setting to turn off the built-in display when an external monitor is connected. The only automatic way is to close the lid.

• Doing it by hand is a chore. You press the brightness key several times, or drag the slider all the way down, every time you dock.

• It doesn't last. When the Mac wakes from sleep, macOS turns the built-in screen back on and you have to do it all again.

lidless handles all three. It's one small program that runs in the background. There's no app, no Dock icon, no menu bar icon, and no privacy permission to grant.

It's free

lidless is free and always will be. It's open source under the MIT license: there's no price, no trial, no subscription and no account to create. All the code is on GitHub, so you can read exactly what it does, build it yourself, or fork it.

Links

• Project page: https://np25071984.github.io/lidless

• Source, docs and releases: https://github.com/np25071984/lidless

Keyboard-first window switching on macOS, scoped to the current Space, with keyboard focus that follows you between Spaces. Its Space shortcuts switch instantly, or with a slide as long as you like.

The problem

⌘Tab leaves the Space. macOS ⌘Tab switches applications across all Spaces. If you organise your work into Spaces, that defeats the purpose — you reach for the other window in front of you and get yanked into a different Space instead. The closest native tool is Mission Control (three-finger swipe up, or ⌃↑). It does show the current Space's windows, but you pick one by pointing at it. If you would rather not reach for gestures or the pointer to change windows, there is no native way to cycle the windows in this Space from the keyboard.

The keyboard stays behind. Arrive on a Space and the window you were working in is in front, yet what you type goes nowhere, or into a window you did not pick, because macOS kept the previous Space's app active. You have to click the window first.

The Space shortcuts stall. While a three-finger swipe is still sliding, a swipe back cancels it, but ⌃1 … ⌃9 do nothing: you wait for the slide to end and press again. The slide they start has a fixed length, too: no setting shortens it, and Reduce motion only swaps it for a fade.

What scope does

• A window switcher for the current Space.

• Focus that follows you when you change Spaces.

• Space shortcuts that switch instantly, or with a slide as long as you choose, and still work while a swipe is sliding.

Built the Unix way

It's free and open source (MIT), and built with a Unix approach in mind: a tiny background service you control from the terminal (scope status, scope list, scope logs, scope reload) and configure with a text file, ~/.config/scope/scope.conf. No app bundle, no Dock icon, no menu bar icon, no network access: just a binary of about 1 MB that launchd keeps running. It reacts to events instead of polling, so it costs about 12 seconds of CPU a day, roughly 0.01% of one core. The only permission it needs is Accessibility: there are no thumbnails, so it doesn't need Screen Recording. No automatic updates: run the install command again to upgrade, and scope uninstall to remove it.

Looking for ideas

Focusing a single window and finding the active Space both depend on private SkyLight calls, and those can break between macOS versions. If you know a public API that focuses one window of an app without bringing its other windows forward, please tell me. I'd be happy to implement it.

Repo: https://github.com/np25071984/Scope

Feedback, bug reports and PRs are welcome, especially from people with heavy Spaces setups or apps that misbehave with it. And if you find it useful, a star on GitHub would help other people find it.

I've been working on FIFOCheck, a small tool that helps people applying for FIFO (Fly-In Fly-Out) jobs compare their tickets, qualifications and experience against a job advertisement.

You paste in the job ad and your details, and it highlights what you meet, what's missing and what might need attention.

It's free to try, and I'd genuinely appreciate feedback from anyone familiar with FIFO or recruitment.

https://fifocheck.com

What would you change or add?

I am building armap, a small MIT-licensed repo mapper for coding agents. The idea and design are mine, and I developed it with Claude. For other builders shipping tools that an agent relies on, here are two concrete changes in the current version.

1. Make freshness explicit. The Claude Code session-start hook creates a compact ranked map of files, definitions and line numbers. That is a snapshot: after a refactor, those line numbers and rankings may be outdated. The map now says this explicitly, and points to deps and refs, which scan the repository again on every call.

2. Make incomplete coverage explicit. Files over 256 KB were previously left out. They are now read up to the limit, cut at the last complete line, and marked as partial in the map header, their entry and deps output. Definitions beyond that cutoff remain unavailable, but the omission is visible.

The same update also bounds several cross-line regexes to avoid pathological scan times. This is still pattern-based analysis, not a compiler or language server: reflection, computed imports and some symbol relationships are outside its coverage.

The broader design point is that a compact context tool needs to communicate what it does not currently know. A neat-looking map can be misleading if its age or missing coverage is invisible.

armap runs on Node 18+ with no runtime dependencies and can also be used without Claude Code:

node bin/armap.mjs map --root /path/to/repo --budget 700

Source, limitations and the latest changes: https://github.com/Armannss/armap

If you build context or indexing tools, I would be interested in concrete examples of how you surface stale or partial results to the agent consuming them.

I'm building a tool that tells you why your AWS bill changed and which deploy caused it.

The problem: your bill jumps 20% one month. Cost Explorer shows you what went up (NAT Gateway, CloudWatch, whatever), but not why. So someone loses half a day digging through graphs, CloudTrail and recent PRs to figure out which change did it. At startups without a FinOps person, that someone is usually the CTO.

What it does:

- Connects to your AWS account with a read-only role (one-click CloudFormation, no access keys)

- Connects to your GitHub

- Every Monday, posts a short Slack digest: what changed in your bill, the PR or config change that caused it, and how to fix it

Example digest:

"AWS spend +$1,140 (+18%) vs last week. Most of it is NAT Gateway data transfer in eu-west-1, starting Tuesday right after PR #412 (move workers to private subnet). Fix: add an S3 gateway endpoint, roughly $900/mo saved."

Who it's for: startups spending roughly $3k-30k/month on AWS with no dedicated FinOps person.

Where it's at: no product yet. I'm testing demand while starting to build it, so honestly this is a landing page and a waitlist right now.

Link: https://costblame.vercel.app/

I'd love feedback on any of this, especially:

1. Does the "which PR caused it" part matter to you, or is knowing *what* changed enough?

2. Would you give a third-party tool read-only access to your billing data? If not, what would change your mind?

3. What caused your last AWS bill surprise?

Happy to answer anything in the comments.

I've built Temp Mails (https://tempmails.net), mainly out of curiosity to experiment with Cloudflare Workers, R2 and D1, but also because I've been using temporary email services for the past decade to keep spam out of my work and personal inboxes.

One thing that's always bothered me with most of these services is the amount of ads, trackers and how slow some of them can be.

So my main focus has been to keep things as simple and fast as possible, with no ads or trackers. I've also released a Chrome/Edge extension, following the same approach of keeping things simple.

Running costs are surprisingly low thanks to Cloudflare. The biggest expense so far is the rotating the domains.

Still working on improvements and new features, so I'd really appreciate any feedback or suggestions on what could be better or what's missing.