How I Built a Privacy-First GIF Maker That Runs Entirely in the Browser

Most online GIF makers follow the same pattern. You upload your images. They get processed on a server. You wait. And somewhere in the background, your files are stored, scanned, or logged. For many users, that’s unnecessary friction. All they want is simple: turn a few images into a GIF and move on. That observation is what led to AnimateGifMaker — a lightweight, privacy-first GIF maker that runs entirely in the browser.

Apple Guideline 3.1.2 Explained: How a Missing Link Blocked Our Subscription Release

Launching auto-renewable subscriptions on the App Store is not just a product or pricing decision. It is also a compliance milestone—and many apps only discover this when their binary gets rejected. This article documents a real rejection we encountered while submitting LingoBoard, why it happened, and how we resolved it to successfully pass App Store review. The Rejection: Guideline 3.1.2 – Business – Payments – Subscriptions During LingoBoard’s App Store submission, the app was rejected under Guideline 3.1.2, with the following message:

Growth Starts Before Marketing

For a long time, I treated growth and marketing as the same thing. More channels. More distribution. More content, ads, posts, experiments. When growth stalled, my instinct was always to look outward. What I eventually learned was uncomfortable: If a product doesn’t grow by itself, marketing only makes the failure louder. Early growth problems rarely come from traffic In early-stage products, traffic is almost never the real bottleneck. What usually breaks growth happens much earlier:

Monetization Is a Product Decision, Not a Pricing Page

When I first added monetization to my product, I treated it as a pricing problem. Monthly or yearly? $4.99 or $9.99? A clean paywall, a polished Pro page, and a subscribe button. Everything worked exactly as designed — except the revenue. Users were active. Engagement was fine. But conversion was consistently low. Nothing was “broken,” yet something was clearly wrong. It took me a while to realize the mistake: I didn’t have a monetization problem. I had a product decision problem.

How to Fix ITMS-91053: Missing API Declaration in App Store Review

Starting May 1, 2024, Apple began enforcing new App Store review requirements related to Privacy Manifests. As a result, many apps started receiving the following review warning or error during submission: ITMS-91053: Missing API declaration This issue often appears even when no recent code changes were made, which can be confusing at first. This article explains why this happens and how to fix it correctly. What ITMS-91053 Means The error indicates that your app references one or more Required Reason APIs, but does not include the required usage declaration in its privacy manifest.
Apple Reject

Why Apple Rejected My App Under Guideline 5 (Legal) in China

Apple rejected my app under App Store Review Guideline 5 – Legal, citing local regulatory requirements in mainland China related to generative AI and deep synthesis technologies. This rejection was not caused by a bug or implementation issue, but by regional legal compliance. What Apple Flagged During Review According to Apple’s review feedback, the app was associated with ChatGPT / OpenAI, which currently does not have the required permits to operate in China.
Apple Reject

Why LingoBoard Was Rejected Under Apple’s Guideline 4.0

Why the App Was Rejected (Guideline 4.0 – Design) Apple rejected the Mac version of LingoBoard under App Store Review Guideline 4.0 (Design), citing a user experience issue related to window behavior. According to the review feedback, when the user closes the main application window using the red close button in the upper-left corner, the app remains running in the background, but there is no clear way for the user to reopen the main window from the menu.