Thank you for joining us for Developing Mobile Apps from IDEA to Launch. This is a case study today that we will be discussing the Safe Night app that was created by TechSoup and Aid Matrix. So I'm going to go ahead and introduce our presenters. We are joined today. Again, my name is Becky Wiegand and I am the Interactive Events Producer here at TechSoup. I'll be the facilitator for today's webinar. We also have Anna Geiger who is the CTO of Caravan Studios which is a division of TechSoup. She will be presenting about the app process that we used in-house here at TechSoup. And then we also have Keith Bode who is the COO of Aid Matrix. And he will be talking about his contributions to developing this app as well. Hopefully this will allow you to come away with some great insights into the process or possible processes for developing your own app and understand a little bit about what it takes to put a real app together for your mobile audiences. You will see assisting with chat, Ali Bazdikian on the back end. So she will be grabbing your questions and saving them for us for the presentation Q&A. Today's agenda we will cover some introductions of both TechSoup and Caravan Studios, one of our divisions, as well as Aid Matrix. We'll take a little bit of time to pull you on what your needs are and what you're considering with mobile app development. And then we'll go into the meat of the program which we'll be talking about safe night and how the process and the app and the why of developing an app for nonprofits. And then we'll share some lessons learned and best practices and have time for Q&A. So who is TechSoup? TechSoup is a part of TechSoup Global and we are working toward today when every nonprofit, library, and social benefit organization on the planet has the technology, knowledge, and resources they need to operate at their full potential. What that means is we are a 501c3 nonprofit organization as well and so we are looking to serve other nonprofits and libraries with donated technology donations, technology products, and also provide the resources with how to use them once you have them. So today's event will largely talk about our own internal process for how we developed our mobile app in the hopes that that will provide some insight for any process that you might undertake at your organization. We launched a new website earlier this year so if you haven't visited us please join us at TechSoup.org to learn more about our work. I'd like to turn it over to Anna Yeager just to introduce a little bit about Caravan Studios which is a division of TechSoup to talk a little bit about the work that they do. Anna, welcome to the event. Thanks Becky. Hi, I'm Anna Yeager. And Caravan Studios, as Becky said, is a division of TechSoup Global. We started this project earlier this year to try some new things. And we are in the process of building about four or five different apps at the moment and some web-based products as well. And we really believe in working with community to design responses to their issues. So it's not just stuff coming out of our heads. It's not coming from the technical side. It's really coming from nonprofits. We work with them in sessions called Generators to get ideas about what are their most troubling problems right now. Not their technology problems, forget about technology, but what are the issues that keep them up at night? And we discuss these in sessions that we call Generators to look for opportunities for technical intervention. Then we go through our process here that will hopefully end in a solution and use of the software. And SafeNight, which we are talking about today, is in between the build and use phase right now on our slide. And AID Matrix has definitely been a huge partner. They are actually doing the building of this app for us. We are the nonprofit folks, and they are the technology folks. So I'll let Keith go ahead and introduce himself. Thank you. So AID Matrix is a nonprofit organization as well and a long-standing partner of TechSoups.  The background for AID Matrix and the idea is that the for-profit world has developed these processes and technologies that really raise the standard of living of most of society. How can you take maybe those same technologies and processes and apply them to people who have been left behind or affected by a tragedy, whether that is a disaster or a personal tragedy? So we try to tap into those capabilities and those capacities and make them relevant to the social sector. And this was a great partnership for us because I think we were able to bring some capabilities from a technology side and the corporate side to then partner up with TechSoup who has such a, particularly in this area has such a strong intimate understanding of the community and the challenges there. And we found that the marrying of the two is a great team to take this project forward. Great. Thanks so much for that, Keith. So today's webinar is really intended to be a case study, not to be self-promotional on our own app. We don't want you to go and download our app and use it. It's really for us to just share how it works for us, give you some best practices, and to talk about how we really came up with the idea and how we implemented that into a solution that would really achieve some of the goals. So we'll talk a little bit about that in the process. But before we do so, I'd like to take a moment to pull you, our audience, to find out where your interests are in mobile app development. So let's first ask, do you use mobile apps on a smartphone? Feel free to click on your screen if you are a current app user, or if maybe you only read your email. Most people these days seem to be using apps to some degree. So we just want to gauge our audience's experience so far because that will help us tailor our presentation a bit to your needs. So I'm going to go ahead and skip to results here. It looks like the fair majority, 93% are using mobile apps on smartphones. And the next question is a bit more complicated. Does your organization run web or app-based projects? And if so, do you run those projects or develop those projects internally, or with external or third-party developers? So maybe you do just web projects like you work on your website internally or you have a third-party partner. Maybe you have worked on apps. Maybe you have not. Maybe you've done all of the above. So let us know in the results where you are on this spectrum, and whether it helps us to know whether or not you're primarily using third-party developers who are not part of your organization, contractors, or other companies to help you develop. So it looks like from the participants you can continue to respond. It looks like most folks are doing web-based development of some kind. About 65% are doing some type of web development, but about half doing in-house and half doing it with third-party developers. 11% are doing both web and app development which is great. And about 17% are none of the above. So maybe you are here just because you are interested in figuring out what kind of development you can do and what the process is, whether it is worth your time. So the next question is your organization planning to develop a mobile app? Are you just considering it? Are you looking for ideas of apps for nonprofits? It looks like so far we've got lots of considering it and yeses. And hopefully today you will get some insight into the decision processes around the app process to see if it is something you want to invest your time and money in for those of you who are considering it. So that's about 45% considering it and another almost 40% who are yes, definitely going to develop a mobile app. So thank you for taking part in those polls. That does help us understand who you are a bit more. We won't get into too much technical detail and we'll try to define things throughout the webinar but if you have questions or if there is terminology that we toss around that we forget to define, please let us know in the chat and we'll try to make sure that we convey that information to you. So with that I'd like to go ahead and hand it over to Anna Jaeger who is going to take us through some of the process of getting started with the mobile app and talk a little bit about what is safe night and we're going to use this as a case study to share that experience and hopefully some of the insights will be useful to you. So thank you. Welcome Anna. Thank you very much and thank you all for joining us today. So if you are at a nonprofit and you're planning on developing an app for social good, you really need to understand what is the goal. I'm sure you've heard about this for websites as well. What is the goal of your website? Well the same thing is true for an app but maybe even a bit more restrictive. You don't want people doing too much with an app. You don't want to be giving them lots of messages and lots of ways to take action. You really want to funnel them because you have such small amount of real estate and small amount of time to really capture their attention. So you really want to understand what is that the primary social benefit goal that you're trying to accomplish with your app. And we'll talk about what ours was in a moment. We encourage you to flesh out the idea and really engage the community. Get other people involved in the process as we have. We've learned that it's tremendously valuable. They come up with things that we hadn't even thought of. So we'll also talk about that. And then getting it built. Do you have folks in-house who have the capabilities or want to learn? Or do you want to work with a third-party development organization? And like our relationship with Aid Matrix, they are not a contractor for TechSoup Global in building this app. They are a partner in the development of this system. And they have really brought a lot of their own experience with fundraising and with infrastructure for nonprofits to the process. And together we make a whole unit, but individually we're not. It's not just TechSoup saying, hey, we need some contractors. So it's definitely important to think about what is that relationship with the developers like and the other parties who you're bringing into the mobile app experience. And then make sure not to forget, and we'll talk about this a little more too, but you need to have budget to maintain it once it's built. The budget can't just be for the initial development. You're going to learn things as you go. You're going to have to scope it down to get to the first deliverable. And then you're going to want to do more with it initially. And think about when the phones upgrade. Both Windows phones and androids and iPhones, they all upgrade quite frequently once or twice a year. So what is that going to do to your app? And when we've heard numerous occasions where folks have had their app out into the marketplace, and then a month or two later the platform versions, and suddenly this beautiful app doesn't work anymore and they don't have budget to maintain it. So we'll get to some more specific and explicit lessons that we've learned towards the end of the presentation. But right now we want to tell you a little bit about the app itself and what we are developing. Safe Night is a mobile service that allows the community to respond to the urgent needs for shelter. And what this means is when an individual is in urgent need of shelter, a qualified staff member at a domestic violence service organization can initiate a request for a hotel room funding. So the person who pushes out the request is from a nonprofit, from a qualified certified domestic violence agency. Both TechSoup and Aid Matrix have a long history of onboarding nonprofits and ensuring that they are who they say they are. And supporters who've downloaded the Safe Night app will then, once the organization has pushed out a request for help, the supporters will receive a notification that an individual is in need and then they'll have an opportunity to help cover the cost of the hotel room via the app. So again, the shelter is the one who does the screening just like they do now of the person who needs the help. They're the ones, the organization is the one who puts out the alert. And it's the donors who have the app installed who can say, yes, I'll help right now and will make a donation. And some people here at TechSoup and others are saying, why are we doing this project? It seems a little abstract and different from what we normally do, but here are just a few stats that really astound us. These are one in four women in the U.S. who will experience domestic violence in her lifetime. I believe all of these stats come from nnedv.org. That's the National Network to End Domestic Violence. And I won't read through all of the stats, but it's really just incredible. And one of the stats that really hit us was on one day in California alone, nearly 3,000 people found refuge in emergency shelters in transitional housing, but nearly 800 people didn't find the housing that they needed. 800 people on one day did not have a safe place to sleep. And so we really wanted to target that unmet need, and we were trying to determine how could we do that. Here's another just real-life example that really hit home for us. And we wanted to make sure that anybody who needed it could find refuge for the night. Our app is not going to end domestic violence, but it will really help people for one day get out of a bad and dangerous situation. Keith, do you want to jump in here and talk a little bit about the goals of SafeNight specifically? Absolutely. I think our main goal is to reduce the incident of domestic violence by basically enabling people and those that care for them to remove them out of the dangerous situation, whether that's the individual themselves calling a hotline because they need help, or often it's the case there's been police intervention and the police are actually having those relationships and are calling and trying to find capacity. And the shelters often, as Anna pointed out, are way too often full and there's not a safe place to put them. So ultimately that's what we're trying to do. There's a couple of enabling goals too though is what we're trying to do is generate new sources of support and capacity for the domestic violence sector coming at this a bit from an aid matrix standpoint where we believe there's capacity out there in the corporate world. Well, one of the places there's capacity in the same city where the shelter may be full there may be a hotel room that's about to go empty. Well, can't we bridge those two things in a room, a space that would have gone to waste? Can't we use some skilled nonprofit volunteers and some corporate connections to actually turn that empty wasted space into a safe place? At the same time domestic violence agencies like other folks are trying to diversify their donation sources. So can we use this tool as a way to reach unique donors, donors who will respond to that very immediate request who maybe may not be interested in writing a monthly check or an annual check but will respond to that immediate impulse. So as TechSoup and Aid Matrix part of what we're trying to do is bring in new friends and new funds, new sources of funds and ultimately more capacity so that we can get more women and those in their family placed in a safe situation for the evening. Part of the process and really one of the neat things TechSoup has done in the partnership has really enforced with us the importance of at the same time capturing as much of the relevant data as possible so that we can go back and serve those people even better as we go on and build the case even more strongly as we go on to convince others to help us and get involved and address these critical needs. Thanks Keith. This is Becky just chiming in because I think this is one example of a solution-based app that's working toward finding temporary smaller solutions with growing capacity of support from around the community and communities that could easily be, the idea for this could easily be transferred to a number of direct service organizations. So if you run a food bank and you need some money specifically to buy food if you run a bike service or a bicycle promotion organization to let people borrow bikes to commute to save on energy costs. You could have something that has a similar type of request system where you as an organization, as a direct service organization could put out the request that we need this today. Or if you're working with an inventory in a soup kitchen that you could have something that says we have a need for this donation. It will cost $30. You can make that donation and it will happen today. So I think that there are a lot of ways or an animal shelter if you serve communities where you need fosters for animals. So I could see that this kind of concept could be transferred to a variety of different mostly direct service organizations. And TechSoup is not a direct service organization that we work as a domestic violence shelter. But we convened with the generators that Anna mentioned earlier, we convened domestic violence organizations and shelters to help them determine what their biggest needs were and this was what has come out of it. So I think there are ways that this concept could be transferred to a variety of other organizations and types of services. So with that I'm going to go ahead and hand it back to Anna to talk a little bit more about the process and to give us some definitions before we launch into everything so that we're all on the same page. Great. Thanks Becky. Now I don't want to scare anybody with any of these so don't worry. You don't have to be able to consume every detail here. But app development is a lot like web development in that you can have a number of different processes from getting to the start, from the start to the finish. One of the most common ones in software development in general is waterfall where you do all the planning up front, then the requirements, then the design, then the development, then the testing, then the acceptance. And it's a tried and true practice. It works really well in general. We used it for the development of SafeNight. One of the downsides is it's not very conducive to learning along the way. So another process that we've touched on and we'll be using a lot more of now that we have the base product, but as we go forward we'll be using something more called agile development where you do small chunks of work. And at the end of each chunk of work you have something that's potentially shipable, a product. You have a new feature let's say, or you have some new content or you have something new that you can get in a small period of time. And each of the teams you work with, the development teams you work with can dictate how long that period of time is. Is it one week, two weeks, a month? But I really recommend this model in terms of it's really great for learning along the way. So if you do two weeks worth of work and you learn something new you can add that learning in and shift the direction of your app along the way. But you have to have a pretty good sense from the start of where you're going and a lot of flexibility and willingness to shift. So that requires some good organizational buy-in that what you start out doing might look very different from what you end up with. And that's okay as long as everybody is bought in. I'm not going to define all of these things right now, but these are just a few words that maybe later if you want to look them up, do some searches on them they might be helpful before you go on the journey of building an app. These are several things HTML I'm sure you've all heard of, but HTML5 is the latest version and CSS3, that's the style sheet. And they really enable app development and responsive web design for websites as well. So those are good things to know about. Keith, anything else you wanted to add in here before we move off these definitions? Just one thing around, there's the definition of native app which really talks about developing an application for use on a particular platform or device. And for a lot of our folks here who have worked with technology thinking about what computer or what web browser is going to see what you developed has not been much of an issue through much of your career. Those of you who are maybe further along in your career like I am will remember the days where we had to develop for specific operating systems and things to work on specific devices. But in this era of web development and most things being on the Internet rather than on your specific machine, we haven't had to think about it that as much. Now as you start, so those of you who have done a lot of web development as you move to the phone and developing apps for the phone, there's a lot more work about things working on a particular device and on a particular operating system. So doing a Windows phone version and an Android version and an iPhone version and not only that for specific operating systems for those applications and some nuances between different Android devices for example. So I believe that's a temporary situation that's affecting us for the next few years but it is something that those of you who are kind of moving from a web based view of the world to this mobile app piece is to really be having enough time and thoughtfulness around the fact that you are going to have to develop things for different kinds of devices. Excellent. Thank you. Great. So getting started with mobile app development. Here again are some terms that you will want to know about and we'll show you a few examples of them in the coming slides. But Keith has shown here on the right a version of the app flow. You can see it doesn't have any details about the fields that are in any of those screens but each of those boxes represents a screen and the arrows and the lines represent transitions to other screens. So from the home screen you have three options or three paths that you might go down. And then on the next slide here is an example of a wireframe where again there are no design elements, there is no color, there is no shape, there is not a lot of layout. But what these tell you is what fields and what functions should be on that screen. And remember when you are doing a mobile app you don't want to cram in too much. That is always my tendency. Let's do more. Oh we left out this bit. Oh this bit is critical. But it is not a lot of real estate. So you have to keep it simple and keep it large enough that people can see and don't have to be zooming in and out all the time. The next step that we did was design. So hopefully this has come up on your screen. And you can see this is the login screen for the Safe Night app. You can see there is the starry black background. And then there is a blue background as well to go around the main fields and the content. And then you have got the fields themselves and the buttons. So this gives once you get to the design, the UI design, user interface design that gives a lot more look and feel to the app. You will get a lot more people responding very positively once you get to this step. It is a much more shareable step. The wireframe example if I can go back to it, people in my experience start to get it when they see the wireframes which is great. But especially if they have some technical experience a lot of folks love wireframes. But a lot of folks who are not immersed in technology I think tend to respond a little bit better to design. You don't have to have the whole thing designed in an agile development process. You could design one or two screens and test it out with your community to see how people respond. In our design we had an initial logo and it was a dove that looked like it was sleeping and very peacefully. And when we showed it to people they thought it was either a dolphin waving or maybe a manatee. And we said, oh well that's not going to work. So we started all over and came up with a different logo. And those are the things that you learn in the design stuff. So don't forget to share those pieces back out with your community or with your advisors, people in your organization to get buy-in to make sure that you're on the right track. Now I'd like to talk just a little bit more about our partnering outside of TechSoup. We have been working a lot with domestic violence agencies in California for the past 13 years. We've done a variety of consulting with them. For the past three years we've had grants from the Blue Shield of California Foundation to support those organizations through the use of technology. So we help them identify what their technology needs were and help them acquire donations to meet those needs. And the idea for this app came out of all of those conversations, those years of conversations with domestic violence organizations. This idea did not come to us overnight. And initially we thought, well let's do a bedfinder app where shelters that are full can reach out to other shelters and say, do you have a bed that will meet my needs? Do you have a bed that will accommodate families? Do you have a bed that will accommodate somebody who needs assistance with getting off of drugs? And when we talked with the community they said, that's lovely but most of our shelters are full. We don't have capacity to share. So what we really need, we had talked about once the bedfinder app, once we get that piece in we'll escalate and we'll start looking for free hotel rooms. And they said skip the bedfinder part, go straight to the hotel room because that's what's going to increase our capacity. So after we had started, we had partnered with Aid Matrix already. We were talking, we were starting to develop the ideas around bedfinding. And the community said, no, that's not what we need. We shifted. We changed the focus of the app to be this more fundraising type of app, crowdsource fundraising for hotel rooms. And so as I mentioned Blue Shield of California Foundation had supported us for a number of years but when it came to the app we actually went to Microsoft and said we want to build this specific thing, will you help us? And they gave us a very generous grant to help explore and get the initial app off the ground. And as I said we had started partnering with Aid Matrix and really because they had such deep experience with fundraising. If you're not aware of it they have the Virtual Aid Drive which I believe is available as a donation through TechSoup. And so they were really familiar with how to process fundraising donations and how they had the infrastructure for accepting credit cards and working with donors. And they had a deep knowledge of developing infrastructure to meet the needs of nonprofits and they had the technical experience building apps. They partnered with Microsoft to build an app called HelpBridge which allows people to reach out for help in a disaster. Hey there was just an earthquake, I'm okay or I'm at this location and I need help. So we really looked for all of those things in Aid Matrix and that's what told us that they would be an excellent partner in this endeavor. And then once we started making some progress we went back to Blue Shield and then we went to Vodafone and said, you know what Microsoft has helped us in this way. Can you help us get a little bit further? And once we had the real solid idea they were willing to come on board and help us with some grants to make this a reality. I think it's terrific to know that a nonprofit especially if you're a smaller organization does not have to just go it alone and try to come up with an app idea and develop it and come up with all the funding themselves that if you work in coalition with organizations that do similar work that it's a great way to not only come up with an idea but also to kind of come up with funding sources to help you afford to build an app that can launch in different marketplaces. So I think that's a terrific piece of advice for people to look at not just their own organizational capacity but to look at their partners, to look at their friends, to look at their coalition of orgs that work on the same issue to see if there are ways that they can partner and work together to build something that will ultimately win solutions for them and for their communities. Thank you Becky. Keith, do you want to do this next slide in the video? Yeah, sure. And I think Becky's point is a good transition point. When we look at the background in terms of the fundraising engine was actually developed for an example Becky had before about people needing food for the food pantry or for the food bank. We have this web-based fundraising infrastructure called the Virtual Aid Drive and it actually started as the Virtual Food Drive and much the way Anna was describing, this was developed with the community and in fact was not even our original idea and its base concept. Our local food bank who we had done other, a significant amount of work with came to us with a sheet of paper and a list of grocery items on it. And a company had sent it out to their employees and people would fill out the grocery list and the amounts and then they would write their check and staple their check to the paper and turn the paper in. And the North Texas Food Bank came to us with that and said, could you put this on the computer? And our eyes got really big because we saw not only was that going to be applicable for them but it was going to be applicable for all kinds of food banks and not only would it be applicable for many, many food banks individually but as a network you could go to national employers and national groups of people and they could make their contributions and make a local impact as part of their national organization. And so the Virtual Aid Drive and Virtual Food Drive and Virtual Aid Drive was born. The same infrastructure is the fundraising infrastructure and underneath technology and processes and support systems that is supporting the SafeNight app now. And we actually believe over time that same story will be able to tell and that same value we are going to be able to tell as this becomes a national system. So through the combination of the back end system that we already had in place, the Virtual Aid Drive and the mobile app development, we have the whole interaction process from the point from where a shelter manager has a specific need. They need to put a person in a hotel room that night. They know about that person. They have the room secured. They know how much it will cost. They can go into the Virtual Aid Drive and put out a specific request for somebody to pay for that specific room. The Virtual Aid Drive then sends a notification out over to the mobile app and out to all those people who have agreed to hear requests from that specific shelter in that specific time frame how often they want to be asked and their phone gets pinged with that very specific request. And if they make that donation right then, then that money will be used to place that person in that room that evening and we have all of the tracking on the back end to make sure that those funds are used exactly the way that we've asked for them. Next we have sort of a video of the whole process. And this is from a technical standpoint that you can use if you develop in the .NET platform and then some other platforms you can use what's called an emulator. And that's basically a way to make your PC act like a phone to test your mobile apps. And so before we had the phone ready, the phone version of the software ready, we had it ready in a stage where we could put it on the emulator and we could start testing the application. So you can see the application sort of running in process here. One of the things we did with that early on was then to go make a movie. Because as Anna said, as much as you can be specific with people, provide them specific pictures and look and feel and such about the application, some people are abstract and like process flows and such, but many people are very concrete. And to the extent that you can give them a very specific picture of what you're doing, you can generate their ideas, their feedback, their support. Here you're seeing the shelter manager logging into the virtual a drive to make that request. See that donor information that make that request for that new room. But one particular trick of the trade I'll say is you can make this web-based movie of your app while it's still in process. And then you can actually, while you're not downloading the live app to your phone yet, you can download this little movie onto your phone. And then for example, when I was at lunch a couple of weeks ago and before the app was ready, but I still had the movie downloaded on my phone, I could sit at lunch and I could go to one of our supporters and just run the movie on my phone and they could see it actually running on a phone and it gave them a very specific idea of how this was going to work. So little movies like this and such can be helpful in being extremely concrete in your support. Here you can see the specific need of the donation, $54. We'll put a person in the room that night. They click on that they want to help. They put in their credit card information. There are other information that has already been stored in the app so they don't have to re-enter that. Here they put in their credit card information and it has all of the security.  It's a secure transaction and none of that credit card information is stored anywhere but we use VeriSign which is the PayPal people. It's one of the biggest gateways out there. And in a couple of clicks they've made an impact. They've changed somebody's situation that evening and really potentially saved them from a very dangerous situation in just a few clicks. So that's a little bit about the movie. Here you can see some other ways that you can give feedback and all of this. And actually those of you that have Windows phones and can download it on the store I know you put the link out there. You actually can see most of the same functionality yourself right now. And I think with that also it's also good to note you saw there we put our sponsors on there. One other tip I guess the way you're developing it too is to make sure you give your sponsors adequate promotional coverage for their contributions. Absolutely. And as you mentioned we also showed this to some of the financial supporters who have backed SafeNight and they loved it. Making this video, the work to make the video before the app was finished has been an incredible boon for us. So I encourage folks to take some time if you think it's going to take a little while even a few more weeks. Having a video like this has been incredible. I got to show it at our staff meeting and I was amazed to see how riveted people were by that video and the presentation. It really helped get people on board. And they started instantly I started getting emails from staff saying what about this? And that's incredible and I really like how you did that. So it was really wonderful that we had that video to be able to show it. A little bit more about engaging the community the way that we did it was we had, other than the work I had already talked about all those years of consulting, we pulled together an advisory board, folks who we felt could look at what we were doing and give us feedback. We could send them documents and get them to review it. It can be a big commitment so make sure that they are signed up for it. We probably tapped hours a couple of hours a month. We would have a meeting and we would have them review some documentation. Some months we wouldn't have anything, other months we would have several hours worth of work. So choose wisely. And then in a moment I will talk a little bit more about our pilot participants but that's our next step now that it is launched in the marketplace. We are going to start piloting it with a few shelters. Go ahead. So one of the things to think about is that step of launching your app in the marketplace and it does take time unlike publishing your own web-based project or something where you can just put it on your servers and it's out on the Internet for whomever you want to access. Apps these days have to go through certain marketplaces and sometimes get some rigorous approval before they are launched. Each app market is different and you have to allow some time for that and different strategies. For example, the Android Market, it's called Google Play these days, but the Android Marketplace is actually very easy to publish too. There is very little review with somewhat an open source based Marketplace. But then on the other end Extreme End is the Apple Marketplace which is much more stringent and Windows and Microsoft is somewhere in the middle of their folks review your app, they test it. If you have things like for where we had the – people are donating money then that raises a few flags. They want to make sure that you're processing that data correctly and you've got the right securities and such. So you have to allow for some of that. We recommend a strategy of going ahead and getting one good complete set of functionality out and in the queue with them as soon as possible. And then while you actually may have some other fixes that you're working on in play, getting some of the cosmetic things right just to get that process underway for review. But that can be – at the time this is usually at the end of your process, of your build process. So pressures can be high at that point. So definitely allow some time and date flexibility for those Marketplaces to approve and actually publish your software. Thanks Keith. Now on to our pilot. We are doing a small pilot starting with a couple of organizations in California. Then we'll expand the pilot to a few more organizations in California. And then we'll have a second pilot moving on to organizations in Texas. And then we expect to expand state by state nationally. And in each of those we expect to learn new things and discover new ways to improve the app. So we're just entering that phase now. We can report back a little bit more on later on how that goes. But you can see in the notes in this particular slide what some of the things were that we were looking for in our pilot organization. I know we want to leave plenty of time for questions. So I'll just quickly go over some of the lessons learned and some of the tips that we have for you. And we aren't by no means experts, but we're just talking from our own experience. But definitely the goal needs to be aligned with the goals of the organization. As I said before, keep it simple. And if you have personally identifying information in it, if you have people enter their names even, or any other information, make sure it's secure. And make sure it meets the standards. Don't just trust a developer, but make them explain, make them show you how it's secure. Have your content copy edited? Have a real marketing plan? And as we mentioned before, budget to maintain it when the phone's upgrades, not just when you want to add more features. Define the goal up front and how you want to achieve it. What is it that you want to do with this app? And be very clear on that. It doesn't mean it can't change, but start with a hypothesis and test that out. Engage your community and your target audience, because keep in mind our community here is the Domestic Violence Service Organization, but the target audience are the donors. So we have to make sure that they're both involved in the process. The advisory board I already mentioned, and trying not to make your app all things to all people. For instance, don't build a website in an app form. You can make your website mobile friendly, but don't build an app to replace your website. And for content apps, you could try getting your feet wet with something like App Maker. They're good for putting in content and media. And as Keith was just talking about, be aware of some of those platform restrictions. For instance, Apple, you're not allowed to do fundraising to nonprofits through their apps. You can get around that by putting in a link to a website, but your app has to be free then. You can't charge for it. And make sure to listen to your community feedback once you get it. So I think that's the end of our structured presentation. I want to do some questions, Becky. Terrific. Thank you so much, Anna. Those are some great tips. We have quite a few questions that have come in, so I'll go ahead and jump right in. And this is probably one that either of you could address. So Lynn was asking, saying that she's really interested in partnering with somebody to develop a mobile app. How do you find a company to partner with to develop it? How did you guys reach out? Were these people you already knew and had relationships with, were these prior funders? As Keith mentioned, we had already had a long-standing relationship with AID Matrix, and we were looking for a way to deepen that. So that's how we found them. There are other ways that we're also doing outreach. We're letting the community know what it is we want to do, and the things that we need, money, developers, other resources. And the community has helped us. And our community doesn't just include nonprofits, but it also includes folks like Vodafone Foundation of America and Microsoft and Blue Shield. So we've let them know, and they've also helped us find some other folks. We've also just been very open online. And people have come and found us wanting to volunteer. A lot of hackers want to learn, and so they might be willing to take on your app Pro Bono. Just keep in mind that it's a volunteer like anybody else, so you have to have experience managing volunteers. Great. So tap into those existing partners and coalitions and funders to see what you can find. So in terms of social benefit, NJ asked, do you recommend building one app to satisfy two focuses, like one to benefit your own organization, and one to also then benefit the community that organization serves? Or should those be broken into two different apps? Like should you try to fundraise for your own work, and also try to get people to donate directly to a direct service cost? Or is it best to have those broken out, do you think? I'll put that to Keith. Well, I would say to start with that the fundraising and the build are two different questions. I think typically you would say that you would build apps, separate apps towards each audience from the actual technology you build. As Anna was saying, you need to be pretty narrow cast in your apps to make sure that they accomplish the goals of that specific audience. From a fundraising perspective, it is often some projects are more attractive than others. So it may be easier, and I as a person who does a lot of fundraising for our stuff finds it often easier to bundle the ask. If I have a couple of projects and maybe one is not as attractive as the other, of course that direct service app is going to have often more attractiveness to a funder than maybe something that also helps you build donor intimacy and expand your donor base or something like that, or help you accomplish something operationally more effectively, those of you that work in large organizations. So from a funding standpoint, I would look at bundling them perhaps and how they fit under a common theme, but from a development standpoint I would err towards the eye of having discreet apps for the discreet audiences. Great, thanks Keith. We have a question that I think Anna might be able to address best from MJ asking, did you have or should we plan for legal costs for reviewing an app's legal consequences especially if we work with at-risk populations? So what kind of legal oversight had to happen, if any, for safe night? Yes, definitely have legal review. And that can often be whatever legal counsel you have set up now, whether you have a pro bono firm or if you're paying for it. I don't know, nonprofits have different situations. They don't necessarily have to have a lot of experience in mobile app technology, but having some is good. And having somebody who's willing to say, yes, I'm going to do the research to understand it. Because of the credit card processing, we had to make sure that that was in our terms and conditions. So we had to fill out special forms for our legal review to say what we were doing with the credit card information, if it was going to be stored, how it was going to work, what level of encryption we were using. And I'm happy to share that resource afterwards, the checklist that we used. It also included things like, does it have a confirmed step before the credit card is submitted? So the legal review is very important, especially when you have, like I said, personally identifying information, credit card or financial information, or if you have any sort of risky information like domestic violence agencies are very technophobic because people can often hack. And so they wanted to be assured that no information about the survivors would be available for hackers. So we made very specific choices about that, and we had legal review. So to piggyback on that, we had a couple of questions from Larry about how do you set up security on your app and what sort of privacy guidelines? So Keith, is that something that you might be able to tackle? I can start, maybe. So there's a couple of things. Transitioning from our last conversation is one of the things is just to make sure from a documentation standpoint and your terms and conditions you've addressed, how you're handling the information, then before we move into technical, maybe one of the logical steps is to think about how to minimize your risk at the same time, maybe maximize your value of having the app and things stored in the app. For example, one of the things we did as you saw in the movie there is that the general name and address information and things like that, we are storing on the app. And so we have to have security around that, but then we actually limited our risk and our technical challenge by not storing the actual credit card number and related information on the app, but more making that pass through and leveraging the gateways of the large technology companies like VeriSign for that. Now of course it does mean the user has to enter that credit card information each time. So we made a logical choice there of how we constructed the app to reduce the technical demand. Then the third thing I'll say is that to the extent that you can use, that you can use as much as possible predefined objects and kits, now we have a Microsoft bias that we work in several different platforms at Aid Matrix. We certainly are a significant Microsoft shop using the VB.Visual Studio and that background enables and helps ensure that you're doing things in a productive way and gives you access to objects and things like that to help with your security measures. That is something to think about for your app and some of the interplay sometimes with some web back ends is you will need a little bit of expense and some time around, sometimes some of that secure socket layer stuff. We use GeoTrust but there are several out there for some of those components. Great. Thanks Keith. I want to tackle a couple of quick questions hopefully so we can get through a few more before we round out at the top of the hour. So what software was used to create the video? Angela wants to know. That was Camtasia by TechSmith. Okay, great. And we also had a question asking if there are any other recommendations similar to App Maker because we were just told that App Maker is going to be taking itself offline. I haven't verified that but other suggestions of App Makers? I have used iBuild App, oh sorry Anna, but I've used it's just www.theletteri, then build, then app.com. I built a little e-book on it and had no technical knowledge was required for that very basic content. Yeah, and it really depends. Also another partner of ours, another nonprofit that focuses on schools, Digital Wish has an e-book builder that you can put a bunch of content and media in videos, that sort of thing and it'll make a very app-like experience for you. And then also on this slide there's also App Builder but you can search on it and look for similar things and give it a try. A lot of them will let you try to build it for free and will only charge you once they're going to submit it to the Marketplace on your behalf. Great, thanks. And just a note because somebody asked if the emulator was free and if it was made on Camtasia that is a purchased paid product. So it's not a free product out in the Marketplace. And the emulator is part of Visual Studio for those of you who work in Microsoft Visual Studio. Okay, and then we had a couple of people asking if there's a way to give feedback from the app itself and if there was a way to become a beta tester for the app, for the safe night specifically. Yes, in the app itself we have in the Contact Us screen, we have one that says Safe Night Feedback so that if you're in the app you can just put that and type a short message to us. Also to become a beta tester, email me and we can talk about it especially if you're in California or Texas. Great, and then I guess one quick question before we wrap up and then maybe it's not that quick but if you could give an estimate of how long it took to build this, how long has this process been for the actual app creation or how long has each phase been since it's an ongoing process? Keith, I'll let you weigh in some but I think each app is going to be different. This one has had lots of different starts like I said. We were going in one direction and then we changed direction and they're getting going and fundraising and all that. So we've been working I think it's about a year on the project, the development though. Keith, what would you say in terms of how many months of active development? Yeah, I would, to Anne's point we've built more than just an app with this program and of course we're both very passionate about it but it is a whole system that's involved getting a lot of different folks together. From a core development standpoint, typically you can get some material piece of functionality together in less than a quarter or shoot for a quarter including getting something released to the marketplace so 12, 13 weeks. Back to Anne's point about agile, a lot of times you have to do a little bit of larger development closer to a waterfall to get one chunk out but I would say try not to develop too long before getting something up for people to interact with. Great, and we will share contact info in the follow-up email as well as these resources. We are at the top of the hour so I'm going to go ahead and wrap it up but I guess the moral of the story is that if you're building a big project app like this one where it's a system it's going to take some considerable resources and time and fundraising efforts. It's not an app to just poke your friends on Facebook so think wisely about whether it's worth your time and resources of your organization to invest in this type of app development. We will have more resources available to you on mobile throughout the month of July so please check back with TechSoup and watch for more upcoming events on this topic. I'd like to quickly thank our webinar sponsor ReadyTalk who provides this platform for our youth to present these webinars to you. So thank you to them. I'd like to thank Keith and Anna for your terrific presentations. We will and also thank Allie for grabbing all those questions on the back end. If we did not get to your questions you are welcome to join us in our community forums at TechSoup.org slash community where you can continue the conversation and join discussions about mobile technologies. Thank you so much everyone and have a terrific afternoon.


