 us where I work in the main society and what I'm going to show you is going to combine a little bit I want to take you one year back to LGM Toronto and beforehand Dave Crossland was like, hey man you got to go to this session, one session and it's like, well, Nathan's session and so turn up and what was it about? Overdive features and especially about having UI for users to control over time features. Now we're going to do a little ratio of hands also this morning who is familiar with overdive features and size of all must be specialized audience that others wake up this I'm going to show some of them anyway what can I say about it's a lot of fancy replacements inside a phone and I'll just show it's a bit put your attention to the number system for instance these are the ones we know, petal height, motor space, proportional space, lower case numbers, motor space, in good phone there's four different numbers included in it. For example somebody with wild world alternates especially if you want to go in the direction of scripted and written phones you need variation you can do this in random ways in open type also so when it went mad with ligatures maybe maybe maybe the ones for three letters so that's just Latin and that's just a small part of it which part of open type features is this getting non-Latin languages scripts to display up here is the actual data input the actual text and will always stay like that but the display writes it's built the rules are built into the phone to a lot of substitutions reordering and then some moving around to bits this is how it comes out on the screen data rendering and it's quite a lot of that and it's more than 150 different scripts are supported Latin is one of them the rest of it is the more complicated stuff actually this number can only go up this number of languages that are defined because some of these rules are really language dependent where you do the substitution or not 390 this number can only come up you know so back to Toronto it was a really cool session where like 25 people in the room which in North America means it's about half of a LGM and we were talking about it and about that must be a library that supports at the end this UI for control and it turns out the library is hard for us and that's not quite a few people is the guy at the end of that session we all thought was a good the good thing if I if I was to work on this UI concept for open type features so get started and when you start this with getting goals defined in this call to vision so I realized in the online meeting find a list where everybody is and I was sort of expecting just like in Toronto it's going to be an exercise in crowd management 25 people in online meeting oh my god so who turned up even Nathan so there's already a clue in there where where this story is going I mean it was really grateful they were there because I don't define the goals that just help that the goals come out so look let's look at the vision it's in three parts you can start reading out infrastructure generally consistently available and platforms desktop tablet handle that's three different designs it left really the direct customer are on the application developers these are value points they don't have to get all this knowledge about topography etc that's what the solution is going to provide them last part end users anyone editing any kind of rich text here's the big clue why it's actually called by this infrastructure project it's just a super general everybody does it the scope I work really hard to get this part in like these users can actually benefit where they can find some value in this super easy to just shoot down the project that's a nice fancy extra but it used to be a bit of urgency into the whole thing and that's in a successful communication bit it all together shows that get a project on the rails and define them what you want to have out doesn't take large documents so let's move on to that infrastructure and over the years I've done a couple of projects in this in this domain the first one where cut my teeth was open printing Linux printing dialogues for everyone this project did not end well exactly for infrastructure reasons but it prepared me for the next one which was Nokia duals in which I must say is by far the most successful and satisfying project in my career so that was good I'm one there and for instance last semester was teaching about student projects that came up was multi-art space a guide now that word for people to take small spaces changes into atelier for one or more persons and also makes the space the guide aspect that is an infrastructure thing I learned some rules along the way that I like to share with you here and the first rule and the second rule of infrastructure is that you just don't talk about infrastructure is another rule that actually needs enforcement nobody really wants to talk with you about infrastructure it people actively avoid you if you do they find it really good that you take care of it but don't bother them it's very good this has a however one implication that one central way how people get rewarded working in close is having an active community and getting a lot of energy from that is why it's closed off in infrastructure I've learned that the hard way that means it's really only two other ways left one is you're on the mission from God you just want to do it nobody's going to stop you or the other one is it simply work that you need to pay your bills nice work but it simply just work second aspect everything's really unfocused there are basically no use cases because there are millions of use cases they're all equally important this really upsets people in projects and there are lots of them who can only talk by the use case this is really the usual way to but also for designers in design constraints are your friend they focus you and this is not there it's everything you can think of and beyond that everywhere does it there's nothing there to help you another aspect I've put here the three large components or trademarks the traits of a trait of a design project it's a structured process this is specification and then the build is a part of the actual of the actual project if you do it well everything feeds back into each other again this is how we do it in my extrapolator for instance but it's different in infrastructure is that you're going to get a direct result out there you're going to get a library guidelines and this is the deliverable of this project to get real results that people users can touch thousands of other applications need to do the whole thing again and the results of that are first guidelines 15 to this process and then finally down there you're going to get the result I'm sitting here trying to influence that or control is a big word includes that is the right one now also not that blue eyes so though most offers just got to be killed just like that you know if I know it and there even more the guide and the library is has to put these in order one thing that I learned that is really a trait of of infrastructure is that it's about a moment that different components meet maybe one user that goes his path with a plan you got a fault with certain capabilities you got an application that defines the main and at point where the meeting time I'm actually able to say what is a good UI to actually control those open type features and I'm sitting there a year before I'm not there at that moment so a general solution that you find in infrastructure is that the one person this user that's there on the spot actually has to put things right you do that through letting them configure their user interface at that point for their own for a week the trick is to let them configure it without them noticing the last thing I want to tell you a little about infrastructure itself is taking a while to find out that because infrastructure speaks for itself that it's there of course it works and it's for everyone that everybody's thinking explicitly implicitly who should provide it that's the answer this is what's killed open printing was just a giant game of chicken between all the parties like it's going to actually pay for the work do the work etc turned out it wasn't opening its government so I could feature themselves some problems and maybe solution some point that this instead of talk about uh yeah we don't know uh there's really little support in any application for controlling this so you don't know uh or that makes that supporting them in the false themselves so very people do it is yeah it's actually very an underdeveloped area and you kind of design things for how things are right now you're going to enable capabilities and at that moment the usage is supposed to really shoot up but also the number of faults supporting it and that's the situation you've got to uh design for so don't design for where the puck is now but for where it's going there's a lot of features different features that need to be controlled you could have a black and white discussion about that is it going into the UI this feature or not a lot of backshedding or you think it shades of gray three shades of gray and you number this level one two three on the first is what implements that vision communicating text aesthetics and typography the bottom is this thing of making scripts working that you saw with the the monogamy and in the middle is what is left over so you start chopping off those 135 into regions and then you can really say okay not UI fully UI splitting of the features still too many that you have to put into UI taking out mutual slipper stuff still too many so we really have to do a still a vast reduction in the amount of stuff to show so I'm going to speed up a little bit one of the design problems that will pop up is that look at these segments they want to reflect the state is this involved in analytics the answer is partially but not at the same time it's this reflecting what is set and showing what what is going on it's going to be this is just for two things it's going to be a lot more difficulty you got a lot of selected text then there are 135 things to reflect and how to do that to add this talk what's going to happen from now on now in a way the situation is clear the situation is clear that actually the situation is difficult and it's not the design problems so I'll skip that one for you that makes it makes it difficult I love solving those problems etc but it's actually those infrastructure aspects that I talk about these forces that actually stop the project that makes all the features for everyone makes it very difficult to move forward there that's what I want to say today thank you