9 ms·
Useful iOS Things GitHub Repository
- toxik 5y agoThis is for iOS developers, maybe change the title?
- daggerdrone 5y agoThe title should be "Useful Swift Things". I assumed it would be about useful tips and tricks about using iOS on an iPhone.
- xenihn 5y agoI'd like to know what sort of "tips and tricks" you expected to be hosted inside of a Github repository.
- aYsY4dDQ2NrcNzA 5y agoPeople use GitHub to store all kinds of useful crowdsourced documents.
- sefrost 5y agoHolding down on the keyboard space bar allows you to move the cursor around.
- swiley 5y ago>Mobile OSes have an intuitive and discoverable UI. That's why they don't have man/info pages.
- read_if_gay_ 5y agoiOS has a Tips app which shows you stuff like this. Not quite a man page but the closest thing Apple is going to give users.
- SllX 5y agoYou can download manuals for most Apple products in the Apple Books store.
- read_if_gay_ 5y agoGood point, I actually forgot these existed. I guess they could be a bit more prominent.
- sidpatil 5y agoI never even knew they existed until now. So much for so-called discoverability...
- SllX 5y agoDon’t know how discoverable this would qualify it as, been a while since I setup an Apple product from new, but the Tips app does point people in the direction of it. Under the Essentials section of my phone, the HomePod section too if you’ve got one—I remember being pointed at it during setup—probably more if I went digging. Mac OS X’s Help pages ain’t too bad either when I last looked at them a year or so ago, and the Help menu is in every single application, not useful in all of them kind you, but at least the First party stuff it is. There’s not been zero effort, but it isn’t completely in your face. That said when I reviewed the help pages, pointed a new Mac user at them and told her to go nuts, she refused to look and forgot that menu was there after a while. How do you solve that? People are either curious or they aren’t, but everything a new user needs is pretty much in there if they’re inclined to learn.
- mosselman 5y agoWow, I didn't know this, thanks.
- swiley 5y agoBefore Apple decided that PC/handheld programming was only something that should be accessible to the elite most people kept scripts and small utility programs on github.
- deleted 5y ago[deleted]
- corobo 5y agoHave you not come across any of the awesome-* repos? I personally thought it was one of them but for iOS e.g. https://github.com/awesome-selfhosted/awesome-selfhosted https://github.com/awesome-selfhosted/awesome-selfhosted
- danappelxx 5y agoI applaud the effort and intent, but to be honest I think rookie iOS developers (who I believe are the intended audience) should stay away from most of this guide. Aside from typos and broken links, it also contains little hidden bites of bad practices and misinformation. Some examples (just going down the readme): > The observer pattern lets one object observe changes on another object. Apple added language-level support for this pattern in Swift 5.1 with the addition of Publisher in the Combine framework. - Apple did not add language-level support, the Combine framework is a framework - NSNotification center was added in iOS 2.0 extension ViewController: ImagePickerDelegate { func didSelect(image: UIImage?) { self.yourImageView.image = image self.dismiss(animated: true, completion: nil) } } > Good To GO - No you're not: what about error handling, permissions, etc. - There are dozens of libraries for this on Github that do the above and more, why not use them? func getDocumentDirectoryPath() -> URL { guard let url = useFileHandler.urls(for: .documentDirectory, in: .userDomainMask).first else { fatalError("Can't find path") } return url } func createFile(resourceName: String, fileExtension: String) { let fileURLProject = Bundle.main.path(forResource: resourceName, ofType: fileExtension) let folderUrl = getDocumentDirectoryPath() let fileUrl = folderUrl.appendingPathComponent("\(resourceName).\(fileExtension)") do { try useFileHandler.copyItem(atPath: fileURLProject ?? "", toPath: fileUrl.path) } catch { print(error) } } - You shouldn't fatalError in code intended to be reusable and ready to blindly "copy and paste" - print(error) doesn't exactly inspire confidence - Again, plenty of libraries exist for this (and Foundation's FileManager isn't that verbose anyway) struct User: Codable { var first_name: String var last_name: String var country: String } - You should use CodingKeys or JSONDecoder.KeyDecodingStrategy instead of snake_case - This section would benefit from a concrete example of JSON<->Codable<->JSON ...and so on. I hope I don't come off too critical here, I just think the author would be better off building something more akin to an Awesome list of links to blog posts, as opposed to a single source of truth of surface-level information where where the bar of knowledge is much higher.
- tokamak-teapot 5y agoCan you recommend a good book or other resource as an alternative please?
- stephc_int13 5y agoI never liked vendor-locked proprietary languages or tech stacks, I think it is even worse when it is from Apple. I use C/C++ on iOS and I'll abandon the platform if they ever remove the support.
- twobitshifter 5y agoThe email message call link is dead.