r/iOSProgramming • • Jan 14 '18

I got tired of searching for the same basic information over and over, so I made iOS Ref, a reference website for iOS developers. It has device resolution tables, iOS compatibility information, a hex code to UIColor converter, and a Swift cheatsheet, all on one clutter-free location.

https://iosref.com/
263 Upvotes

33 comments sorted by

16

u/eugeniu Jan 14 '18

The goal of iOS Ref is not to provide information that isn’t available anywhere else, it is to make the most important iOS developer info and web tools accessible as quickly as possible. I just started this website this week, so I’m still working on adding and removing content. But over time, I hope to make it a stable location where you can consistently find important information. I’m definitely looking for feedback so please let me know what you think should be added or removed!

22

u/aepryus Jan 15 '18

2

u/eugeniu Jan 15 '18

These are really great suggestions. I was thinking of adding a Swift functional programming and closure cheatsheet/reference page, but a page specifically for Swift closures makes a lot of sense. NSDateFormatter would be great too, that class drives me crazy, but I totally forgot about it!

8

u/kevinios Swift Jan 15 '18

Great list! I would add WTF Auto Layout: www.wtfautolayout.com

3

u/dakine_developer Jan 15 '18

So much WTF resolved with this...

1

u/eugeniu Jan 16 '18

Hey /u/aepryus, today I added Swift functions and closures quick reference pages and I was wondering what you think of them.

2

u/aepryus Jan 16 '18

These look great. Thanks for working on all this.

2

u/somebunnny Jan 15 '18

That’s pretty funny. I don’t have a list of sites like you, but I’ve been to every one on your list multiple times.

5

u/matschmid Jan 14 '18

This is great, would love to help contribute content to the cheat sheet if you’re looking for more!

5

u/eugeniu Jan 14 '18

Thanks! I'm worried about making the Swift cheatsheet too long, and kind of stretching the definition of a "cheatsheet", but I'd like to make other cheatsheets, like one for arrays, functional swift, etc. What kind of other cheatsheet would you like to see?

1

u/matschmid Jan 14 '18 edited Jan 14 '18

Off the top of my head, dictionaries and threading would be useful to have added to the cheat sheet. Maybe also link to an app icon image resizer (I like this one) and Podfile formatting guidelines

2

u/eugeniu Jan 14 '18

Both of those sound like a good idea. I was thinking of building my own icon resizer too, but the site is completely static right now, and I think this would necessarily involved some server-side work. So it's something I'm thinking through on how to incorporate.

4

u/brendan09 Jan 14 '18

May I suggest adding: http://iosfonts.com

You could also build your own implementation from the open source data set: https://github.com/mcritz/iosfonts/blob/master/data/iosfonts.json

It's good to know what OS versions the font you pick is available on, if you're deviating from System.

1

u/eugeniu Jan 15 '18

Interesting, I don't usually work with custom fonts so I didn't know about this site. I added it as a link for now.

3

u/piotrnowicki Jan 15 '18

Things made of anger are the best.

1

u/eugeniu Jan 15 '18

I know, right?

2

u/[deleted] Jan 15 '18

Lovely website, many thanks!

I'd like to suggest you to add ProMotion (120Hz) and iPads on the display tech page :)

1

u/eugeniu Jan 15 '18

That's a good idea, added!

2

u/[deleted] Jan 15 '18

Awesome, thanks!

1

u/well___duh Jan 14 '18

Why does your hex->UIColor converter take 7 characters? Just thought that was an odd character limit, it made me think it could take an alpha value (allowing for 8 characters) but it stops at 7.

4

u/eugeniu Jan 14 '18

Ah the limit is in case anyone enters a # before the hex code, such as #ffaa00.

2

u/mobilecode Swift Jan 14 '18

Mine goes to 11.

1

u/[deleted] Jan 14 '18

I like this idea.

1

u/eugeniu Jan 14 '18

Thanks :)

2

u/busymom0 Jan 14 '18

Good shit mate! Useful!

2

u/uradox Swift Jan 15 '18

Simple, but nice. I like it :)

2

u/iLearn4ever Swift Jan 17 '18

This is a wonderful idea. And it finds its place directly on my Bookmarks bar (and not some sub-folder). Will comment later with suggestions when they come to my head.

1

u/UIvapor Jan 15 '18

Awesome idea/work! Would you be opposed to adding a link to a color palette generator in the hex converter page? I use coolors.co

1

u/OlegPRO991 Nov 09 '25

Hey, iosref does not work now, or is not updated anymore. Did you stop updating it?

0

u/[deleted] Jan 15 '18

[deleted]

1

u/eugeniu Jan 15 '18

Thanks for your feedback :)

0

u/[deleted] Jan 15 '18

[deleted]

1

u/eugeniu Jan 16 '18

That's a good point, maybe I should change it to use forEach. However, forEach and for-in are not the same. In forEach, the loop block is a closure, while it isn't in for-in. That means that you can't use continue and break in the loop if you use forEach. Furthermore, if you use return in for-in, it will return the function, while if you use return in forEach, it will only return the closure.

Personally I use continue and break a lot, so I tend to stick with for-in, but as a new Swift user, it's probably a good idea to use forEach by default, and for-in when necessary.

There may also be performance difference between the two, but I'm not sure how significant that is.

1

u/GenitalGestapo Jan 15 '18

They're basically equivalent, but there are scenarios where you'd use one over the other. There's no general rules that says one is preferred over the other.