4d588e4a18
* Add localized label for the AI prompt status accessory view Previously, this icon would have an accessibility label matching its SF symbol key, ‘faxmachine’. * Darken status editor character count foreground color By changing it to .secondary, it gets to an APCA contrast of 61, which is a _just_ passing Bronze score for that text size. It’s still quite short of WCAG 2.1 AA at 3.3:1 (recommended is 4.5:1) * Change remaining character count color to red when < 0 * Refine remaining character count accessibility In this commit, we - Change its trait to `.updatesFrequently` - Set a localized `accessibilityLabel` - Set its `accessibilityValue` to the remaining character count - Disable user interaction (which is presumably set automatically by virtue of being enclosed in a `Menu`) * Set accessibilitySortPriority on Status editor ScrollView Previously, the traversal order placed the elements inside the `ScrollView` last. Now, they follow on from the navigation bar contents in the expected order. * Hide the AvatarView from status creation accessibility When there is only one account available, there is no functionality associated with this element, so it is considered decorative-only, and should be hidden * Set TextView placeholder’s `accessibilityValue` to placeholder text when empty This behaviour matches `UITextField` * Hide TextView custom `placeholderView` from accessibility Previously, TextView would vend two accessibility elements when the placeholder was visible. This causes needless confusion for users. Now, the TextView matches the accessible behaviour of text inputs elsewhere. * Improve accessibility of post `privacyMenu` Previously, it would be presented as `Everyone, Button`. Now, we move the visibility to its `value` and use `Visibility` for its label, in conjunction with a hint that states it `Changes post audience`. * Add `.button` trait and accessible label to emojis in `customEmojisSheet` Previously, these would all present as `image` with no description, making it very hard to discern what kind of emoji you were adding. * Change drafts sheet item type to `Button` A button with an action has a more accessible representation than a `Text` with a tap gesture. |
||
|---|---|---|
| .github | ||
| IceCubesActionExtension | ||
| IceCubesApp | ||
| IceCubesApp.xcodeproj | ||
| IceCubesNotifications | ||
| IceCubesShareExtension | ||
| Images | ||
| Packages | ||
| ci_scripts | ||
| .gitignore | ||
| .swiftformat | ||
| IceCubesApp-release.xcconfig | ||
| IceCubesApp.xcconfig.template | ||
| LICENSE | ||
| PRIVACY.MD | ||
| README.md | ||
| TERMS.MD | ||
README.md
IceCubesApp
IceCubesApp is an open source application for accessing the decentralized social network Mastodon! It's built entirely in SwiftUI, making it fast, lightweight, and easy to use.
You can connect to any Mastodon instance and browse your timeline, interact with other users, and post updates and media.
The project is split into different Swift Packages to make it easier to manage and maintain the codebase. Each package is focused on a specific aspect of the application, such as the UI, network communication, or data models. This modular approach allows for easier collaboration and ensures that the code is organized and easy to understand.
It's a great starting point for learning SwiftUI. The app covers many of the basic concepts of SwiftUI, such as building layouts, working with data, and handling user interaction. By exploring the code, you can gain a solid understanding of how to use SwiftUI in your daily life. Plus, the open source nature of IceCubesApp means that you can see how real-world applications are built and get a sense of best practices for using SwiftUI.
The architecture is straightforward MVVM for most parts, no redux on this one ;)
Please note that IceCubesApp is currently in an early stage of development and as such, there are many features that are still missing. While the app is functional and can be used to browse and interact with Mastodon, there are still many features that are planned for the future.
Thanks!
Building the project
To build the project, you need to clone the repo and create a copy of the included .xcconfig file to create your config before you can compile the project. Otherwise, you will get an error.
Here are the steps:
- Clone the repo
- In the same folder that contains the
IceCubesApp.xcconfig.template, run this command:
cp IceCubesApp.xcconfig.template IceCubesApp.xcconfig
- Fill in the
DEVELOPMENT_TEAMandBUNDLE_ID_PREFIXvalues. The first should have your Apple Team ID (which you can find by logging into the Apple Developer Portal). The latter is your domain in reverse notation or whatever you use as the prefix for your projects. - Save your changes, and then you should be able to compile the project without any issues.