Live from Las Vegas, it's theCUBE! Covering AWS re-invent 2019. Brought to you by Amazon Web Services and Intel, along with its ecosystem partners. Okay, welcome back everyone live. CUBE coverage here at re-invent 2019 in Las Vegas. I'm John Furrier, your host, extracting the signal from the noise with Stu Miniman, analyst at SiliconANGLE theCUBE and Wikibon. We've got two great guests talking about the ecosystem and the future of software and how customers are consuming it in the cloud. Todd Osborn, GVP of Alliances and Channels at New Relic and Josh Hoffman, GM and Global Lead of ISP, Partner Ecosystem of AWS. Guys, welcome to theCUBE. Thanks for having us. Look guys, the top story to me at this show so far is obviously infrastructure at scale. The software development lifecycle is continuing to evolve. We are more automation, more, as Andy says, heavy lift things being done, which means that application developers are going to get more and more goodness. DevOps created infrastructure as code, check. Now we got data, tons of data everywhere. So we're seeing an ISV renaissance, more software.  So what's you guys take so far of the impact of the ISVs here? Josh, talk about that because this is a big story. The impact is massive. I mean, if you walk around the floor, you'll see folks that are automating new ways of doing DevOps. You're looking at new ways of securing serverless functions. You're looking at new types of storage. So you could go across every category of technology in this room and you will see an incredible amount of innovation. Our partners are really driving that. Talk about the relationship with AWS, New Relic, AWS, long standing partnership. Where is it now? Where is it going? It's, I mean, it's off the charts. So even just the last year, the amount of momentum we've built together has been fantastic. So we participated in a whole bunch of different programs. We've got dozens, hundreds of joint customers that were doing things together. I mean, just look at this event. It's just astonishing. We operate in a lot of different partner models from reselling with various partners to building technology programs, to participating with Josh and team and our friend Dave McCann and team on AWS Marketplace. Just a whole host of different things just continue to expand the partnership at scale. And the consumerization of the software, the procurement process, we've had Teresa Carlson on from Public Sector, whether you're in the public sector or commercial, procurement is still stuck in 1995, it feels like, right?  You've got a lot more ways to get software with the marketplace. What are you guys seeing with customers? Is it really that bad? Am I over, it's not that bad, but you know what I'm saying? I mean. So from my perspective, one of the cool things we're seeing is AWS and the cloud providers are driving a consolidation of budget, of modern stuff, of cloud, of all the new things that companies want to do. That's all getting consolidated either into new groups or new budget cycles. And AWS is making it really easy to participate in those. So through programs like the marketplace, through various other initiatives we're doing, we can combine what we want to achieve with what the customer wants to achieve, which is speed to market with what AWS wants to achieve, which is faster adoption of all the different services and bringing the right ecosystem along with it. So the modernization of the procurement cycles along with the modernization of the technology is really cool to watch. Well, I wanted to ask that before I want to get to the question that addresses Andy Jassy's point on this keynote. This is the first time I heard him talk like this. We see two types of developers and two types of customers. People who want the low level building blocks, the builders, and then a new set of customers who want solutions. This is your wheelhouse. This is where the solution network kind of ecosystem is evolving very quickly. Can you guys share your observations on what he means by that and what does it mean for customers? Sure, I'll share it in the context of what we're doing with New Relic. When you think of the concept of a solution, a lot of our customers, hundreds of our enterprise customers are going through our migration programs. They need help making sure that what they're doing on-prem is translating to what's happening in the cloud, what the applications are doing on-prem and how they're performing in the cloud. So we've collaborated with New Relic over the last year and a half on a number of new, not just migration programs, but windows or views into how the applications are performing. And we've designed those specifically for customers who are going through those migrations. So you just take that one little category and it's an area where we're collaborating together to bring something that is a full solution to the customer for those who are going through that migration journey. Your take on the whole solution thing. Yeah, so last year at Reinvent, we announced really the first solution that New Relic had ever launched, trying to meet that market need and we announced the cloud adoption solution. So everybody knows we've got this great platform with all these cool features. We had never really gone to market and said, not only do we just address application monitoring or infrastructure monitoring, we actually address the business outcome of migrating to the cloud and all the benefits of doing that. So we announced that as a methodology last year. We added to that over this past year because we've enhanced our platform to have this new capability that we call programability, which is the ability to write applications on top of the New Relic platform. So we've built and we launched today a cloud adoption solution application, kind of a mouthful. But what it is, is it's the ability to use our technology and our platform to very easily drop that into a customer and help them very quickly get time to value of delivering on a solution and ultimately achieving the business outcome they're looking for.  And just like Amazon, what you want is you want builders and you want them putting solutions on top of it. Give us a little bit of the momentum of what you've seen since New Relic won and the rollouts. So I don't know the formal count, but I know we're way past the dozen applications that we launched since then. We also added several different features, including logging and some other technologies. We've closed a bunch of different deals with these new technologies since then. And then a couple of the cool things from the partner ecosystem we've done is with the platform capabilities we have, firstly, we're now getting ready to embark on building our first technology partner program. So we were talking to dozens of different partners in this room about how they can build with us on New Relic to make the platform even stickier for our customers that can now integrate New Relic with various other technologies. And then the second thing we were proud to announce today is we've actually just signed three new managed service providers. So kind of another partner motion that we're driving in this ecosystem. And the new features of the New Relic platform helped enable us to do some really cool things with the platform and also evolving business model to close. So we're excited to close three top AWS partners, which is Bespin Global, Blaze Clan, and out of California Mission Cloud as three new partners that we just signed agreements with. So we're happy to do that. Yeah, when we talk about the transformation, you know, one of the biggest challenges for customers is their application portfolio. I noticed New Relic has two booths here. There's one specifically just focused on serverless, which I think is awesome. It's got some cool things there, very focused on that developer app dev deployment there. But you know, your customers, they've got a broad spectrum of applications and that journey to transformation and modernization is going to take time. How do you deal with the spectrum of what they're dealing with? Todd, maybe start with you and then Josh would love your viewpoints too. Yeah, I mean the spectrum is massive. So our biggest challenge is keeping up with everything and continuing to innovate with all the things that are happening. But again, the benefits of the platform that we have enables us to do that in the enhancements we made this year. Now that our platform is more open, we can collect data from multiple entities, not just the New Relic agents that we were built on. So the concept of observability and being able to observe the entire application environment is built on the fact that data's got to come from all these different places. Then we need to turn that around and curate it into the right experience and the right use case that the customer is looking for. So all I can say is that our company's built on innovation. We try and stay on the cutting edge of all that, try and stay current with that and meet the customer's needs as everyone here is innovating crazy at scale. Todd, talk about what's going on in New Relic. What's the coolest thing going on in New Relic right now? Cause Lou always comes on the queue. Lou's the CEO and he's cool, we love him. But he's always got his hands in something. You obviously got the observability thing down. Cloud operations becoming standard. That's a tailwind for you guys as a company. But what cool things are you guys working on right now? You know, I certainly can't do Lou any justice. So the customer stories and things that he comes up with are amazing, but you know, from an industry's perspective, like gaming is hot and it's just, like media and entertainment is hot. So we're just doing some really cool things with some really cool customers. Maybe not as cool as Lou would be, but you know, customers like are really adopting our migration story and we're really driving some significant business together. So customers like World Fuel Services and Fleet Complete, we've recently come out and announced the stories of how we're helping these companies migrate. And frankly, that's what's cool about it. It's like everyone wants to get on the cloud faster, do more faster and we're enabling that in some really cool customers. So I want to get your both reactions just two memes that we're developing on theCUBE this week. One is called, one is cloud native. If you take the T out, it's cloud naive, okay? So and the other one is something that I introduced on my post, one of my Andy's story I did was you got born in the cloud, which is clear benefits. There's no discussion there, check, winning, builder, but reborn in the cloud. As companies are becoming reborn, this is not just migration, this is a fundamental mind chef shift. This is a reborn enterprise. And if you're not reborn in the cloud, you're probably not going to be around longer. That seems to be the message. What's your reaction to cloud native without the T and reborn in the cloud? I think it's an accurate statement, it's funny. It's the first I've heard it, I may steal it if I can use it. Freeze, pass it on. I will. I would say that from an APM perspective, many of our partners are in different phases of their journey. And so everything that we do is around three anchor points, which is helping those companies build great software if they haven't already, or if they're making that transition. Once they've made that transition, how do we help them market the software? And then the third piece is really, how do we help them sell it? So in the case of New Relic, we've got a number of folks around the world that are helping with that co-sell process based on the solutions that we've jointly defined. And then we also help build out the channel, because as AWS, we've got tens of thousands of consulting partners. So the idea when you talk about that journey of becoming cloud native, is how do you help a partner through that? You've got to hit on all three of those pillars to do it. And the leadership's got to be there from the top. Totally. You got to have board alignment, you've got to have executive sponsorship, you've got to have technical buy-in, all of it. Todd, you guys have a very savvy customer base, great cloud native observability. What is the naivety issue? What are people mostly naive about? Because if you don't do it right with instrumentation and observability, if you're naive about that, you're going to get bitten in the, you know what? Well, being naive there is not having your observability platform in place. But you really can't anymore. The old world of, if you had a monolithic application running on servers, monitoring sometimes was optional or nice to have something that you could only afford on your most mission critical applications. As soon as you flip the DevOps, bunch of cloud native technologies, modern applications built on the most modern frameworks with entities that have all these dependencies to make sure that application works, monitoring is a must-have and observability is a must-have. So that's naivety. From day one, out of the box, out of the box. And to the reborn comment, as soon as you cross that path, you rebirth yourself every day. It's constant, you're releasing code daily or multiple times a day. And so there's no like, reborn statement anymore. It's a completely agile process. When you're at that point. It's a belief system changeover. It is. This is not just saying it. You got to really believe what you're doing. You have to measure and prove it. Which is what New Relic is great at. Because if you take what's happening now on premise and you go through that transformation, you've got to show that you've actually achieved not just savings, but you're helping developers be more efficient. And so you can't prove that story without the before and after. Yeah, yeah. Love talking to the cloud native gurus that you guys are. Congratulations on your marketplace and ISV success. It's only getting the beginning of that run. Yep. It's kicking butt. Congratulations. Hundreds of thousands of customers are buying and hundreds of thousands more. Todd, congratulations on New Relic. Always great to have you guys on. Thanks a lot. Great impressive company. Great results always. Great team. Great product. Cloud native for sure. Props to that. Thanks for coming on. Appreciate it. Thanks so much. I'm John Furrier, Stu Miniman here in theCUBE. Extracting the signal from the noise. Day two of three days of wall to wall coverage. Two sets here on the ground. Thanks for watching. We'll be right back.


