Make sure to read Apple's API Design Guidelines.Specifics from these guidelines + additional remarks are mentioned below.
https://github.com/linkedin/swift-style-guideTags | swift style-guide ios |
Implementation | |
License | creative-commons |
Platform |
This style guide is different from others you may see, because the focus is centered on readability for print and the web. We created this style guide to keep the code in our books, tutorials, and starter kits nice and consistent — even though we have many different authors working on the books. Our overarching goals are clarity, consistency and brevity, in that order.
A guide to our Swift style and conventions.Use let foo = … over var foo = … wherever possible (and when in doubt). Only use var if you absolutely have to (i.e. you know that the value might change, e.g. when using the weak storage modifier).
Note that brevity is not a primary goal. Code should be made more concise only if other good code qualities (such as readability, simplicity, and clarity) remain equal or are improved. You can enable the following settings in Xcode by running this script, e.g. as part of a "Run Script" build phase.
ios style-guide styleguide naming-conventions swiftlint swiftformatA curated list of awesome iOS frameworks, libraries, tutorials, Xcode extensions and plugins, components and much more. The list is divided into categories such as Frameworks, Components, Testing and others, open source projects, free and paid services. There is no pre-established order of items in each category, the order is for contribution. If you want to contribute, please read the guide. Instabug has just released their visual repro steps feature to enable you to trace all the views that the user interacted with before a bug or a crash occured. This will help you reproduce bugs and fix them 10x faster. We highly recommend integrating Instabug’s framework as they compiled a lot of other great features like network logs and screen annotations, providing you with useful and rich data attached to each bug or crash report. Instabug is offering awesome-ios community an exclusive 15% discount on all paid plans. Go to 1 minute integration guide.
awesome swift-library swift-extensions swift-framework ios-animation ios swift-language apple-swift swift-programming objective-c-library ios-libraries arkitStyle Guide Guide is a boilerplate for creating a custom style guide for your organization's design system. It provides just enough IA and hooks to get you going. As a bonus, I've provided links to helpful resources and inspiration to help you as you create your own custom style guide. Style Guide Guide is built using Jekyll, a static site generator which works quite well for managing the content of a style guide.
Style Prototypes are a Pattern Library tool for designing in browser. Style prototyping is a technique used to create a typical instance of a design from which a final site can be assembled. Style Prototypes are a unique tool because, not only are they responsive by default (meaning your client will be able to sign off on styles they've been able to see natively on all browsers and devices), they encourage Style and Color Guide driven Style Tile and Component Guide generation. This means that after you've built out your Style Tile, you'll be on your way to having finished your Style Guide, which you need to for Style Guide Driven Design (and coincidentally takes lots of design decisions off of the shoulders of Front End Developers). You'll also never need to have someone guess at what colors they can use with a fully built out Color Guide with both hex and Sass values.
yeoman-generator web app front-end design-in-browser style-guide sassStyle Guide Guide is a boilerplate for creating a custom style guide for your organization's design system. It provides just enough IA and hooks to get you going. As a bonus, I've provided links to helpful resources and inspiration to help you as you create your own custom style guide. Gatsby Style Guide Guide is built using Gatsby, a site generator built with React.
gatsbyA cool and customizable popup style action sheet for iOS 😎
swift-library ios ios-swift ios11 menu actionsheet cocoapods carthage popmenu ios-libraryiOS Finder-style file browser in Swift 4.0 with search, file previews and 3D touch. Simple and quick to use. Import FileBrowser at the top of the Swift file.
One thing has always bothered me as a Ruby developer—Python developers have a great programming style reference (PEP-8) and we never got an official guide, documenting Ruby coding style and best practices. And I do believe that style matters. I also believe that a great hacker community, such as Ruby has, should be quite capable of producing this coveted document. This guide started its life as our internal company Ruby coding guidelines (written by yours truly). At some point I decided that the work I was doing might be interesting to members of the Ruby community in general and that the world had little need for another internal company guideline. But the world could certainly benefit from a community-driven and community-sanctioned set of practices, idioms and style prescriptions for Ruby programming.
style-guide rubocopPullToDismiss provides dismiss modal viewcontroller function like Facebook Messenger by pulling scrollview or navigationbar with smooth and rich background effect. If you update from 1.x to 2.0, see migration guide if needed.
carthage cocoapods swift-extensions swift-framework swift-library swift-language apple-swift ui ios animation awesome-swift awesome-iosThis Clojure style guide recommends best practices so that real-world Clojure programmers can write code that can be maintained by other real-world Clojure programmers. A style guide that reflects real-world usage gets used, and a style guide that holds to an ideal that has been rejected by the people it is supposed to help risks not getting used at all — no matter how good it is. The guide is separated into several sections of related rules. I've tried to add the rationale behind the rules (if it's omitted, I've assumed that it's pretty obvious).
This Emacs Lisp style guide recommends best practices so that real-world Emacs Lisp programmers can write code that can be maintained by other real-world Emacs Lisp programmers. A style guide that reflects real-world usage gets used, and a style guide that holds to an ideal that has been rejected by the people it is supposed to help risks not getting used at all — no matter how good it is. The guide is separated into several sections of related rules. I've tried to add the rationale behind the rules (if it's omitted, I've assumed that it's pretty obvious).
This style guide outlines the coding conventions of the iOS teams at The New York Times. We welcome your feedback in issues and pull requests. Also, we’re hiring.Thanks to all of our contributors.
One thing has always bothered me as a Ruby developer—Python developers have a great programming style reference (PEP-8) and we never got an official guide, documenting Ruby coding style and best practices. And I do believe that style matters. I also believe that a great hacker community, such as Ruby has, should be quite capable of producing this coveted document. This guide started its life as our internal company Ruby coding guidelines (written by yours truly). At some point I decided that the work I was doing might be interesting to members of the Ruby community in general and that the world had little need for another internal company guideline. But the world could certainly benefit from a community-driven and community-sanctioned set of practices, idioms and style prescriptions for Ruby programming.
The goal of this guide is to present a set of best practices and style prescriptions for Ruby on Rails 4 development. It's a complementary guide to the already existing community-driven Ruby coding style guide. Some of the advice here is applicable only to Rails 4.0+.
The goal of this guide is to present a set of best practices and style prescriptions for Ruby on Rails 4 development. It's a complementary guide to the already existing community-driven Ruby coding style guide. Some of the advice here is applicable only to Rails 4.0+.
Standard is a JavaScript style guide, with linter & automatic code fixer.
eslint linter style-guide static-code-analysis ecmascript javascript-standard-style code-checker code-linter code-standards code-style hint jscs jshint lintThis guide outlines best practices and naming conventions to help graphic designers and developers manage a large number of icons prepared for an iOS project. Naming an asset starts with breaking up the user interface of each screen into namespaces (or sections). Each namespace represents a logical grouping for the assets and can be used to create asset names.
guide iosStyle once, use everywhere. A Style Dictionary is a system that allows you to define styles once, in a way for any platform or language to consume. A single place to create and edit your styles, and a single command exports these rules to all the places you need them - iOS, Android, CSS, JS, HTML, sketch files, style documentation, etc. It is available as a CLI through npm, but can also be used like any normal node module if you want to extend its functionality.
style styleguide design-systems cross-platform design-tools build-system build-tool style-dictionary dictionary amazon css design properties tokens sass scss ios android react react-native style-guide
We have large collection of open source products. Follow the tags from
Tag Cloud >>
Open source products are scattered around the web. Please provide information
about the open source projects you own / you use.
Add Projects.