SwiftUI-Animations has no package manifest, and its gallery links 31 entries while the overview claims 25
A repository containing a variety of animations and Animated components created in SwiftUI that you can use in your own projects.
At a glance
- What is it?
- SwiftUI-Animations is a gallery of SwiftUI animations and Metal shaders, each in its own folder, meant to be copied into an app rather than installed. That design shows up in the repository itself: an Xcode project and no package manifest, a committed Finder metadata file, and a set of gallery labels that do not always match the folders they link to.
- Who is it for?
- SwiftUI-Animations is a good fit if you want a specific loader or button animation and are willing to copy the folder rather than take a dependency, because the self-contained layout is exactly what makes that safe. Three things to know before you copy anything.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 41 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Shubham0812/SwiftUI-Animations3,624 ★ · +103
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| Shubham0812/SwiftUI-Animations | 3.5k | 3.6k |
103 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
There is no package manifest, so integration is copy and paste
The repository root has an Xcode project and a source directory, and no package manifest of any kind. That is the design decision everything else follows from. Each animation lives in its own self-contained folder with all the source code needed to integrate it, which means integration is copying a folder into your own project rather than adding a dependency. The README says it twice in different ways: the overview promises that each folder carries everything you need, and the run instructions end by telling you to open any folder in the project navigator to read or copy the code. So there is no version to track and no upgrade path, which is a fair trade for a folder of view code and a real cost if you want to pick up a fix later.
# Clone the repository
git clone https://github.com/Shubham0812/SwiftUI-Animations.git
# Open in Xcode
cd SwiftUI-Animations
open SwiftUI-Animations.xcodeprojThe gallery links 31 entries and the overview says 25
The overview paragraph claims 25 plus custom animations and Metal shaders. Count the links in the gallery table and there are 31 of them, arranged in eleven rows of three, with the final row holding one entry and two empty cells. Only one of the 31 is not under the animations folder: the first row's shader entry points into a shaders directory instead, which is consistent with the claim that the collection includes Metal shaders. So the prose understates the count by six, and the table is padded to a three column grid with empty cells at the end. Neither is a problem for a reader, and both are a reminder that the numbers in an overview paragraph and the links in a hand-built gallery table drift apart unless something checks them.
Six gallery labels do not match the folder they link to
Because the gallery is a set of labels and paths written by hand, the two disagree in a handful of places. A card labelled with one wording links to a folder with another: the shuffle entry is labelled in one form and opens a folder named in another, the card viewer opens a folder named for a bank card, the cart entry opens a folder named for a cart, the item entry opens a view named for adding, the chat bar opens a folder without the space, and the signal indicator opens a folder with the name spelled without the hyphen. The GitHub mascot loader is a small one: the label uses the capitalised spelling and the folder does not. None of this breaks anything, since the link is what matters, but it does mean that searching the repository for the name you read on the page will miss roughly a fifth of the gallery.
The structure listing contains a folder the gallery never links
The project structure section prints a directory tree under the common code directory, with the animations folder annotated as holding each animation in its own folder. Reading the visible entries gives you the same list as the gallery with one addition and one omission. There is an extra folder in the tree for a second loader variant that the gallery table does not link at all, and the tree does not include the shader folder that the gallery's first entry points into. The tree also stops partway through its own listing, ending mid-name, so it cannot be used to check the full inventory either. Between the three sources, the prose count, the gallery links and the directory tree, no single one of them is a complete and consistent index of what is in the repository.
The iOS 17 floor is the real adoption cost
The requirements table has three rows and they are unusually modern: iOS 17.0 or newer, Xcode 16.0 or newer, and Swift 5.0 or newer. For a collection of pure view code that would be unremarkable, and for this one it means the newest entry point conventions are available, including the macro form of previews that the run instructions mention alongside the older provider protocol. The run instructions add one more recommendation that is not a requirement: choose an iPhone 14 or later simulator from the device picker, because the animations are the kind that look wrong on a small screen. The README does not state what happens below iOS 17. There is no fallback path described and no note about availability, so if you support older systems this repository is simply out of range rather than partially usable.
Every animation has a preview, so the app is optional
The most useful line in the run instructions is a tip rather than a step. Every view file includes a preview provider or the macro form, so you can run a single animation directly in previews without launching the app at all, by opening the file and using the preview shortcut. That turns the whole application into a convenience: it exists so you can browse, but the actual integration workflow does not require it. The full flow is still described for the browse case, four steps from cloning to tapping a card to open it full screen and interact with it. Combined with the folder layout, it means the shortest path from this repository to a working animation is clone, open one file, read it, copy it.
A Finder metadata file sits at the root
The top level listing contains a file whose name is the macOS metadata file Finder creates when you browse a folder in a file browser. It is committed alongside the licence, the readme, the contributing guide, the code of conduct, a security policy, a contributors file and a changelog. Two details in that listing are worth noting for anyone automating against this repository. The licence file is named with a markdown extension rather than the bare name that most tooling looks for, so a script that resolves licences by convention may not find it. And there is a directory whose name is an assistant tool's, which is a growing convention across repositories but not one this README mentions.
Editorial conclusion
SwiftUI-Animations is a good fit if you want a specific loader or button animation and are willing to copy the folder rather than take a dependency, because the self-contained layout is exactly what makes that safe. Three things to know before you copy anything. The floor is iOS 17 with Xcode 16, which is the real constraint if you support older systems. The gallery labels are not always the folder names, so read the linked folder rather than searching for the display name. And the project ships no package manifest, so integrating means moving files, which means owning them from then on.
Frequently asked questions
What does the SwiftUI-Animations repository contain?
More than 25 custom SwiftUI animations and Metal shaders, from loaders, toggles and buttons to interactive components and GPU effects, with each one in its own self-contained folder. The gallery table links 31 entries in total, one of which points into the shaders folder.
How do I run the SwiftUI-Animations examples?
Clone the repository, open the Xcode project, pick an iOS simulator, an iPhone 14 or later being recommended, and press Run. The app then lists every animation on its home screen, and tapping a card opens it full screen.
What are the system requirements for SwiftUI-Animations?
The requirements table asks for iOS 17.0 or newer, Xcode 16.0 or newer and Swift 5.0 or newer. The README does not describe any fallback for older systems.
Can I preview one SwiftUI animation without running the whole app?
Yes. The README says every view file includes a preview provider or the macro form, so you can open the file and use the preview shortcut to run that animation on its own, without launching the app.
How do I integrate a SwiftUI animation into my own project?
By copying its folder. The repository ships an Xcode project and no package manifest, and the README describes each animation as a self-contained folder with all the source you need, which is why the run instructions end by telling you to open a folder and copy the code.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/shubham0812-swiftui-animations)Star history chart for your README
[](https://hysenlabs.com/projects/shubham0812-swiftui-animations)Was this useful?