Hi guys, this is Linda from Brain Education TV, if this is your first time, welcome! Like this video, subscribe to our channel, and click the bell for notifications of each new episode. In this video, I'm reviewing Ilchili's newest book, The 100-Year Golfer, 7 Arts for a Lifetime with the Game. Ilchili is the founder of Brain Education, and he's written over 40 books. And The 100-Year Golfer is the latest one to add to his collection, available now. The premise and storyline of this book revolves around the game of golf, but the principles, tips, and life-wisdoms that Ilchili shares can be applied to anything in life. And I think that's the true beauty of his newest book, The 100-Year Golfer, because let's be honest, not everyone's a golfer like me. But it's okay! In this book, Ilchili shares three tips on how to perfect the game of golf that can be applied to all things in life. Number one, do it joyfully. Number two, do it naturally. And number three, do it while being connected. Connected to what? Connected to myself, connected to my peers and companions, and connected to nature, the world around me. And to help the readers understand just how to connect with these three things, he breaks it down in the seven arts for a lifetime with the game. Those seven arts are number one, energy, number two, fitness, number three, breathing, number four, meditation, number five, kigong, number six, self-healing, and number seven, consciousness. Ilchili shows you how with these seven topics, you can develop a habit of connecting to yourself, connecting with others and connecting with nature to have a more fulfilling and meaningful experience in whatever you do, whether that be golf, any other sport, your work, your relationship, anything that you set your mind on doing. The book also contains some personal snapshots of Ilchili playing golf, which I thought was a nice touch to the book. And it also contains some exercises based on the seven arts, with diagrams that go along with the text to show exactly how to do it, which I thought was very helpful as well. And for me, one of my favorite parts about the book is that Ilchili shares his personal experience, how he started to play golf, what awakenings he had, and what really inspired him to write this book. So all in all, the 100-year golfer book is a perfect whole in one! The 100-year golfer book, along with this book, is part of the longevity collection by Ilchili. If you're interested in learning how to live a healthy, long, long life, make sure you check out not only the 100-year golfer, but also the I've Decided to Live 120 Years book. The 100-year golfer is available to purchase online or in person at your favorite bookstore. I will leave a link in the description below for a quick and easy way for you to pick up your copy today. If you're interested in longevity, if you're interested in energy work, if you're interested in sports, if you're interested in the arts, if you're interested in how to utilize brain education to better your life, make sure you check out the 100-year golfer today. Thanks for tuning in! I'll see you in another video! Bye!


