Name: GOTO 2016 - 効率的なAndroidレイアウト - ダニエル・ルー (GOTO 2016 • Efficient Android Layouts • Daniel Lew)
Uploaded: 2021-01-14T06:50:50.000Z
Duration: 47 min 39 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

I've been doing Android drawup for about seven years,

first the Travel App company, the Expedia,

All right, I'm gonna give my presentation over here.

You know, you can click to engage, to rate sessions,

and ask questions, of which I will probably then answer

the questions at the end if you ask them.

Anyways, so this talks about efficient Android layouts,

and when I was writing it, what I found that

I was really interested in wasn't so much so

but the efficiency in terms of leverage that you have

as a developer, and so I started thinking about it

in the way that Archimedes was referring to, like,

how fulcrums work, where, like, if you just give him

a proper place to stand, he can move the Earth,

and so that's sort of the focus of this talk,

as a developer, because a lot of Android teams

are fairly small, and you're asked to do a lot of things.

And so in my case, it would be if you give me a

a standing desk, I will write you an Android app,

and I hope that you're not expecting me to make

any more terrible jokes this entire time,

So, this is really just kind of a mish-mash of things,

there's no narrative, so I'm just trying to cover up

any particular layout, and I think the main thing

is the simpler the ViewGroup you can get away with,

generally, the better, because the more complex ones

require a lot more maintenance, and you can run

into a lot more bugs, and so on the higher end of things,

I'd say probably RelativeLayout's one of the most complex.

ConstraintLayout is yet to be seen, but it looks like

than RelativeLayout when it's finally done.

Somewhere in the middle of there is LinearLayout,

and then down there at the bottom is FrameLayout,

which is one my favorites, because it's so simple.

And there's a lot of other views in between,

they sort of occupy the same space in Android right now,

which is that they position views relative to each other,

and RelativeLayout's sort of limited in this regard,

but it's what we've had since the beginning,

whereas ConstraintLayout is new and can do,

but there's some key problems with both of them

besides the fact that they're fairly complex.

One of them is that RelativeLayout is fairly slow,

is that it's fairly alpha-ish at the moment.

So there's alpha out on Maven central, but a few times

they've completely changed the API around, so it's not

I mean, you could play around with it now, and you could

use it if you want, but you're gonna end up with

some of that cutting-edge problems that you end up when

you're trying to experimental technology.

LinearLayout is great, stacking views vertically and

horizontally, you can distribute the weight, so this is a

simple view, so rows are stacked vertically, and then also

I'm actually fairly okay with nested linear layouts

as an opposition to RelativeLayout, and I actually,

last time I told someone this, this was like by far

the biggest question that I got, is everyone coming

to me later saying, "But I love my RelativeLayouts,

I was then that nested LinearLayouts are the worst

things in existence and so I can't believe that

SO to head off that question that I was going

to be getting on the sessions thing, is that LinearLayouts

So if you use layout wait, and you nest them pretty

deep, then they an get pretty slow, but that's only

a sometimes thing, whereas by opposition, RelativeLayout

always has to do two passes, it's always slow.

So the hope is that eventually ConstraintLayout

will be our savior and save us from the situation

of having to decide between the two of them.

But in the meantime, I think really what's most

字幕リスト動画再生

GOTO 2016 - 効率的なAndroidレイアウト - ダニエル・ルー (GOTO 2016 • Efficient Android Layouts • Daniel Lew)

sort

individual

multiple

basically