thoughtbot Build Phase #54
Flow controller Flow Controllers on iOS for a Better Navigation Control - Alberto De Bortoli
Show NExt/Previous
Responder chain
Cocoaの日々: [iOS] Responder Chain と UIViewController
The Best of iOS Development, Delivered Weekly. Free. - iOS Dev Weekly
VIPER - backronym for View, Interactor, Presenter, Entity, and Routing
Architecting iOS Apps with VIPER - Architecture - objc.io issue #13
no sound bounces at all
blood pumping
last 3 hours 30 seconds
quiet
bbq
chicken libs beans salada
pepper
massachusettes
store closes by choice
10pm
run out meat
ios dev weekly
well informed
flow controller
mvvm stack
dont really like
view hierarchy
wired
self. navigation controller
view controller
hipohesis
encapsulation
navigating into
get around
flow controller
show next
show previous
viper
only thing
create concrete objects
could work
well
mvvm
architecture
describe
top level controller
injected
dependency
application controller
instanciate with navigation controller
view controller branch
branch again
codebase
storyboards
segue
push pop vc
detail
profile
post
continuous loop
ability
discontinue
duplicating segue
initialize
children flow
could have larger flow
navigation
anything
responder
push state
responder chain
communicate
knowledge of
nice level abstraction
remove
interacting
meaningful
nicely named method
dont think
gaining
coupling
method name
user profile
communicate
tap post
user avatar
storyboard
tap post
communicate
responder chain
view model
flow controller
detail view
shadow view model
big problem
storyboard
callback
sucks
big condition
comstantize
hate that method
necessity
detail view
get away from that method
init with view model
one line
type safety
because
string checking
apple could solve segue action
stupid thing
single catch all delegate
casted
compiler
love segue
big believer
immediately
tappable
awesome
worse it
one object
profile view
post
show user profile
complete loop
no conditional
responder chain
button
jump to profile
lot of complexity
long time ago
sdk
authentication
pretty close
requirement
catch all info
ended up
create default
override method
checklist
step one
step two three
inject additional info
view controller
implement another method
additional controller
niceway
havent written
great
interesting
configurebility
nice clean way
how do we do this
pass nav controller
blindly
deep
going down
need this now
nav controller subclass
dedicate
where would you inject
hate that stupid
wrap boolean
common pattern
container
we have now
navigating into out of
animating
acting like
if storyboard
navigation controller
make vc semantic
back to nibs
no need flow controller
segue
publication
subscribers
high level
ios dev weekly
obj c tag stackoverflow
mvvm
viper
alternative
happy
outside box
i dont wanna switch to nibs
size class
coredata without managed object
boiler plate
nibs good
storyboard better
know reason not use storyboard
love to hear
no one disagree
hate mail
terrible reason itunes
