rcarver

TCA UI Performance Journey

A few notes on what I've learned over the past week refactoring my app to improve UI performance.

Context

The app manipulates a single large model struct. That struct gets fed into a renderer on all changes to generate an image. The UI is largely made up of sliders, which need to be very responsive. Any extra time on the main thread is noticeable (and I already throttle sliders from the view to the store at ~15fps)

Original Design

rcarver

import CustomDump
import Dependencies
import Graphiti
import GraphQL
import Vapor
import XCTest

final class DependenciesTests: XCTestCase {
    func testStatic() async throws {
        let result = try await self.resolve(

rcarver

import ComposableArchitecture
import SwiftUI

/*

 This is a proof of concept for "shared state" in The Composable Architecture.

 Goals:

 * An ergonomic way for child domains to access data provided by a parent

rcarver

import Dependencies
import Foundation
import SwiftUI

/// The things you could vary the animation on.
struct AnimationResolutionInput {
    // This makes no sense, it's an example!
    var colorScheme: ColorScheme
}

rcarver

run: build
	echo 'a\nb\nc\nd\ne' | ./go-pipeline -name a -sleep 1s | ./go-pipeline -name b -sleep 2s

build:
	go build -o go-pipeline .

rcarver

check: build test vet lint

test: start-dynamodb
	DYNAMODB_HOSTPORT=$$(docker-machine ip ${docker-machine-env}):${dynamodb-port} \
		go test ./...

vet:
	go vet ./...

lint:

rcarver

#!/usr/bin/env ruby

# A very simple script to republish all of your kits at Typekit. Just pass your
# api token as the first argument to this script.
# 
# Sign up for Typekit http://typekit.com/
# Get an api token at https://typekit.com/account/tokens

require 'net/http'
require 'net/https'

rcarver

Typekit Font Events

UPDATE: Typekit Font Events have been opensourced as WebFont Loader. Typekit's available events will be updated soon with full support for the WebFont Loader API.

---

Web fonts may be the best thing to happen to web design in years, but that doesn't mean there aren't some tricky issues to overcome. One of the most annoying things is dealing with what's become known as the FOUT or 'Flash of

rcarver

    def perform
      if payload_class.respond_to?(:before_perform)
        result = args ? payload_class.before_perform(*args) : payload_class.before_perform
        return if result == false
      end
      begin
        args ? payload_class.perform(*args) : payload_class.perform
        if payload_class.respond_to?(:after_perform)
          args ? payload_class.after_perform(*args) : payload_class.after_perform
        end

rcarver

  Scenario: Choose a free plan, then create an account
     When I go to the homepage
      And I follow "Register"
     Then I should see "Find the plan that's right for you"
     When I follow "signup-trial"
     Then I fill in "First Name" with "Joe"
      And I fill in "Last Name" with "Johnson"
      And I fill in "Email" with "[email protected]"
      And I fill in "Password" with "test"
      And I fill in "user[password_confirmation]" with "test"