WidgetCraft Community: Browse, Publish and Remix Widgets Made by Other People

The short answer

WidgetCraft's community is a remix gallery for widget designs, not a social network. You browse what other people have published, tap Use to drop one into your own library, and edit it into your version; publishing runs the same loop in reverse — from My Widgets you send a design out with a title, a description and tags. What the community surface is made of is discovery by category and sort, one-tap use, and an editable copy — there is no author identity to follow and no reply thread under a design. WidgetCraft is free, needs iOS 17 or later on iPhone or iPad, about 50 MB of storage, and is on the App Store.

Why people are actually searching for this

The query behind "WidgetCraft community" is rarely "does a gallery exist". It is three separate questions wearing one hat:

• Can I get a good design without spending an evening on layout? Somebody who can already build the thing has already built the thing.
• Is "Use" a copy or a subscription? If pulling someone's design means their server keeps serving it and their account can change it under you, that is a worse deal than designing.
• If I publish mine, what leaves my phone? A design built from photos of your family or a widget bound to your step count deserves an answer before you hit publish, not after.

Those three questions live in three different layers of the app, so it is worth taking them one at a time.

"Use" gives you a copy, not a subscription

This is the part worth being precise about. Tapping Use adds the widget to your own library and it is yours to modify into your own version. Nothing about it points back at the creator's account, and nothing about it keeps updating from wherever it came from. Your later edits do not push to the person who published it, and their later edits do not overwrite yours. You are holding a document, not a live feed pointed at someone else's server.

The document is a whole design, though — layers, not a flat picture. Image layers can come from your album, from SF Symbols, from an App Store icon, or from a URL, and text and numeric layers can bind to live data such as the system date, weather and health data. So a remix inherits the bindings, not just the look: take a health-rings layout from the community and the numbers it shows are your own, read on your own device, because the rendering happens locally. That is the honest version of the privacy claim — the design never had your data in it, and your data is read locally — and it is also why the bindings are the thing to check when you pick between two designs that look identical.

Publishing is three fields, and that shapes discovery

Publishing is deliberately small: from My Widgets, select the work, tap Publish to Community, and add a title, a description and tags. Three fields are the entire metadata surface, and that single fact explains how the community behaves. With no author name, no bio and no follower count, ranking has nothing to work with except the design itself — so you find things by sorting by popularity, by latest, or by category, and a good layout surfaces because it is good.

If your goal is an audience, this is the wrong room. If your goal is a countdown layout at eight in the morning, it is exactly the right room.

There is also a second distribution route worth knowing about, and it lives in the editor rather than the community. The editor's share menu can export the design as a .widgetcraft file, generate a QR code by uploading it, copy a share link, export a preview image, or copy the document JSON to the clipboard. That is how you hand a specific design to a specific person without going through a public list at all — the practical route when the person is sitting next to you, or when the design contains something you would rather not post publicly.

What a community widget is under the hood, and where "offline" actually ends

Most competitor pages stop at "browse and share". The mechanics are more useful than that, because they tell you what will and will not work on a bad connection.

• The gallery is a cached service, and the categories are not remote. Three catalogs are hardcoded — Featured, Home Screen and Lock Screen — and the category list is defined in the app with its titles coming from the app's own localization. Eighteen of them ship today: Trending, Photo, Dashboard, Break, Game, Countdown, Calendar, Time, Weather, Launcher, Fun, Tools, Device, News, Other, Health, Productivity and Lifestyle. Only the widget lists and the recommendations actually cross the network.
• List sizes are fixed. A category list is fetched as a single page of 100 items; a recommendation page caps at 30. There is no endless scroll here, and a category with more than a hundred designs will show you its hundred.
• The fallback order is memory, then disk, then a snapshot bundled in the app. Open the gallery on a plane and you get the bundled snapshot rather than an error screen. A normal refresh returns the cache immediately and lets the network update land behind it, which is why the list sometimes looks a beat behind what a friend just published.
• Recommendations never hand you a remote package. The server only serves designs that are already in the app's local preset pool, so tapping Use on a recommendation gives you something that was already on your phone. That is why you will sometimes recognise a "new" design.

And here is the honest limit of "every widget runs locally": a widget document can carry a data source. The editor supports an HTTP source — a URL, method, headers and a JSONPath to extract a value from the response — and a JavaScript source for transforming what comes back. A widget bound to an HTTP source needs a connection to refresh. The rendering and your data stay local; a number somebody wired to a remote endpoint does not. If a design shows a number that is not a clock, a date, weather or health reading, check what feeds it. The permissions a widget can draw on are a short, visible list — Calendar, Photos, Camera, Location, Motion & Fitness, Bluetooth and Notifications — which is worth remembering when you are deciding whether to install something a stranger made.

When the community is the wrong tool

Worth saying plainly, because "community" invites over-promising:

• If you know exactly what you want, borrowing is a detour. The same is true here as it is for the 200+ preset templates in the library — a preset is a starting point, and so is a borrowed design. Budget for editing.
• If you need a specific number, a specific font or a specific binding, no gallery will have it. The editor is where that work happens.
• If you are not on iOS 17+, it does not apply at all; the app is iPhone and iPad only, and the designs come in Small, Medium and Large for both.
• If you want your widgets to work with no signal and no exceptions, check the data bindings first, as above.

What WidgetCraft does differently

The differentiator is that the community's output is a real design document, so "remix" means more than recolouring a picture. Everything a community design is made of is editable afterwards: stack, grid and layered containers; text along an arc; images, GIFs, charts and dates; shapes; and per-layer opacity, corner radius, blur, scale, shadow, 2D and 3D rotation, brightness, contrast, saturation and hue rotation, sixteen blend modes and independent animations. Undo and redo cover the edits, the preview flips between light, dark and auto, and on iPad the layer list, preview and layer editor are visible at once in a three-column layout. There is also an AI-assisted path for starting from a generation rather than a blank canvas.

Be honest about where the weight sits, though. The social layer is thin by design — sorting, one-tap use, a copy, three fields on publish. There is no documented rating, comment or reporting surface, and the App Store listing for WidgetCraft leads with 150+ widgets and playable mini-games (2048, Sudoku, Chess, Match) rather than with the community. The library holds 200+ preset templates, and the app carries a free tier with a 4.9 user rating; the listing does not mention a paid subscription.

The decision

If what you want is a good design today without designing it, WidgetCraft's community is a legitimate shortcut — browse by category, Use the one you like, and adjust it in an editor that can do more than swap a colour. If what you want is a following, a reputation, or a design that updates itself from someone else's server, it is not that product, and no gallery page should convince you that it is.

WidgetCraft is free on the App Store: browse a category, use something, and see how far the editor takes it before you commit to building your own. If you would rather start from a preset instead, the template library covers the same ground — and the editor guide is where the real depth is.