that I will support and defend the Constitution of the United States against all its enemies, foreign and domestic. I, Richard M. Nixon, saw me swear that I will defend the Constitution of the United States against all enemies, foreign and domestic, that I will bear true faith and allegiance to the same, that I will bear true faith and allegiance to the same, that I take this obligation freely without any mental reservation or purpose of evasion, that I take this obligation freely without any mental reservation or purpose of evasion, and that I will well and faithfully execute the office upon which I am about to embark, be executed the office upon which I am about to embark. So help me, God. So help me, God. I do solemnly swear, I, Dwight D. Eisenhower, do solemnly swear that you will faithfully execute the office of President of the United States, that I will faithfully execute the office of the President of the United States, and will, to the best of your ability, and will, to the best of my ability, preserve, protect the Constitution of the United States, preserve, protect, and defend the Constitution of the United States. So help you, God. So help me, God.


Okay. Yes. So, let us just briefly remind you our setting. There will be no calculation, essentially. So, let us start from a simple case to variable continuous function that defines, so here mu is measure, reference measure, we call reference measure on c. And this function induces operator from L2 space to itself given by this integral, we denote again by kf, integral operator y to mu y. So, by when theorem these operator k, this kernel, we call this kernel, again induces a probability on the space of configurations on c, that is subset of c without accumulation point. So, here is our c and we denote element by x. So, it is just a collection of particles in c, probably there will be infinite one. So, this is our x, this point our, so the collection of all these points are our x. So, this probability we will denote it by pk. And yesterday we write, we wrote two formulas that characterize this pk. In fact, this pk just gives us a way to choose randomly some subsets which is locally finite. So, and also we have already know it is important to have this property to introduce this thing, spa measure of pk and p. So, what is this? This is by definition. So, I will give only intuitive definition. This is just in general pkpl, distinct point in c. This is, so here this is random subsets of c with distribution pk. And per measures at least is the conditional measure, conditional distribution of this random thing. x, but I erase these particles provided we are in the event. We know the event provided the event, the following event happens. This p1pl is in x. Of course, this is the other event, the other probability event. So, it's not direct to say this, but intuitively it is such thing. So, this is exactly what we calculate yesterday. The conditional thing we fixed some, for orthogonal polynomial ensemble we fixed some last p1 to pl and consider the conditional distribution. And we will denote, we denote this conditional measure by pk. So, let me write it p and the line. And we are interested in fact in calculating derivative of such thing. We are interested actually in fact in p and q, but with pq. So, here q is of the same length. Later we will also say something about when pq, the length is different. Okay. In fact, yesterday we also see that the orthogonal polynomial ensemble then this conditional measure to self is given by another orthogonal polynomial ensemble and which is again induces a determinant point process. And this fact is in fact is general. There is a theorem of Shihai Takahashi which says the following. So, we denote. So, okay. So, the first thing is pk, this conditional measure is again a determinant point process and with kernel which is explicitly given, with kernel given by the following. So, for stating the kernel, let us write in several case. When p, the length is just one. Then this is very easy to write it. The kernel is k, we denote by kp1, kxy equals to kxy minus kxp1, kp1, kxy minus over p1p1. In general this is, we can iterate this. In general this kp bar is given by kp1. So, this is a new kernel. Then we do the same procedure for p2 and etc. And actually there is a explicit formula for this which is given by determinant of kxy, k, okay let me write like this. Determinant of p, p, i, p, j. Here is for 0 from i, j. There is no 0 in particular in fact. Set p0 to x, p0 to, this is x and y. Okay. I don't think, this is, okay. I still need to write it probably. So, I am not allowed to be lazy. kp1, so xp1, kxpl. This is kp1y, kp1p1, kp1pl and kply, kplp1, kplpl. And divided by the determinant of this sub-metrics. This is given by determinant of kp, i, p, j for i, j from 1 to l. So, in other words we can write it in a compact way. So, this new determinant point process is just the determinant point process given by this kernel. So, you write it very simple. We removed the, put here to here. But the meaning is here is this power measure and here is a determinant measure given by this explicit kernel. So, there is an important fact, exercise. Assume that k is an orthogonal projection then orthogonal projection of this thing, u, 2, k, l. So, some subspace is some 2. Then kp, this just one point, kp is the orthogonal projection, the kernel of the orthogonal projection onto the subspace given by the following, f in l that vanish at g1. There is in fact a subtlety here because usually a function l2, we cannot say the evaluation at one point. But here since our kernel is continuous or nice kernel there is no, at least for our purpose there is no subtlety here. Okay, now let me state our theorem and explain, give an intuitive explanation how we get such result. So, our setting is the following. We fix a function which is say to a smooth such that the Laplacian is bounded from below and above. I think this is probably not essential but let us focus on this. And consider the following measure on c, where lambda is the big measure on c. And then we define the generalized weighted fox space determined by this lambda phi as those columnar effect function on the whole plane such that it is square integrable with respect to this measure. It turns out this is a closed subspace of l2, c, d, lambda phi. So, the orthogonal projection onto this fox space is caused to generalized Bergman kernel or Bachman kernel that we are denoted by pi phi. This is the kernel, the reproducing kernel space. That means for any f in this columnar and square integrable with respect to measure then f is actually given by this integral equation. So, for example, the simplest example and probably the most important example is for the function that correspond to the Gaussian measure. So, this d lambda phi is the Gaussian measure and in this case if I don't make mistake probably there is one half somewhere is given explicitly by this very simple formula. Questions now. So, we are interested in the determinant point process generated by such kernel. And in particular for this important example the determinant point process p, pi, this is a probability measure on space of calculations of c when in this example it has a name and Geneva point process which is the limit of eigenvalues of Gaussian non-commission matrix. So, we are going to call this generalized point process and we have remember that we would like to compute these things. We would like to understand the derivative of such things and we already have such the kernel is just the orthogonal on some subspace. So, now we are interested to the following. So, this gives our original fox space gives rise to this problem gives rise to this original point process and if we consider the subspace f those functions vanish at point p1, pl then this we have orthogonal projection onto the subspace that has denoted by p underlying and this orthogonal projection gives us the point process and by Shihai Takahashi this measure is exactly the measure that we are interested for which will appear in the calculation of course cycle of the different morphism on such space. So, we do the same thing here we have something here and we get we obtain a kernel that depends on q and we obtain the point process here which is again given by Shihai Takahashi this thing. So, now our purpose is to understand the rather negative derivative between such two point process. So, it is very natural to study first. So, everything in fact if we completely understand the relation between these two subspace probably this will give us an information for these two point process and the reason that we study such kind of point process because there is a very simple relation between these two subspace and this is actually a very simple proposition which can be also a good exercise which says that p equal to d minus p1 pl z minus q1 z minus ql this means so this is a function multiplied by space which means I multiply each function inside the space by this function and put them together as a new as a new subspace. So, this means here if we denote g p q this is just those function f g p q f is in the space q of course this is very simple because the algorithm function that vanish at q1 to ql they can be divided by this polynomial and the only fact that we need to check and this of course this one vanish at this point p1 to pl the only thing we need to check is such things is indeed l2 with respect to the measure. Okay, then it turns out this function is very important and we have the following this function appears in our calculation. So, we can start with a simplest case where this psi is radial so this theorem is so we have in fact in two steps and the version that I will present here is obtained one week or two weeks ago. Okay, the first case when phi is radial which means that phi z equals to phi z modulus in particular and just erase this Gaussian case is in this case. So, then the first thing is the following limit that depends on p q so I will write p p as p1 to pl is q q1 to qk so this limit infinity product of the particles inside our set without accumulation point times this function to modulus to square x minus p i x minus q i for square i l this exists in l1 relation space with respect to this measure this is in the case when p when k equals to l actually this is the most difficult part to show such product which is which will turn out to be a infinite product actually converges. The second thing is we can compute explicitly this the expectation of this limit second delay the expectation of p psi phi q bar so always under this assumption psi p q is given by the following quantity so this one i j less than l q i minus q j square and the same thing so this is a fundamental determinant to power p i minus p j square times determinant of i the p i p j this is from i to l determinant i j from 1 to l the same thing for q and so in particular this means we can calculate explicitly the okay I haven't say in fact and also the relative derivative is indeed given by these quantities very explicit same so this is given by determinant of this q i q j over determinant of p i p j times the inverse of this i minus p j square i less than j i less than j for those q i minus q j square and times this limit psi p q x so the third thing is when l and k are different then actually we cannot compute the relative derivative derivative because they are just a singular these and these are singular they are supported in disjoint subset singular and I would like to say that this result when this phi is just as a Gaussian weight then the result the same result similar result is already obtained is due to osada shihai but with a very different proof this case is due to osada shihai in 2015 so okay this is the radial case how many times 2 12 okay 10 minutes and so probably I will not have time to explain how can we get such result but still let me state the result for radial case because it seems more there is something interesting there so in general general phi so first the following is true the following limit again exists and denotes again by so the the case a will be a particular case of this the limit of exponential of integral and some function that one will define later sum of function p i z minus q i z i from i 1 to l i phi z z d lump phi times the rest part so this is a correction term which in radial case will be 1 1 to l x minus p i x minus q i square so here k p a point k p so for example k p 1 z is given by 2 radial part or real part of the following function p of z I forgot actually this should be some p q which is explicit big one we want to erase the singularity at 0 this is explicit one plus p squared over 2 z squared and of course if lambda the phi is radial this is forget this it's just the integral will indeed be 0 and so every other thing are the things in case a hold erasing hold except we do not have yet with except we haven't yet get the explicit computation of the expectation explicit expectation formula which in fact conjectually is the same thing is just we in some in some compute in some proof there's one step we cannot we haven't yet overcome that difficulty mm-hmm so I have 5 minutes so I will briefly give a okay I forgot one thing here one this is one this I know it's here so they are singular and in particular I can say it probably okay this point process is gosh various rigid so this is this is already again true for the general case this rigid means this point process if we know the configuration outside the compact set then we almost surely know the particle inside this compact set okay so no this is not consequence this is the way how we prove that they are singular and actually the most so an important thing that we need for all this computation is estimate of so it's really from complex analysis of results of Christ's estimate of the kernel which says that we have such thing is given is controlled by some fixed say and the off diagonal thing so it goes exponentially fast to zero this is the one main ingredient okay I still have a few minutes let me briefly give give the intuition of this so you will forget every these limit things we just prove that the rather negative derivative is some constant times such thing and remember this remember that this is just the function between two to kernel so in generally we have the following CRM but which is very technical this is 2015 if we have a L this gives us the projection pi and this gives us as point process and this is not so it can be point process on some abstract face space not just a C and we have a function G for example here okay for simplicity let us take G positive it's not essential G L some function here we get new projection pi let me denote by pi G and we have we have a new point process them and the technical assumption on this pair on such pair assumptions on pi and G so in so roughly speaking the rather negative derivative can be computed and be computed as this a constant then constant normalization constant of G X so but actually this and this is just a roughly speaking this product usually so in general never converges so we indeed need like here this this is kind of some principle value print so we take the product over first the product over some ball then we let the ball goes big and big okay let me stop here


