Swift Ipados

Open-source Swift projects categorized as Ipados Edit details
Related topics: #iOS #Swift #SwiftUI #MacOS #Watchos

Top 15 Swift Ipado Projects

  • CodeEdit

    CodeEdit App for macOS – Elevate your code editing experience. Open source, free forever.

    Project mention: Stuck with NSHostingView binding to SwiftUI view | reddit.com/r/SwiftUI | 2022-07-01

    I'm trying to use CodeEdit's SegmentedControl in my own Mac Appkit app. I'd like my app to be able to be:

  • SwiftUI-Kit

    A SwiftUI system components and interactions demo app

  • Appwrite

    Appwrite - The Open Source Firebase alternative introduces iOS support. Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!

  • free-sidecar

    Enable Sidecar on Unsupported iPads and Macs running iPadOS 13 and macOS Catalina

    Project mention: Using Universal Control and Sidecar at the same time.. | reddit.com/r/ipad | 2022-03-16
  • SlideOverCard

    A SwiftUI card view, made great for setup interactions.

    Project mention: What is your favorite SwiftUI library? | reddit.com/r/SwiftUI | 2021-12-31

    📷GitHub - joogps/SlideOverCard: A SwiftUI card view, made great for setup interactions.

  • LocationSimulator

    MacOS application to spoof / fake / mock your iOS / iPadOS or iPhoneSimulator device location. WatchOS and TvOS are partially supported.

    Project mention: I have an iPhone and I’m looking for a spoofing app but my phone ain’t jail broken, is it possible to download one? | reddit.com/r/PokemonGoSpoofing | 2022-06-12

    This works if you have a mac https://github.com/Schlaubischlump/LocationSimulator

  • SKCountryPicker

    A simple, customizable Country picker for picking country or dialing code. 🇮🇳 🇯🇵 🇰🇷 🇩🇪 🇨🇳 🇺🇸 🇫🇷 🇪🇸 🇮🇹 🇷🇺 🇬🇧

  • SwiftlySalesforce

    The Swift-est way to build native mobile apps that connect to Salesforce.

  • Scout APM

    Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.

  • DNSecure

    DNSecure is a configuration tool of DoT and DoH for iOS/iPadOS.

    Project mention: Gambling and Adult content DNS blocking using Mullvad VPN | news.ycombinator.com | 2022-07-13

    In iOS from what I know you need a configuration profile for that, I don't think it needs to be signed.

    Yes, you can make one with Apple Configurator 2, but there is also some tooling/app that may help, like:



  • SwiftFM

    SwiftFM is a Swift framework for the FileMaker Data API

    Project mention: SwiftFM | reddit.com/r/filemaker | 2022-02-22

    👉 https://github.com/starsite/SwiftFM

  • jyutping

    Cantonese Keyboard for iOS & macOS. 粵語粵拼輸入法鍵盤

  • CombineCloudKit

    🌤 Swift Combine extensions for reactive CloudKit record processing

  • BetterWeather

    The missing Apple Weather App for Mac.

    Project mention: ApiRest AfterShip website | reddit.com/r/swift | 2021-11-16
  • Duplicate-Tab

    A Safari Extension for iOS & iPadOS. 🖇

    Project mention: Duplicate Tab - New app, who dis | reddit.com/r/apple | 2022-01-02

    It comes with a variety of app icons to choose from, designed by Yannick Lung. Plus, I created a GitHub repository where you can view portions of Duplicate Tab's source code so that you know nothing weird is going on. The repository also contains answers to frequently asked questions and somewhere to post feedback.

  • RVS_BlueThoth

    A Native Swift Core Bluetooth LE Central (Client) Abstraction Driver

    Project mention: You don’t need to work on hard problems | news.ycombinator.com | 2021-08-17

    > I had one developer take 6 months to build a (relatively simple) top nav for a web app. This shouldn't have taken more than 1-2 weeks, even with a careful eye for detail.

    Oh, you mean "bikeshedding."

    Here's an example of the difference between basic quality, and High Quality:

    If you look at most of the repos for SPM modules in my portfolio[0], you'll see that the vast majority have test harnesses. I prefer using test harnesses[1].

    These test harnesses tend to be pretty damn robust apps. Many are "ready for app store" robust. A lot of folks would just publish them, "as is." I've been writing apps for a very long time. I'm fairly good at this.

    I can write a fairly good test harness, with full app capabilities, in less than a day. If I take the time to localize it, maybe add a day or so.

    Here's an example of some test harnesses[2]. Note that there are four of them. These represent the four different target environments for Apple (iOS/iPadOS, WatchOS, TVOS, and MacOS). I'll probably need to fork iOS and iPadOS, in the future, but we're not there, yet. A single codebase is still good for both.

    They test a Bluetooth framework[3].

    It probably took me around a week or so, to write each one. They are pretty damn good. I think they are all "App Store ready."

    I decided to actually go ahead, and create a set of apps, based on these[4], [5], [6].

    I spent well over a month, on each, after merging over the test harness codebases, to make them ready for the App Store. Lots of UX testing, removing code that only applied to testing, and adding "friendlier" user interface.

    I'm working on an app that I started about a year ago. Actually, I started it over ten years ago, if you include the two servers that I wrote, upon which it depends.

    One of the reasons that it has taken so long, is that I have truncated months of work, and tossed them in the garbage, because they were not the proper way to go. I have an "evolutionary design" process[7], that means this can happen. I plan for it. I've probably shitcanned three months' of work.

    Another thing that I do, is have an "always beta" approach to Quality. I maintain the product at "incomplete, but ship Quality" status for as much of the project as possible. In fact, I've been sharing it with the team, using TestFlight, since Oct 3, 2020 at 7:47 AM (I got that from the TestFlight metadata).

    That means that the app has been stable and robust enough for user testing, and approval for basic App Store release (TestFlight External Testing is a more relaxed standard, but try pushing out a crasher, and see how far that goes).

    I add localization support, accessibility, Dark Mode support, leak testing, etc., at every turn. It's very useful, because I can solicit immediate feedback from non-tech team members. It also means that the "basics" for App Store release are constantly being tested and validated.

    Even more useful, if we want to ask for money, it's dam easy. We just loop the person we're begging from, into the TestFlight External Tester pool, and they can run the app without a Marketing chaperone, or sacrifices to the demo gods. We can also get valuable feedback from them.

    It's really, really nice, and it has been, for many months.

    I feel like we are now at a "starting point." Even though it has been a fully-functioning, release-ready app for the last couple of months, it need the "MVP treatment," where the testing pool is expanded, and we start applying it to "in the wild" scenarios.

    Lots of companies use their customers as guinea pigs for the first several releases; usually by shoving baling-wire-and-duct-tape junk down their throats (and making them pay for it), before hitting their stride. It's a deliberate strategy. Some months ago, I read a post, here by a founder, declaring that "if you don't get physically sick at the quality of the code in your MVP, then you are spending too much time on the code quality."

    Basically, deliberately write garbage, and force it on your users.

    One of the reasons that I took on this project, was the founder is a friend of mine. He is running it as an NPO (501c3), and putting his own money into it. He doesn't really have much of it, to begin with. Also, more alarmingly, he didn't actually have a particularly good idea of what, exactly, he wanted the app to be. That's a recipe for disaster.

    He asked me to help him vet some development shops he was approaching, to realize his vision.

    It was eye-opening. He got a number of ridiculous quotes. I know what is necessary for this type of project (not small). For example, when one said that they'll deliver a full multi-server, multi-client app for MVP in three months (firm), upon getting a vague, hand-wavy requirements spec, it was hard for me to keep a straight face.

    After a few of these, I just got disgusted, and said "Screw this. I'll do it." I've been developing it for free, as a native iOS/iPadOS app.

    He has to pinch himself.

    [0] https://stackoverflow.com/story/chrismarshall

    [1] https://littlegreenviper.com/miscellany/testing-harness-vs-u...

    [2] https://github.com/RiftValleySoftware/RVS_BlueThoth/tree/mas...

    [3] https://github.com/RiftValleySoftware/RVS_BlueThoth

    [4] https://apps.apple.com/us/app/blue-van-clef-for-mobile/id151... (iOS -Includes Watch app)

    [5] https://apps.apple.com/us/app/blue-van-clef/id1529005127 (Mac)

    [6] https://apps.apple.com/us/app/blue-van-clef-for-tv/id1529181... (TV)

    [7] https://littlegreenviper.com/miscellany/evolutionary-design-...

  • RVS_ParseXMLDuration

    A Smart parser for xs:duration

    Project mention: Code Colocation Is King | news.ycombinator.com | 2022-02-03

    Not completely. The way that it works for me, is that I start work on a project, and, while building, I notice that some code that I'm working on is:

    1) Pretty complex, and fairly insular; and/or

    2) Possibly useful, elsewhere.

    If that's the case, I will then stop work on the main project, and take some time to extract and "genericize" the subproject. I'll usually set it up as a standalone open-source project; complete with tests and documentation.

    This may happen before I have completed the coding in the main project, or may happen as the result of a review, after the fact.

    In some cases, I very clearly need to develop a subproject before starting on the main project, or before certain milestones within that project (for example, SDKs or drivers). In that case, the timelines are completely separate.

    If you look at my GH repos, you'll see a whole bunch of these projects, including some rather strange ones, like an XML duration parser[0]. These are the types of projects that I extract.

    In some cases, I end up not using the extracted project in my main project (happens to some of my UI widgets). In that case, even though I am not using it, I still have an excellent project for the future. Here's an example[1]. I have ended up not using the spinner in my own work, as it was too obtrusive a widget, but it's nice to have it available for future projects.

    [0] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

    [1] https://github.com/RiftValleySoftware/RVS_Spinner

NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020). The latest post mention was on 2022-07-13.

Swift Ipados related posts


What are some of the best open-source Ipado projects in Swift? This list will help you:

Project Stars
1 CodeEdit 12,088
2 SwiftUI-Kit 1,857
3 free-sidecar 1,383
4 SlideOverCard 618
5 LocationSimulator 439
6 SKCountryPicker 224
7 SwiftlySalesforce 124
8 DNSecure 91
9 SwiftFM 47
10 jyutping 45
11 CombineCloudKit 43
12 BetterWeather 21
13 Duplicate-Tab 16
14 RVS_BlueThoth 10
15 RVS_ParseXMLDuration 1
Find remote jobs at our new job board 99remotejobs.com. There are 3 new remote jobs listed recently.
Are you hiring? Post a new remote job listing for free.
Static code analysis for 29 languages.
Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.