サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ノーベル賞
artsy.github.io
By Orta Therox Mar 17, 2019 On Valentine’s day in 2014, @alloy made our first commit moving the Artsy Mobile team to JavaScript, and paving the way to the shared Omakase JavaScript stack across web + iOS. We’ve done a write-up at 6 months, 1 year, 2 years and at 2.5 years we collaborated on a React Native conference with Facebook which features a very long Q&A session with the people who worked on
By Orta Therox Jan 5, 2019 It’s been three years, and Swift Package Manager (SPM) is at a point where it can be useful for iOS projects. It’ll take a bit of sacrifice and a little bit of community spirit to fix some holes probably but in my opinion, it’s time for teams to start adopting SPM for their 3rd party dev tools. TLDR: You should be using SPM for 3rd party dev tools like: SwiftLint, SwiftF
By David Sheldrick Nov 21, 2018 This year TypeScript gained a new feature that punches far above its weight. Working through our (enormous) backlog of unsorted TypeScript “Suggestions” and it’s remarkable how many of them are solved by conditional types. – Ryan Cavanaugh, TypeScript maintainer Conditional types probably aren’t something you’ll write every day, but you might end up using them indir
By Orta Therox Mar 17, 2018 @alloy first mentioned React Native as an option for Artsy back in March 2015, and in February 2016 he made our first commit to get the ball rolling. Since then, we’ve grown a new codebase, Emission, which has slowly taken over the responsibility for creating the UIViewControllers presented inside our iOS app. We’ve come quite far from where we started, and I was asked
By Christopher Pappas, Eloy Durán Nov 27, 2017 At Artsy we <3 TypeScript. We use it with React Native via Emission and on the web via Reaction. Until recently, however, projects that required the use of Babel had to implement convoluted tooling pipelines in order to work with the TypeScript compiler, increasing friction in an already complex landscape. (An example of this is Emission’s use of Rela
series: React Native at Artsy
By Orta Therox Jul 6, 2017 React Native is a new native library that vastly changes the way in which you can create applications. The majority of the information and tutorials on the subject come from the angle of “you are a web developer, and want to do native”. This makes sense, given that the size of the JavaScript/web audience is much bigger than native developers, and far more open in the ide
Hey there, so you’ve decided to take a look at React Native? Well, last week I ran a workshop inside Artsy on React Native and Relay. The video takes you from react-native init to having the initial structure of a View Controller based on Relay with a real working API request. The video is about 45 minutes, with inline questions. If you wanted to just run through the notes, you could probably get
As the Artsy iOS app grew larger, we started hitting pain points: We want to support other future platforms such as Android without creating more teams. We want different business teams to work on the app without disrupting each other. We want our architecture to evolve in order to increase programmer efficiency. It took us about a year to start resolving these issues. Ideally, we wanted to find a
Dependency Injection (DI) is a $25 word for a 5¢ idea, but it’s an idea that has become wholly foundation to how I write software. I want to take a look at some of the ways our team have been using DI in Swift. DI users in Swift (and Objective-C) are generally in one of a few camps: Use initializer injection to provide objects with their dependencies. Use property injection (with laziness even!).
Model View ViewModel has become the default way I write apps on iOS – it makes writing iOS apps a joy. I’ve written about it again and again and oh my. But last Autumn, as our team was all-hands-on-deck to wrap up the auctions kiosk app, we chose not to use MVVM. Why not? We were building a new app in a new language using a non-Swift framework for functional reactive programming. I was also teachi
OpsWorks is a new service from Amazon that promises to provide high-level tools to manage your EC2-based deployment. From the announcement: AWS OpsWorks features an integrated management experience for the entire application lifecycle including resource provisioning, configuration management, application deployment, monitoring, and access control. It will work with applications of any level of com
このページを最初にブックマークしてみませんか?
『Artsy Engineering』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く