Five web app workflows: local image tools, AI visuals and creative downloads

Winson Yang — Wed, 14 Oct 2026 01:37:48 +0000

I build five small web products: two tools for working with existing images, one for fashion visuals, one for personalized songs and one for digital pet portraits. Their interfaces use familiar words such as upload, preview and download, but those words refer to different workflows.

This walkthrough explains those differences using the products' current public behavior. It also gives readers a short checklist for evaluating an output before using or purchasing it.

Start by identifying the operation

Before choosing a tool, ask whether you need to transform an existing asset, combine several assets or generate something new. That distinction affects the input, the processing step and the output you should inspect.

Task	Starting point	Result to inspect
Community graphics	Existing artwork	Resized emote, badge or sticker
Image layout	Several existing images	One combined image
Fashion visual	Model photo and garment references	Generated clothing and scene details
Personalized song	Name, memories and an occasion	Lyrics, then an audio preview
Pet portrait	A pet photo and a style	A portrait preview, then a digital PNG

Two browser tools for existing images

Emote Resizer prepares emotes, badges, emoji and stickers for online communities. It provides platform presets, PNG and GIF workflows, generated file sizes and over-limit warnings. The resizing takes place locally in the browser. The review step is practical: check the dimensions, animation and file size against the receiving platform's requirements.

Free Image Merger has a different purpose. It combines photos side by side, vertically, in a grid or in a freestyle layout. Processing is local to the browser, with PNG, JPG and WebP export and no signup requirement. Here the review step is the composition: order, layout, spacing and whether the final combined image contains what you intended.

Both workflows start with assets you already have. They transform or arrange those inputs rather than generate new artwork.

A reference-based fashion workflow

TryOnSwap starts with a model photo and garment images. Its studio supports changing one garment, assembling an outfit and creating a fashion scene. Uploading references requires signing in; generation uses credits, with introductory credits after email verification and credit packs without a subscription.

The useful review questions are different from a resize operation. Are the garment details consistent? Is the model consistent? Does the scene match the intended presentation? A generated fashion visual is a creative concept, not a measurement of clothing size or fit.

Two creative download workflows

Songifted separates a personalized song into stages. You supply the recipient's name, occasion and memories, review the lyrics before singing, then listen to a free 45-second preview. Purchasing the full track is a later decision. Name spelling and personal details are worth checking while the output is still text; the preview then helps evaluate the musical direction.

PawMotif starts with a pet photo and a selected style. Users inspect a free portrait preview before deciding whether to buy the finished digital PNG. The delivery format matters: it is a digital download. Gallery frames are presentation mockups, so a physical print or frame requires a separate plan.

A small review checklist

Before exporting, publishing or purchasing an output, check:

The input: do you have the artwork, photo, garment reference or personal details the workflow actually needs?
The operation: are you resizing, arranging or generating?
The boundary: does processing stay in the browser, or does the workflow require an account and uploaded references?
The preview: are you looking at dimensions and file size, image details, lyrics or an audio excerpt?
The delivery: is the result an image file, a full song or a digital portrait, and is a purchase required for that result?

A successful export or a visible preview is the start of this review step. The final asset should be inspected for its intended use.

I am the builder of the products linked here. This is a product walkthrough based on their current website descriptions.

My $200/month AI tool audit: 6 subscriptions down to 2

Winson Yang — Sat, 21 Mar 2026 10:12:33 +0000

I'm a solo founder and I was subscribing to 6 AI tools: Claude, ChatGPT, Gemini, Manus, YouMind, and Spokenly. About $200/month total.

One day I realized I was spending more time deciding which AI to open than actually doing the work. So I did an audit.

The audit

For one week, I tracked every time I opened an AI tool and wrote down what I used it for. The result:

Claude: ~80% of everything
ChatGPT: ~10% (mostly quick brainstorming)
The other 4: splitting the remaining 10%

I was paying for 6 tools but really only needed 2.

What happened after I cancelled 4

Monthly cost: $200 → $40
Productivity: went UP, not down
The biggest gain wasn't the money — it was not having to think "which AI should I use for this?" every single time

When you only have 2 tools, you actually learn them properly. You build real workflows instead of jumping between 5 different interfaces.

I built a tool for this

I figured other solopreneurs probably have the same problem, so I built a free quiz: AI Stack Finder

5 questions, takes 2 minutes. It tells you which 2-3 AI tools you actually need based on your role and tasks, and how much you could save by cancelling the rest.

Tech stack: Next.js, Supabase, Vercel. The recommendation engine uses a greedy set-cover algorithm to find the minimum set of tools that covers all your tasks.

Would love to hear: how many AI subscriptions are you running right now? Have you done an audit like this?

DEV Community: Winson Yang