of the twins with their big lead, the Astros, the Dodgers. We have really three divisions that are heavily weighted now, ready to be runaways. Who do you think ends up with the largest division lead at the end of the year? Well, this is the Indians last stand, this series right here. If the twins, they lost the first game, if they lose this series, the Indians, they're done. They're waving the white flag. They're going to trade everybody they can, as they should. Now, the Dodgers have a huge lead, the Astros have a huge lead. I think the twins will end up with the largest lead, just because the division is so much worse than where the twins are at. So there's not a real contender. OK, you look at the Dodgers. They have the Rockies who made the playoffs the last two years, and they're charging. You also have the Astros. The As of some point are going to make a run. They were too good last year. They're too good of an offense. They're too good of a team. And they always seem to find a 10 game winning streak out of nowhere. Whereas you look at the twins division, they have the Indians who, at some point, are going to have to give it up and sell. The White Sox aren't ready yet. The Royals haven't been very good, and the Tigers aren't very good. So the twins can just rack up wins in their own division. Whereas even the Astros with the As and the Rangers are playing better above 500, they can't do that in their division. Only the twins have that division where it's like, OK, we're playing the Tigers. We should win two out of three every time. The White Sox, two out of three every time. The Royals, two out of three every time. And once the Indians sell, who knows what they're going to be? It's been a dramatic fall for the Indians. Quick, too. It's unfortunate. Quick, really. Well, they lost Kluber. He got hurt. Bauer hasn't been the same this year. They're starting pitching as Carasco hasn't been as good this year. Their bullpen's kind of fallen apart, other than Brad Hand at the back end. So they have no offense, which why? They have good names, Lindor. I mean, I know they didn't make any splashes. They lost Michael Brantley. Lindor hasn't been what he was supposed to be. Ramirez has been terrible since the second half last year. So they need help. And the only help I see is by trying to make some moves and get ready for next year. And the twins, even if they win, they want to avoid the Yankees, because it seems like. The twins don't want any part of the Yankees. Every time they fall to the Yankees. What about the impact? A lead-off guy and his leadership, you heard his manager talking about it, McCutcheon out for the Phillies. Well, I think Gabe Kapler summed it up perfectly. Not only his impact on the field, but in that clubhouse. He was a leader. You saw him with the handshakes with every single guy. I mean, how the heck can you remember 24 other handshakes with every guy he has? Well, that's incredible in his energy, his presence. And the biggest thing is his professionalism.  And he gets on base. He takes walks. He's a darn good left fielder, too. So not only the offensive side of it in the clubhouse, they also lose a great left fielder and a great presence. So this hurts the Phillies. Yes, they got Jay Bruce. Yes, they brought Jay Bruce in. And luckily, they did it before they even knew about this. But it weakens their defense. Jay Bruce is a nice player, but he's not McCutcheon. Herrera's out, so they have to move King Rita Centerfield, who was kind of their utility guy. It just weakens them, their whole lineup, and defensively. And let's not forget, yes, they'll be around. But when you're not playing, it is really hard to be a clubhouse president. All right, so the July 31st is that one final trade deadline for the Major League season. We talk about Phillies needing pitching. So now, do they need an outfielder? What's the priority? I think the Phillies could use a pitcher, starter, a reliever, and an outfielder. They need three, so they need to get on it. And they will. Is that just to win the division? If they, look, the Phillies came into this year after the moves they made with Rio Mudo, Segura, McCutcheon, Harper, they came into this year saying, we're going for the World Series. So yes, getting the playoffs, it's a great story. Like, if Phillie gets to the playoffs, yeah, hey, we made the playoffs. But they came into this season, World Series, to win the World Series. Well, they need help to do that right now. Yeah, and they need, I mean, they're doing this, they're hanging around first, without Harper being Harper, and hopefully he'll become the player they thought he would be.


