 users. Why are you missing users? You have to find them. Look at that, you don't have my notes anymore. That's more exciting for me. And more surprise for you. And you need who else said something. Over here. You need time. I cannot help you with that, sir. I believe there is a talk later this afternoon about how to build a TARDIS. Perhaps you would be interested in that, but you are in the wrong place. There are some possibilities here. Maybe you are technically superior like the Betamax, but you actually decided to charge something for your time and effort and it's a whole lot more than what the VHS player was costing. Or your Betamax only holds one hour instead of two, and so while you might make really good video displays, you're going to lose. Just because you're the best doesn't mean that you win users. You might be a lovely Dvorak keyboard, which is arguably faster, and the guy with no users is like, yeah, that sounds like a great idea. All of these things, and yet how many of you are using one? That guy. Not to be. These many things that perhaps were really good ideas and yet did not work out. And this is like just the handful of things that came to the top of mind when I made this slide. And you can see just because you've done something awesome before doesn't mean that your next project is going to be super awesome. A lot of these companies have done really successful things. Juiced was created by the founders of Skype and Kaza. So sometimes things work out. Sometimes things don't. Not how not to be the thing that you've never even heard of at all because they didn't even have enough success for you to know that they failed. That's an entire set of goals. Have you defined what success means for your project? If you don't know that, it's going to be hard to figure out what direction to go and where to lead your community or even where to find a community because if you can't tell them what you want to do, they actually might tell you what you're going to do. And that's an entire other talk for another day. Your goal might be the very basic open source goal. Fix up. You don't need the rest of this talk until that's something bigger. It might be to get an A in your class. Again, noble goal. You probably don't need a whole lot of the rest of this. But maybe your goal is more users than developers. Maybe it's to gather contributors. Maybe it's world domination in which case you're going to need a whole lot more. Maybe it's to build a TARDIS so that you can get more time to build your next project. Along the way here though, you should also be considering why you're choosing open source because that's going to mean something else for your goals and something else for what success that are highly successful for. That's what we're all about here in open source landia is community. Large projects often have designated community managers which if you ask 10 people, you will probably get 10 different definitions of exactly what a community manager is supposed to do with their day. But in many cases, it's that person or that group. It could be a group of people's job to help guide a lot of the rest of the stuff I'm going to talk about in addition to the direction of the actual project and the code roadmap. But before you can just work on community, you have to know who that is. And in a lot of cases, you actually have two communities. You have your user community and your contributor community. So when you're working out the plan for the rest of what you're going to do, you need to know who you're talking to. And sometimes, or sometimes it could be almost double the work if the Venn diagram of your users and developers has a very narrow overlap. And that might be part of your definition of success. Open source, I think a lot of the people who are working on these projects are the people who are also using them. But sometimes they are simply people who have an interest in making success for the people who do need the project. One good example is mailing lists. You probably need at least two, a user list and a contributor list. And if you think of the projects that are not yours that you are a part of in open source, they probably have even more, lots and lots of mailing lists for specific groups and so forth. I have done the majority of my work in the Fedora project which I don't actually know how many mailing lists we have. I don't think I want to know. I don't want to count. That might be an entire separate problem. You might have two blogs, one for your users and one for your contributors because the content is not necessarily of interest to both of them. What you would post on one is not going to be exciting for the other. We're actually dealing with this right now in Fedora. We launched Fedora Magazine a year or so ago and it's this constant debate about what is the right content for that. Is Fedora Magazine for the users? Is it for the contributors? Is it for both? And how you communicate matters. You have to communicate with your communities. That is pretty paramount to this whole process. Defaulting to open is hard for a lot of people. It doesn't really come naturally since about kindergarten after they stopped telling you that you had to share everything then somewhere after that you're like, no, we don't talk to each other anymore. And it gets a lot harder to collaborate. Sometimes being a dictator is the easy way to go. That doesn't mean that it's the right way to go. It's not really the open source way to go. As many smarter people have said before me, surprise is the opposite of engagement. If you are surprising your community, they are not an engaged community. When you are open with people, you avoid surprising them. You keep them in the loop. Because nothing is going to kill your new contributor's desire to participate faster than surprise. It's going to make them feel excluded. Like the opposite of community. Like they're the guys standing over in the corner of the basketball game, not actually getting the ball. Building community means talking to your community, being a part of your community, having those conversations in public, and as few as possible privately. So make it easy for them. There are all sorts of tools out there. There's IRC, obviously. They're Hyperkitty, which is a project to give you both the joys of a mailing list and the joys of a forum all at once. So if you have people who like one, it shows up in the other. And Beauty of Crossing, there are a couple of tools that do that sort of thing. So now that you've got all your community people caring, make it easy for them to continue caring. Figure out the best tools for your community. They're not the same ones for everyone. And there are endless tools. When you have contributors who are enjoying themselves, that means that they are engaged in your project. They are interested in your goals. They share your mission. That means that they're active. They're making contributions. And that's how we get back to success. That's how we get to meet your goals that you set back in the beginning. So now how do we do all that? The dirty word. We don't like to say that word around here, do we? You have to type great code and shows up to use your project. It is never, ever going to happen, which is why the title of this talk was, If You Build It, They Won't Come. Your users are not the psychic friends network. But marketing is such a dirty word. So we're going to call it cupcakes so that you don't feel uncomfortable on Sunday morning talking about marketing. We're going to talk about cupcakes because everybody likes cupcakes. There are many ingredients to your cupcake plan. It's always better to build a cupcake plan on numbers because one cup of flour and two cups of flour, not the same thing. You need to know what you're dealing with. So user information, statistics, data, know who your users are, what they need, and how you can meet those needs for them. A little bit of marketing 101. This is just, this is not an exhaustive list of your marketing tasks, but it's the basic entry level. Here's where we're going to start so that we can go find ourselves some users, some more contributors, meet your goals. You need to figure out the implementation of your plan. Which of these tasks is most important based on that data? That's where you start. And there are a lot of bad ones. But I think that inks a good job of it. First of all, it tells me what it does. I tried to find a piece of software and somebody says, oh, I think X works. And so I go to X's website and then I look at it and I'm like, I don't, I don't know if this meets my needs because there is nothing on this page that tells me what your software does. Not a single sentence. No idea. If I'm lucky, it tells me how I can go install it. And so now I'm faced with the choice of do I trust the friend who recommended X, who thinks that it probably works, or did they just want me to stop talking about my problems? Collins, under the big banner, you know where you go want to go if you are coming to be a part of the Inkscape project. It has obvious links for common tasks. I want to download it. Oh, look, there's the download link. This has pretty much everything that I want all software websites to be. Which makes sense because Inkscape is Design's software, so I would hope that the designers had kind of gotten this right. Talk about social media, which is a little more comfortable than the dirty M word, and we don't have to talk about cupcakes anymore. I really recommend that your project social media is not your social media, because at some point, ideally, you have a highly successful project, and you would like to be talking about your project, and if you would like to tweet about what your cute puppy did over the weekend, your users really don't care. And so you might as well start from the beginning and have those as separate channels. I think a lot of people make the mistake of simply talking about their project on their personal social media, which is a good thing. You know, talk about what you're working on, but your project social media and its goals and what's new in your project should be a separate channel. I think on a much larger scale, a really good recent example of this is Chris Hardwick had the Nerdist handle everywhere, and then Nerdist Industries has grown into this empire, and so finally they were like, hey, Chris, we're gonna need to go get your own handle. And so now he has, I think, at Chris Hardwick, both places, and Nerdist is for the media empire. So as a side note to that whole separation of self and project, the sentence, my opinions are my own, is kind of meaningless. So just stop putting that crap on your profile. The most important thing that you can do with your social media is to be responsible that it is there and ignore everyone who says anything about your project. There are tools to help you do this. I like Hootsuite. One of the handy things about Hootsuite is you can say, if my project is Gluster, tell me every time someone mentions Gluster. And so then every time someone rants about Gluster, you can get on there and say, oh, I see you're having a problem. I think I can help you. Here's what you should do. This just helped us. There's a fun new book. If you go over to the Expo hall, go by the no-start booth. If you have kids who are interested in Minecraft, they have a new book called Learn to Program with Minecraft, which is pretty much all the words my six-year-old wants in the world, all in one title. But the Linux instructions are specific. And I'm like, but, I mean, I could go get one and get some cables and probably get it. But the Linux box is right here. Surely we can just make this, it's just Linux. We can make this work, right? We couldn't make this work. And so we tweeted. And the guy, we found the author. There he was. He was like, yeah, working on that. There was an exchange of information. In contrast, if you ever tweet at Subway, they have no interest in your existence. They don't care whether you're eating their sandwiches or what you're doing with them. I could just go down the list of Delta. Delta will help you. If you complain about Delta, they will solve your problems on Twitter faster than calling Delta. So there's your recommendation for if you're flying back to the East Coast and you don't know how you're going to get home tonight. You just, you tweet at Delta Assist. Sorry, I could ramble about the Twitter gathering metrics. Find out what's happening. It's not going, I think we had a hundred followers last year. Now we have a hundred and two. That's like growth, right? Like one is engaging with you. Numbers are there to help you. And again, there are tools like Hootsuite that do this for you. Facebook has insights built in. There are free ways to start out before you can start paying. You can also pay Hootsuite exorbitant amounts of money to tell you more information. And finally, the social media that most of us are probably hitting on a regular basis. But there could be cases where you might need to be serving your users, your future contributors, and some other social media. For example, there are a number of countries, China in particular, that have their own social media networks. If you are creating software that primarily serves a geography that has its own social media, you should get on to that one. Or it seems like a weird place to go. Unless your ink, there might be some other social media where your people are. So be a little creative. Figure out where your people are. Go meet them there. Make it easy for them to be a part of your life out of Hootsuite. This is not any actual data. This is just what you can easily get for free out of Hootsuite. These are some of my favorite collateral pieces for the sake of having a slide that we've done for Fedora. But what I really loved about this was that this was aimed at engaging new users, which is a significant Fedora challenge at this point. We can come to scale and other Linux tests and everybody already knows what Fedora is. And either you already have used it or you're not going to use it. Like, there's only so much more engagement that we're going to reach these to South by Southwest Interactive Festival where there were a lot of photographers and musicians and designers and other people working on different things. I think there are actually a couple more in this series. And so what this did was it was not all about Fedora. It actually gave them a list of the tools that were relevant to their interest to get them interested in free software. Like, paper. Paper in 2016? Why are we doing this? But think about how long this weekend has been. And are you going to go home tomorrow and remember everybody that you saw on the exo floor and every talk and everything that you wanted to remember? Nope. Nope. You're not going to. I do a lot of confidence you want to remember later. I pick up the postcard in their booth or their brochure or at least their business card so that later I can go, oh, I wanted to know more about that. I wanted to talk to that guy. Paper still has its place in a lot of our lives even here in the future in 2016. See of open source? That we often call these successful projects now that don't have stickers. Somebody's going to ask you for them. Everybody's going to ask you for them. In fact, now I started to see in the last couple of years of conferences there are increasingly people carrying around binders like Pokemon trading cards of stickers. And they're like, oh, so I have this one that they only made for Oskon in 2013. I will trade you for your EFF sticker from last, yeah, totally. I'm at 14x hashtag. I'm at 21 shirts. Can anyone beat that? And as a step further beyond that, these are pictures from Fridays, have people post pictures of themselves wearing their Sentos t-shirts, of which there are clearly many. This is a small selection of them on conferences and booths. And you're going to have to talk to people, which sometimes is even scarier than the cupcakes, interact with people, because it doesn't help to give them a sticker with a cute character on it, and then tomorrow they don't know what that character is, which is good fairy. You could stand up here and give a talk, which is super helpful for finding new people. Tell them in your talk description, I am solving this problem. Here's how I'm doing it. Come to the talk. And I do recommend if you're not accustomed to the talk giving, to reading an assertive blog post out there about how to write your talk proposals, because I have also sat on the proposal review committees and the number of talk proposals that I have read that are, my project is good, literally. You get this. No. Think of places that are not necessarily FOSS conferences, if that is relevant to your goals. Like I mentioned, we took Fedora South by Southwest. We've gone to MakerFair and education events to reach those separate audiences that are not simply the open-source crowd that we see every day. We've gone to music events. Perhaps it's most relevant to you to hold a series of hackathons or get on meetup.com, hold meetups, talk to people. But what you're doing, show them how to do it. Do not make hour-long videos. Make short videos. Nobody wants to watch an hour of your software on YouTube. So again, all of that, not an exhaustive list. And every time I try to say marketing, it's going to come out as cupcake. People are going to be like, I don't know what you're talking about. Cake baking type of person to contribute to your project. All of these people exist. Value them. It turns out your roommate's English degree is useful as well. And you do need both of these, because in the same way that most programmers are not good designers and most designers are not necessarily good writers and like people have strengths for reason. Nobody is good at all of the things. And I doubt any of you are massive corporations, but I would like to show you we take the most shot in Florida and watching fail. So this is what happens when you don't have a good writer reviewing your work. Tell me when you spot what's wrong with this picture. It should be describing. Tell me why your project is good, why your software is good, and never mention the other ones. Because there's a tendency to like inkscape, but it does this differently. Well, now all you've done is tell me that everybody knows what inkscape is. Nobody knows what yours is. And so maybe I should just go check out inkscape. I'll hold on whether to show this, but I haven't watched this video in a lot of years and it's one of my favorites. This every time Larry Ellison said red hats and his key notes up on YouTube, Larry Ellison red hat. You are competing with or the things that you would like to be better than it's not helping your case. The slide went and that's a little distressing. Making diagrams. What's interesting is none of these tools have good websites, which I think is kind of hilarious. They're super handy. There are countless tools out there to help you do all of these things, but you are likely not a UX or UI expert. And so you should also find one of those in addition to your new writer friend, a designer friend. Your designer friend may be an expert in these things. And if anybody would like to know what that list of tools was, you can email me and I will find what the heck happened to this slide because much like all of those websites that won't tell me simply what the heck their project does, there are plenty of them that won't tell me how to use it once I have installed it to figure out what it does. One to me to this day was a piece of software that I knew did exactly what I wanted to do. I just didn't know how to make it happen. And so I went to their website and I clicked documentation and it took me to about six paragraphs about the history of why they decided to make this piece of software, which is not documentation in any way, shape or form. Again, you might have two different types of documentation. Contributor documentation. How do I help you? And user documentation. How do I use this thing that you made? Good documentation is a set and I'm not at all biased because I started out in technical documentation. Recruit people who are good at it because you know you've read bad documentation. You have tried to figure out how to do something and gone and that is really why you should not be the one writing the documentation. If you are the one closest to your project, closest to your code, closest to what you think that it's supposed to be doing, you are the last person who should be telling anybody else how to do it. You need to find somebody else to learn how to use what you have created so that they can explain to someone else how to do it because it's obvious to you. Because it's in your head. You made it. You are not your user. Find someone else to help you with that. In particular, focus on what is the first, is it terrible? You should probably fix that. One of my favorite ones, I seem to have lost several slides and I apologize, is if you go look at PHP's documentation, they do something really cool. And so you can go, you can be using the PHP documentation and go, oh, I can do that better and then you can leave a comment as to how it works better. Now, the downfall of this is there are 400 bajillion comments and nobody is going to sift through all that. So there may be a model in which some curation of the comments is useful, but I think that is super helpful on most of the pages. One way to remember is to respect your writer and your designer and your documentation person. You are a UX expert. Those people are just as important to your project as the people writing the code because everybody always thinks of their piece of the project or their piece of the company that their role and whatever they're working on is the most important. The coders say there's no software if I don't write it and the marketing people say nobody is going to know about it if I don't tell them about it and the documentation person says nobody can use it if I don't tell them how. And in a company you've got the lawyers and the HR people and all these people and everybody thinks that they're critical of the process. The reality is all of them are and all of them working together is what's going to lead you to your eventual success. And that is the thought that I would like to leave you with. So thank you for getting up on your Sunday morning and coming to hang out. Are there any questions? Any particular piece anybody wants to talk about more? Delete it. I don't know what have it. So this is the first time I've tried to use slides.com. So what I'm saying here is perhaps they could use better documentation or better code or better a whole lot of things. I thought I'd try something new so that works out well. There is a website actually specifically dedicated to showcasing good open source project website in an awesome world I would have it in my notes. My email address is Ruth at redhat.com I am really easy to find and so if I cannot pick R-U-T-H Ruth at redhat.com because my last name is spelled S-U-E-H-L-E and nobody should have to spell that. I got that address. If you email me I will find that website again and let you know what it is. And I recommend neverusingslides.com. We'd have been here about 10 more minutes if it hadn't eaten all my slides. Any other you had a question? Going to come work on the big projects you know the the Linux distributions and whatnot and even those big projects have trouble finding the good designers who are using open source tools. Red Hat has trouble hiring designers who use open source tools. But I think so one thing you could do is find go to those projects because I think that the people using those tools are also likely to be flocking to those places. Go to places like this website that hopefully I will find again someday for open source website. I talk to people on Twitter talk to people on Facebook go to I am sure I don't know but I am assuming because there's a Facebook group for everything that there's a Facebook group for open source designers. Go say hey I'm looking for help go hang out Deliberated Pixel Project I believe is the full name of people who are making free and open source art assets for games. And there are a couple of other websites that are places for people post free and open source Creative Commons license assets for whatever you need art for. Go find where the people are and say hey I got this thing going on I would love to have contributors. I saved the file as a PDF. Let's see where it went. High five to the husband if he's right. Any other questions? Write down enough for you if you care enough you will figure it out. It was since it was not Libre Office or Open Office. That makes it a short short list. But they did help me on Twitter so I don't want to I don't want to make them super angry because they did try to help me. It never did work out so it would change lines in my document like I would close it and then when I open it again things would have changed and like that is not helping especially in a spreadsheet. Does anybody have like are there things that you think that your project or a project is doing really well that you want to tell other people about? Does everybody really just want to go to In and Out for lunch? If you are going to try something oh hey look I found the rest of my slides. Babe sorry I will answer your question. Can you can you rephrase your question? I got a little excited about finding my slides. Learn how to write documentation is what you're saying. So if any projects they're going for attempting to write documentation so a good place to start is writing some and then getting feedback. Find an established project that has good documentation people available who can give you guidelines. There are plenty of style guides out there there's plenty if that's the thing that you want to learn to do is to write technical documentation while there are all sorts of books and websites about that and there are lots of communities that would be willing to help you build that skill just in the same way that if I'm a new developer I could go to OpenHatch and contribute some small you know bite-sized bugs and somebody's going to help me and works, right? So this about the success of Open Source Software and what's cool about this slide is even though I don't usually put a lot of words on slides I did this time and so you can actually just read the words that I was going to tell you about what all of these Open Source projects. So this is based on slightly older data because the book came out and I think 2012 and they studied Sourceforge up to I think it's like 2009 data but I suspect that in general the information is still good. 37% of projects were abandoned after the first release. 46% were abandoned before they even got to release. That is not a supreme rate of resounding success. That didn't go as well as I hoped. I totally know how to use software guys. And this was a list of characteristics that they found that were reflected in successful Open Source projects across the board that like I said in the beginning they had clearly defined goals. They knew what they wanted to do what problems they wanted to solve what success would look like for them. They knew what their users look like. We didn't really talk about this but a lot of companies in particular and so successful software projects in the same way create user profiles. A sample person will name her Jesse and she is probably about 25 years old and she lives in a major metropolitan area and if you're making cupcakes you go down into the details of like sometimes you get super detailed. Jesse has three cats and she likes to read books and goes mountain biking on the weekends whatever. But you can read all sorts of things about writing user profiles for trying to meet the needs of the people that you are interested in meeting. Goals, good project communication, modular architecture but when all of this came down good leader who was good at communicating the project's vision. That was the supreme single item they found that led to project success. And that means that somewhere in here we're going to have your URL. This is mortgage statistics all those is the expensive way this is results from Vitergia that we use for a lot of the Red Hat projects and it tells you things like your mailing list contributions are down 47% this week what the heck happened or you have 40 billion new Twitter followers what happened but what happened is up to you they just give you the numbers. Y'all if you see an exciting slide it wasn't there before. Be mine for creating site maps and mind maps free browser and platform combination you could want. And so just for fun here's what redhat.com looks like in links 2.8 on windows 7 user profiles likely scenario. There's the php user contributed notes. I think I might have lost that website forever which is sad because it was really good and now I'm going to spend the entire time in the airport today googling to try to find it again. Bomber. I will I will hunt it down. You email me and I will find that website because it is really cool. And what was even further interesting about it was not only was it a lot of really well web design websites it was a lot of open source projects that I'd never heard of and I was like oh oh what's that do oh that one looks good too. So again just because you made a pretty website doesn't mean anybody showing up to use it. You got to do all the rest of it too. Directions to in and out. Anyone bring cupcakes? If you really do love cupcakes there's a place about two blocks back called yummy cupcakes. I had the chocolate and vanilla. Yummy like I have pretty high cupcake standards and so it's not like the best cupcake I've ever had but it was it was yummy. We went because now you guys are just watching me ramble. Ascon Booth said to me you know what I really want I want a root beer cupcake. How come nobody makes a root beer cupcake? I'm like surely that's got to be a thing. Somebody somewhere makes a root beer cupcake. And so I googled root beer cupcakes Pasadena and I said it's two blocks away. You can go. Sadly they're not making root beer cupcakes right now but that is a thing. Give that man a cupcake. So I'm just going to start telling you features that I want. If you remember Amazon used to have this thing called listables or something where people would be like top 10 books where children are crying on page three or whatever. Like there was just a list of all the things and then you could go put that in yours though and then we'll go make weird list of all the things on yours of what I did not say about that which is if it's a sentence all right let's see if I can make one up off the top of my head. Enterprise grade tools like if you can get as many buzzwords as possible in one sentence I don't know what it does. You have told me nothing. Get rid of all of those words and write a sentence that makes sense. Have a 10 year old read it? Find out if it still makes sense. You've told me it's easy. So here's the problem of telling me it's easy. If I do this and I fail you've just called me stupid and I don't feel good about myself and I don't want to use your stuff anymore. Actually one of the like fundamental rules of documentation guys who want to write documentation is don't call things simple. Don't call them easy. Don't say this is so easy. We're than a five year old and that sucks. I don't like being dumb. I did those things. It didn't work now. What do I do? I left your website. I've gone on somewhere else. I'm putting emeralds on train tracks. I have quit software altogether and gone to open a base. I'm making cupcakes. Some emails to the Fedora Webmaster to set up Apache web server and Apache gets all these emails too and they're like, why did you hacks on my website? Because you know, you get that set up Apache. They get the emails and they're like, why did you hacks on my website? We didn't. You didn't. I would go back to web development for it in the back of my head. Raise you in something dumb. So then, but I hate when I like, I think we're so there's nothing at the bottom. I think that my browser has barfed which actually might be the case here. Like maybe it's just scrolled. Is there anything at the bottom of your website? Do you guys know what I mean? Like simple idea to keep software provenance data close to the code. A command line based utility written in Python, released under Apache 2 and is available on GitHub. So I like that you've declared a license because we didn't talk about that but declare a license. I care a little bit which one it is but I don't care a lot as long as you pick one instead of not picking one. I see a download link at the top. Super handy. Oh, we didn't talk about case studies. This is also a super awesome thing that you can do once you have enough users. Especially if so one just happened. Yeah, community manager. And so it's entirely possible that she knew this was going to happen but Facebook showed up here and gave a massive talk about how they use Gluster and with all sorts of data and it was super awesome. That's a great success story for size things or full of success stories. That's what they do. There's a lot of negotiation involved. But even for your smaller project you can, you know, if you're inkscape actually here's a really good example, Blender. Blender can say the other movies that I have long since forgotten the names of that win that competition every year. This is what people do with it. That event that does impress my 10 year old. I showed her Big Buck Bunny and I'm like, oh, look, the software used to make this is right here. You can use this right now and then maybe you can make the next Big Buck Bunny. If you guys don't know what that is, that probably sounds completely bananas, doesn't it? Have you guys seen Big Buck Bunny? Okay, good. I'm speaking at open source conferences and I work at an open source company and most of my friends are sort of nerdy vaguely in some way and then once in a while I'm like, those words made sense all of the rest of the time and now people are looking at me like, Big Butt what? We have diagrams. Does everyone think his diagrams are useful? Because I'm kind of looking at the side ways. I'm trying to read the weekly questions. Like your documentation link doesn't go to about us. Support. I can get help. You have the social media links. I can find you. When your stuff goes wrong, I know where to find you. This actually looks easier and so I'm not the best person to rate that as someone who is not you. Someone who is not the beginning of the project but someone who is successfully using it. How do you use it? Why do you use it? What are you doing with it? Not like I use Fedora to run my server that plays Minecraft for 47 children in lower California. Not that level of detail but yeah exactly what you're saying is what does it do? And I also really like features pages with screenshots because that's where I go when I'm trying to figure out like but I'm not sure if you do the one little thing that I really really wanted to do. I really like features and screenshots and not teeny tiny screenshots that only make sense if you've already installed and seen the software. It's going to make teeny tiny screenshots. At least let me click it so I can see a bigger one which is why the this slide about the UX and UI when I finally found it has that itty bitty picture of how the wireframe software works is because that's what's on their terrible website screenshots page is this itty bitty screenshot that I haven't used the software but clearly that's what it would look like at a Raspberry Pi screen size if you were making wireframes on a two and a half inch TFT. I'm full of bad ideas. You need more bad ideas. Do your wireframes on a two and a half inch screen. All right anybody else for coming you can go have in and out and cupcakes.