Most of this information comes from the tax guide for small business for individuals who use Schedule C. Publication 334, tax year 2022, you can find on the IRS website, irs.gov, irs.gov. Looking at the income tax formula, we're focused on line one income. Remember in the first half of the income tax formula is in essence an income statement, but just an outline. Other forms and schedules flowing into these line items, one of those, the Schedule C. Having business income minus business expenses, the net business income from the Schedule C flowing into line one income of the income tax formula. When we look at page one of the Form 1040 note that the Schedule 1 is what the Schedule C flows into and then it flows from there into page one of Form 1040, line number eight. The Schedule C is a profit or loss from business having an income statement format, income minus expenses. We're focused here on the expense side of things and specifically on the rent expense side of things. All right, so rent expense. So when we think about rent expense, just remember we're not thinking generally personal rent. We're thinking the business rent has got to be ordinary and necessary for the business. You might be asking and thinking, well, hey, I do my business in my home. Well, then you have a home office type of situation and you might be renting the home or you might be owning the home if you rent the home, then yes, some of that rent might be business related in a home office kind of system. Okay, so let's get into it. Rent is any amount you pay for the use of property you do not own. So we know what rent is. It's not our stuff. We're renting it. We're just using it. We're paying for the use of it. So in general, you can deduct rent as a business expense only if the rent is for property you use in your business. So if you use whatever office building in your business or if you're renting equipment or something like that similar type of situation, then it would be a business expense you would think and you would be expensing it when you make the rent payments usually. So if you have or will receive equity in or title to the property, you cannot deduct the rent. So this is where it gets messy because if you imagine buying a piece of equipment, for example, then if you were to buy the equipment and finance the equipment, that's different than say renting the equipment. And a lot of people get this confused. And I think one of the reasons is because of the main thing that we purchase, the big thing we purchase is a home on the personal side of things. And we're so used to people saying, well, I don't really own the home. The bank owns the home. And they're referring to the fact that the bank has a loan that's secured by the home. And it's used, I think that's a joke, right? This used to be a joke. Well, the bank owns 80% of my home, but they don't really own 80% of the home. They have a loan, you owe the bank and the loan is collateral. They only have access to the home if you default on the loan. And the way to realize that is obviously the bank can't come to the kitchen table and have a discussion and say, I own 80% and therefore we need new rugs in the living room or something. We need to redo the kitchen. They don't get to vote on that kind of stuff. So renting is different than financing. So if we apply that to like a piece of equipment, then if we finance the piece of equipment, then we've got the loan that we have to put on the books to deal with. We're gonna be paying interest on the loan, which is kind of like rent on the purchasing power in order to buy the equipment. The equipment will be on the books as an asset because we couldn't expense it most likely because it's a big piece of equipment we're gonna use into the future. And then we expense it in the form of depreciation, possibly being able to have the 179 deduction or the special deduction to allow us to expense a lot or all of it upfront. If we rent it, on the other hand, then you can imagine we have a piece of equipment that we're gonna be paying rental. Now, because we don't actually own it, we're not gonna be able to put it on the books and depreciate it, but instead we're gonna be paying for it and expensing it when we make the rental payments. Usually you're gonna, as you use the property, you make the rental payments and you would be expensing it and when you make the rental payments. Now, these days, you would think those two methods would come out somewhat kind of similar in that like when you buy the property, they, you usually allocate the depreciation over the useful life.  But these days you get that massive 179 and special depreciation. So if you buy it, then that could be a benefit to the purchaser of over-renting if you get that massive deduction upfront. Whereas if you rent it, then you're not gonna get that massive deduction upfront. If it's a normal rent, you're gonna be getting the deduction when you pay for the property because you don't actually own the property. Now, it's possible to try to set up a situation that's structured in form as though it's a rental agreement, but in actuality, it's a purchase. So for example, if they set up an agreement that basically said that you're gonna rent it for the life of the equipment or that you're gonna be able to purchase it for $1 at the end of the rental agreement or you're required to rent it for so long that it'll actually account for like the whole purchase price of the equipment, then in format, you've actually bought it and you set it up as a rental agreement for whatever reason, possibly tax reasons on either the seller or purchaser side that preferred it to be formatted as a renting agreement as opposed to a purchase kind of system. So then we'd get into these issues where, well, was it really a purchase even though it looks like a rental thing and do I have to treat it as a purchase or a rental thing?