RX 24 - Ask the Core Team

Transcribed Content

Okay. Welcome to the ask the core team session. Thanks to those of you who put in questions for us. We're excited to have a chance to answer them for you. This is kind of gonna be a a low key chill session. We'll do a q and a. The questions are in, so I'm gonna pose them to John. Most of them are about, certain product questions. I will say that questions that looked like they might be product support, we're not going to answer in this session. So we recommend that you connect with the community after hours or make a rockstar consult if you haven't had one yet. There will be a lot of people around that can answer those questions for you. So, please feel free to do that. We'll we'll not be addressing those in this particular session because that wasn't the purpose of this one. So shall we kick it off? All right. John, are there any plans for native chat features within the NextGen platform for web or mobile? Yeah. We've been talking about our desire to do chat. It's definitely a feature we wanna do. We know there's a lot of people in the community who are talking about it. I don't even think it needs to be part of NextGen. It would just be a feature ad. We don't need to wait. Here's the things we need. We need churches who will commit that this is something that they want because it'd be a pretty heavy investment. We could use some extra funding for that. We need to definitely nail down the requirements because chat is a huge feature. We're so spoiled by the chat platforms, whether it be Slack, Teams, you name it. There's like a thousand. And they all have different functionality from each other and different user experiences from each other, so we really need to boil that down to really a minimum viable product that we can go out with. Chat also is more difficult than it sounds because we also have to get that to work across Rock Mobile and web. And talking to churches, we just really feel like if you don't have both, it's gonna be problematic. Some people say, well, you should do it because you can get rid of Rocket Chat. And trust us, we would love to do that, get rid of Rocket Chat. But I think we take for granted how many, you know, features are in Rocket Chat. So that wouldn't be an initial goal. I don't think our initial goal is to create the most fabulous feature rich chat environment of all time. It's really to get come down to a finite set of chat needs and get those fulfilled. And then we'll do some rock magic, like maybe track interactions across conversations that you participate in a conversation. We're not going to duplicate all that chat data into the Rock instance, but the fact that you chatted, that might be something we wanna be able to easily report on in data views and such. So that's something we're very interested in. We just need to make sure that we can get enough churches to sign up for that. Another thing to keep in mind is we would be building this on top of a chat framework. So we're not gonna write chat from the bottom up. That it would actually be kinda crazy. These frameworks do have costs. So there's monthly costs you have to pay for that. It's typically billed on monthly active users. And depending on your usage, it it may not be that many or you might have a lot. One of things that we think about too as as we do this is putting that down as an addition to the AppFactory monthly cost. The benefit of us aggregating those costs is we can share monthly active users. So typically, there's going be a minimum number of monthly active users that you have to have to have the platform. In most cases, that's gonna be more than you need. So by aggregating, we can get, you know, lower the cost for you but also get economies of scale. These chat programs are really good. Our frameworks are really good at segregating those users so you don't have to worry about, you know, the the chats coming across. You'd have to basically have to guess a GUID, which is nearly impossible to to switch over to a channel you didn't know about. So we have a lot of thought and research. I think there's people in the community. You know, Mika at Sun Valley has done a lot of ideation about what this could do. Tim Lemons runs a group of digital strategy people interested in digital strategy, and there's been a lot of discussion there. But I think we just really need to get final commitments to do it because I don't want us to invest a lot of resources in something that turns out not to get well used. Alright. Thank you. I have a two part question. Part one is when is v 17 being released to alpha? Yeah. I wish I knew. Like I said in the keynote, we have to finish the communication wizard. Actually, I should say we should have to start and finish the communication wizard. So we're still right now in the design phase of that and really trying to balance the power and the simplification together is the last remaining hurdle. We have not had a lot of time to focus on that. We've had a lot of other projects like Check-in v two, LMS. The LMS project, again, I cannot overstate how big that feature is and how great it is too, but that took a lot of our design resources away. So now that we're on fit and finish on that, coming out of the conference, our primary goal is to get communication wizard designed and then to development. That said, I always say this like, oh, after the conference, we'll get right to that. I know I always say that for every conference. This one's been much more than usual so I started writing all the things I promised to start after the conference and I'm up to like 30 or 40 in my Asana task So I kind of chuckled to myself when I told someone at the conference, hey, I'll get back to it right after the conference. I'm like, oh, that's another one. So we are inundated with with stuff that needs to be done, but but we do wanna get that out. But I I I think I'd be lying if I were to give a date right now. Okay. Part two of the question. Is next gen check-in in v 17? Yes. Our recommendation for next gen check-in is that you go very slowly. So realize that the configuration is compatible, so you don't have to, like, keep two things configured and in sync. It all uses the same configuration except the labels. You have to remake all your labels, but that shouldn't be too hard with a new label designer. And what I would say is if I if I was you, I'd I would put like a one kiosk over in the corner. In the first weekend, I'd probably have like one or two staff people check their kids in with that. After a few weeks when that's pretty smooth, I'd have your some subset of volunteers check-in with that and then slowly roll that in. So I don't wanna say it's gonna be like event registration where we had to, like, retweak a bunch of stuff. These features are very complex, especially checking because there's so many different use cases. One of the things that we did that I think is kind of interesting, we created this little harness internally that basically you can automate a check-in process. And so we're using that to validate and double check our work with all the algorithms, making sure all the algorithms work the same. So we've really been focusing a lot of time and attention on that so that we can make sure that the QA is as good as possible. But it's definitely not something you would just install in all your kiosks in one week and just walk away. At least not until a whole bunch of people have already done all the testing, then maybe you could. But Okay. Here's a really good question. Regarding your desire to be more accessible for smaller churches, would you consider having a mobile app that functions like the Rock Core app where we can run our own mobile instance? However, having a simple welcome screen to have a form for a unique key that would connect the member's app right to your Rock instance. Yeah. That's something we have talked about in the past. Our biggest problem is not having I enough ideas. It's having enough resources. And when I say resources, there's two parts of resources. I mean, a lot of people when when I say that, they think money. Well, that's definitely one. But human resources is the hardest. We spend so much of our day recruiting. Cassidy has been running around the the conference like crazy. She's been amazing at the conference, but she spends a lot of her time on recruiting and doing video screens and connecting with all the different platforms we use to do recruitment. We also do selective recruitment where we go into the Lincoln and we're looking for specific people, and then we target them and invite them to to apply. We also spend a lot of time at universities in the Phoenix area. Grand Canyon University is a a very big university here. It's actually a Christian university too. And so we go on campus and we present at classes and talk about, like, what it's like to work in a faith environment and with technology. We've had some great hires from Grand Canyon. The person who wrote the programmer who wrote the new settings thing was right out of college. He's only been with us, you know, a few months. And it's just so cool because he's, like, so on fire for what we're doing. And he loves technology and he's like I was just talking to a day and he's like, I just love that I get to do this. And and then I was like, what do you think of all this? He's like, I'm just blown away. So it's pretty cool. And he's a great developer too. That works really well too. Braden's another one who's super young and is making a huge impact. Like all the they used to be Daniel Hazelbaker did almost all the programming. I did some, but he did a majority. Daniel doesn't do hardly anything with Rock Mobile anymore. Braden's completely taken over everything for that. And to do that at such a young age is, like, unheard of. And if you went to a session, you realized that he's a really good communicator too. We actually didn't really even know that. I guess like, you're gonna do the two product keynotes. And he's like, oh, that's so awesome. And then I was like, have you ever presented before? He's like, nope. I'm like, well, this is gonna be fun. And he nailed it, like 10 out of 10 in my opinion. So when we have all these features, our heart is to want to do all of them but we're limited by resources. It's almost like you're playing this I I don't gamble, but if you're playing this big thing and you're having to place all these bets and you don't have enough chips, so you have to strategically put your chips to to try to cover as much as you can with the limited resources that we we have. That's what we do all day. We're trying to figure out what's the best way for us to use the resources, the human capital that God's entrusted us with to maximize the kingdom impact of what we do. So this is an idea we have thought about, but I I love the fact that it came up again because sometimes you have these ideas and you forget the idea. And and this is a good reminder of the GI. I I think it's one that we probably should move up higher and and get to soon, especially as we talk about accessibility. I was just checking a Brayden a day. We have a Brayden and a Brayden. Boy, that's confusing. Although we have three Jonathan's. But that's actually a good thing, I think. Oh, boy. So just to make sure Apple would allow that because Apple's pretty tight about what kind of stuff goes in there. And he thinks that we had no problem. So it's not a super hard thing for us to do. And I think it would have a big impact. So those are the types of things we like to prioritize too because if we can not just spend a lot of time and it has a huge impact, I think that's great. It would still require that you have a Rock mobile app designed and configured on on your side, but it would greatly reduce costs and complexities of getting it deployed to the App Store. Longer term, of course, we love it to ship out of the box with a very, very basic app that you could just change your logo and maybe your colors. Again, we would love to be able to do that too, but that would be a much larger investment in time. It would have a good impact too, but that's a hard amount of time, a lot of time, and a good impact, you know, where what's gonna trump that is easy and big impact. So I just wish there were more hours in a day. Definitely. John, will there ever be workflow action for printing a label? That I'd never thought about that. That's that's a really good one. And I would say probably the answer would have been no until we had Cloud Print because in most cases, that has to come from the server. And we know most of you can't do that today because of your firewall rules. I was talking to someone a day too and they're they were just having, hey. Yeah. We did set up the VPN and, boy, is that a lot of work. And occasionally, Azure drops a couple packets and then your label doesn't print. So I think with the advent of Cloud Print is the only thing that would even enable that to even be an option. But now that we have that, I think that's a great option. We'd have to kind of think through how it works, you know, like how you configure it to make sure you had all the right you know, the labels need a certain bit of data so they they have all the right merge fields to do its thing, but it certainly is not impossible. I like that idea. I never considered it. But I think first, we'd have to get cloud printout and get you guys adopted and running it, and then it would make more more sense, I think. And it would also have to go on the ideas board. Yeah. That's a great place for it. Vote it up. Alright. On one of the most recent podcast episodes, NFC was talked about very briefly and that a lot of research has gone into it. Where can someone start to understand the research that the team has done? I'd highly recommend going to the session that we had on NFC, which was just the last session. That's why I'm out of breath. I was asking Trevor down there, when's the next session I need to be at? He's like, 04:05. I look at my watch, it's 04:04. I'm like, oh. And down there, you mean in the downstairs rooms off the Yeah. So that's why I'm out of breath. So anyways, so you missed that, but we do there is an NFC white paper that was just published by Triumph. So we've been doing, like I said, a lot of research in NFC. The good news is it's not hard. It's like pretty easy. There is a lot of lessons learned, like little teeny micro lessons learned. So we've gathered our all of our project notebooks. We wrote it up as a white paper and we just put it on the the Triumph website. I think almost anybody can self-service that kind of project. If you need help, any partner would be willing to help you with it. But I really feel like most churches could probably just do it themselves. And we just wanted to provide everything we knew on NFC so that we could jump start your project. And we'll continue I just wrote down there some more notes that we need to add to that so we can kind of keep it as a running notebook of what we know. So the good news is it's powerful and easy. To use it as check-in like we did though for the conference is going to require v 17. There's some you know, v v two check-in required for that, and we need to get that out. But you can get started today with doing some really cool things with NFC. It's not hard. So look for the white paper. It's I think it'll really help you out. Okay. Are you ready for the next one? Sure. How do you pronounce SQL? These kind types of questions always scare me because I've gotten one in the past. How do you say and specifically to me, targeted to me, John, how do you say Azure? And so it makes me think, well, I must be saying it wrong. But Azure can be Azure or Azure. I say Azure. All the YouTube videos I watch say Azure, so I think I'm saying it right. But Azure is good too. I say SQL. You can't say SQL, but it was funny when I was I was making that AI video about the SQL. Did you see that AI video on SQL? Like, I put SQL and it didn't know what to do, so I had to spell it out s e q u e l and then it got it right. So that is probably has to be the appropriate way. If AI thinks that, then Whatever AI thinks for sure. Two out of two people think SQL. Do you have a timetable of when the old blocks will go away and will have to use new Obsidian blocks? Well, it's when v next is done. We and that's, you know, kinda at the point where we're at. We have a lot of the hard work done. Now we have to just do the grind of just replacing all the blocks. Now we have a pattern for how we replace blocks. You know, a lot of times we like to chop them. So chop means we take away the old one and we put the new one in its place. The good news is you don't have to do anything. It's just automatically the block settings all come across and everything. Sometimes we'll swap it, which means that we'll put the new one in its place and we won't take away the old one. Just in case we miss something, you could always manually swap it back. We try not to do that because that eventually means that we have to then later do a chop to get rid of it in case you put it back. And then sometimes we just kinda like sneak it in there and it's that's meant for you guys to kinda play with it before we swap it or chop it. So like the group scheduler, the new group scheduler is a very different block and we kind of like snuck it in there and some churches are using it. I think we need to go back now and probably swap it and then that one will eventually will chop it. But our goal is to keep this as transparent as possible. We've noticed that new Obsidian blocks often do not include IDs on many of the output elements like the web form versions did. See family preregistration for an example. We often relied on these to target elements for styling or JS on a page. Was it a purposeful decision to remove these or an oversight? Yeah. I was talking to Daniel about that, and it wasn't purposeful. I think there's a technical reason why it makes it a challenge, but we're committed to try to figure out how to get it in there. So we'll we'll circle back to that after the conference and try to figure out how to get that back in. What are your plans to upgrade the experience for creating and installing plugins, and why is there not a search bar in the plugin store? The real answer and the truthful answer is we didn't need one when we started. We had like six plugins. Why would you need to search? That's a lot of the reasons why things are the way they are in Rock is because it simply wasn't needed when we made it and then everything grows. And you'll never know that you need something like that until past the point that you need it. I mean, sounds weird but that's true. Like, you don't know you need it until you're past the point of needing it. So in hindsight, it's like, well, of course, what are you thinking? But when you only had six plug ins, you didn't need it. So that was something I, again, put it into the I b idea board. I agree. That's a great idea. Like, no one would argue that. It's just great to see the community say, okay. Again, going back to our resources and we only have so many chips, do we burn chips on that? And it helps when you guys say, yeah. We think that's a great idea. It derisks us to now put those chips on that. So in a sense, you're starting to, like, change the betting structure a bit. And and sometimes there might be a feature like, we don't think it's that great of an idea, but if you guys vote it super high, it doesn't matter. It's like, okay. Well, give the people what they want. And as long as it we would never do that if we thought it was counter to the strategy or vision, but that's really rare that we ever see an idea that's like we actually think it's a bad idea. Like, I I can't even think of one that we've seen come in that we thought was a bad idea, how valuable it is. But just know you know our heart, like administrative features versus ministry features. And I think, you know, another way to look at that is, you know, administrative features, I'm not wrong, but it ain't right. If you're a hair for the comedian, that made sense. But otherwise, you're probably thinking I'm weird. When are you skipping around the room? After the out of breath has come up the stairs, I don't think I I was kind of like, props for him. He skipped a lot, and he was not that out of breath. A little sweaty. I was literally sitting there going, wow, it must be really hot up there. I'm gonna be sweating like a storm. And then I realized, oh, no. He's been skipping the whole time. For the LMS feature that's coming, what can we do right now while we're creating training content so that we're prepared when it comes? That's a great question. I would say keep going on the content. The content is what's gonna take a majority of the time setting up the LMS. So I think soon we'll be able to publish some documentation or some Figma to kind of give you an ideation of like how the activities we see them being broken down because I think that would be helpful. But just know, like, you just create atomic content, like small videos, like chunk it. And I think that's pretty obvious. I think that's what you would do anyways. But I'd say keep working on the content. I just had a conversation with healthy healthy growing leaders, and it's kind of fun because we as we talk with you guys at the conference, the product starts to make more sense. The the features start to ideate and make more sense. I was like, Greg, what we need to do is, like, we need to make help you make a plug in where you can take content about the Discord or the motivators and then you can put it in the rock shop. And then churches can come and like, you know, get that and bring and that by installing that plug in, it automatically gives you content in your LMS. So you could just go one button click, puts it into your system, and now you have a whole training class on disk for your lay leaders or your staff or whatever. So sometimes, you know, these ideas, they were never meant to be but when you start collaborating with people, you know, it wasn't Greg's idea or my idea, it was just us standing together, you know, brainstorming the value, the credible value that he provides and how do we make that value more accessible. And then it's like, boom, we I was just talking about LMS. How do we make LMS work? And we walk away from that conversation both better off. Okay, John. You know how when you take a DISC assessment, the results that you get are limited, but other people can see more data about your assessment. Why is that? I don't know. You can customize the results. I would love for whoever sent that in to tell me more because I'm interested. I think the disc scores I think all of the assessments in rock are probably one of the most underutilized parts of rock. It's free. And the impact you can get from that at scale, you can send that out to 2,000 people and you don't have to do anything. They just take it and you get it right back. So how do we make those assessments more powerful? I would love more ideas on that. It's not something I have in in my day that I can set up a time apart to figure out the why and the how, but if someone can help me understand a little bit more why the the how and maybe or the why and then some ideas on the how, that would is very helpful. I do know that we want to keep pushing on that. One of the ideas I was thinking about the other day is like a lot of churches do an at the movies. Who in here does an at the movies? Yeah, a lot of churches. How cool would it be if you send out to all the people in your congregation at the movies, what movie star are you most like? I mean, do that on Facebook all the time. You give them the disc test and at the end of the disc test, it tells you what movie star you are. So it's kinda cool content. Now I'm like, oh, I'm like Tom Cruise. But at the same time now you have a ton of personalization and you have a ton of ways you can make that more ministry impact. So how do we make it fun? So Greg's actually working on for me like a list of movie stars in their Discord so that we could create a recipe around that. And he's also gonna do it for, like, sports sports athletes. And he already has biblical characters. So how do we make this content fun? Because then we can do amazing ministry based on it. So we are really wanting to keep ideating and and improving those assessments, and so is so is Greg. He would love to be able to help you and help you understand that to a deeper level. All right. Next question. Is there a plan moving towards an updated front end UI? Bootstrap three is a fairly old framework, and there are a lot of new options. Yes. So technically, don't use Bootstrap three. We we have Bootstrap three plus plus plus. Like, we've added a lot of Bootstrap four into three. We have a lot of other things we want to do. Here's the thing I don't think we will ever do. We will never marry ourselves to one of these frameworks. We learned a lot by doing that because when we marry ourselves to a framework, we've made the decision for you that you are now married to those frameworks. And when those frameworks upgrade, they break everything because they don't care about, like, upwards compatibility. They and honestly, they shouldn't. Like, I I get why they don't. But you've already invested tons of money in your websites and your themes and all kinds of styling that we can't just go choose and break. Like, we will not do that. So, yes, we're actually working right now. We have another student that just got hired on and and he's working a % with me on recreating and reimagining the the styling. Our goal is to make it compatible with the with the utility classes that we have today, and then we'll add stuff to it. Braden at his session talked about how we had a standardized color theme in Rock Mobile. Well, that work actually came from the work we were doing on the web. So they're gonna be combined. So you can pick we're gonna have standard, you know, coloring, typography, spacing, etcetera. It's gonna be based on CSS variables, so it's gonna be very responsive and easier to to do. It's gonna be very modern. But what we're not gonna do which which I'm not gonna do I'm gonna channel my Mike Goodman. Is we're not gonna like marry ourselves to a CSS framework because they don't care. And they shouldn't. But we're gonna take the best from them. And we we we've done it today. We've pulled some stuff from Tailwind and brought it into Rock. We've taken a lot of stuff from Bootstrap four, a little bit from five, some from Untitled. So we're just stealing the best. When is Ask Chip gonna be updated for better, more accurate information? Yeah. He's he's a character. I'd probably say the honest answer is when the search when the AI tools get a little bit better, they have a big problem with flat out lying. There's a better term for that in the AI space, hallucinations. They hallucinate facts. There are better ones and I spend a lot of my personal time researching that. There's a whole area of of AI called RAG, retrieval augmented generation, and that's what that service is. And we're constantly trying to find new, better ones. I think Microsoft's got some cool stuff with Copilot that you can build your own agents and and things and we're playing with that. It goes back to resourcing a little bit too. When do we put chips on this? I can tell you one area I've really researched a lot is trying to get it to know the data model of Rock better so that its sequel and lava will be better and that is not working well. I mean, I I can't tell you the level of research I've done on that. And for the most part, everybody's in the same boat and saying the same things. Microsoft just put something in Azure. Let say it again, Azure. A way to do it'll generate the SQL statement for you. So if anybody can do that, right, right, they have your schema. It is Microsoft. It's Azure SQL. The SQL it pumps out is like straight applies too. It's like there's no table called that and you know that. It's funny because when I'm doing that I'll say like, show me all the tables that have a column called this and I know there's five and they'll return like three. I'm like, is that all of them? Yes. That is all of them. I'm like, what about this table? Yes. That table has a two. And I I have no problem going back. Why did you lie to me? Well, sometimes I I'm like, no. You straight up lied. So we're working on it. I've even made my own rag of it where I've you got to I mean, as you do it, it's all about chunking the data into little chunks and then you have to vectorize it and then you can do the search across it. Like I did it all myself with it and it still didn't do a very good job. It was better than than the other ones because I I I can be more descriptive exactly of what our data model is, but AI is an amazing thing, but it's also really stupid at some things. I'm hoping with the new chat GBT five, which is supposed to be coming out any day like Strawberry, it's supposed to be much, much, much better, but we'll see. Next year, can the app offer a place to take notes for each session? It could. We have that capability in Rock Mobile. It's just, again, resourcing. This last year, people really wanted feedback, and so we implemented that. It's now when we add that this year, it's easier for us to obviously do that again next year. It's it's not like free. We still have to like reconfigure it but it's copy paste, change a few things. And with our rigging pattern, it's become a lot easier. But it does all of these requests are all good but they all take away from the finite number of chips that we can spend. So, yeah, we we have that capability. It's a good idea. You know, I think we'll have to look at how we're doing in preparing for the RX next year and see if we can add that or not. Yeah. Does the announcement about the new mobile block mean functionality for other giving vendors is decreasing? No. I think that's been a question that I've heard a couple of times. No. It's not decreasing. Giving vendors for years have been doing giving experiences inside of Rock Mobile with a web experience. And you can't tell the difference. Definitely, the average person using these mobile apps cannot tell the difference between a web and a native. And so that's been satisfactory and happy for for many, many people. We just simply wanted to also have a native experience for that. So we are not taking away anything from the giving experience that has always been in Rock. We have a plug in architecture and a provider model to support any giving vendor that wants to use event registration and our giving blocks, Like Spark has created giving blocks. They can use ours. But for years, I've been telling giving vendors, yeah, don't go recreate your own event registration. That would be crazy. Trust me. You don't want to do that. But you probably shouldn't use our giving blocks. Why would you just you guys are experts on giving. Why would you just wholesale use our user experience? That's where you should ideate and innovate is on the user experience around giving. It wouldn't make sense to do that for for event registration, but for giving, you should. So we've added one capability into into Rock Mobile. That's it. We haven't taken away anything. We don't plan to take away anything. We think and have thought from the very beginning that options are good and Rock should be an open platform. No one should ever be able to to be kicked out of of the Rock ecosystem. We've seen church management systems do that. It's quite quite often. As soon as they get bought by a company that owns a giving platform, it's common that next thing that's going happen is you get ejected if you're not their giving platform. We would never do that. Not only just because it's the wrong thing to do but because it would be not what you guys need or want. We want you to have options. In this case, because of the technical requirements of writing this for mobile and all the security required, all the authentications and encryptions and PCI compliance, like that credit card cannot touch our code. Otherwise, it's not PCI compliant. So creating those level of abstractions on the web is very difficult, but we did it. It's orders of magnitude harder on mobile and we simply can't do that. Again, it goes back to the chips. Right? If we took every one of our chips, we could do it. But is that the best use for you guys? No. Especially not when there's another option, which is the embedded web giving, which you can still have highly customized user experience. So, you know, maybe our messaging from stage could have been better. That's possible. We can always do better at that. Just know that we also gave or at least we Spark gave twelve, fourteen hours of content. Actually, it's probably more than that. That we have to prepare for this. And I personally had to prepare seven hours of content. So to get every messaging point just right, especially when someone was saying, how do you remember all that? How do you memorize all that? I'm like, I don't memorize that. I just get up there and I kind of know and I've gone through it enough times that every time I go through it, something else, something different comes out of my mouth. Sometimes better, sometimes worse. But so that one maybe we could have been clearer. But yeah, we're not taking away anything from The Giving. We just added one feature into Rock Mobile. And unfortunately, it's very hard to make that extensible. And I think that's one thing from a programming perspective that's very hard about Rock. And and when programmers come to our team, they're blown away by the extensibility. Now from a programming perspective, that means when we're programming, we have no handholds. We have nothing to nothing firm to hold on to because everything can move and be reconfigured in a different way. So it's it's almost like silly putty and trying to be make something very structural out of Silly Putty. It's very flexible and extensible and you guys love that, but it's very difficult to code. And so sometimes I think it can be we can forget how hard that is. And so in this case, it was just a decision we made to say, well, we can have this feature and it can work like this or we can never have this feature. And so we thought, well, know, MyWell's a nonprofit. We're a nonprofit. A lot of you guys use MyWell. But if you don't, well, great. You still have other options. You can still use the web view and it's just as good. So that's our thinking on that. That was the last question, but we still have five minutes. So if you guys have any other questions or you want to follow-up on one of those, definitely feel free. Questions? Yeah. I was interested in the peer network Mhmm. Feature. And I was wondering when you did the relationship diagram, are those names that they're connected to gonna be clickable? And is there a way to highlight specific people like group leaders or staff so that we could see that visually too who's connected to them? Yeah. You know, Daniel and I did all that work, but it was a couple months ago. I can't remember if they're clickable. You can definitely see them. I think they are clickable. The colors that I showed are by group type. So if one of those group types was like a staff one, you could color code it a different way. There is a lot of dynamic abilities there. Like the size of the circle on the inside is the size of the connection they have. So there's a lot of information in that diagram. And that was a very simple diagram. Some of the diagrams we have will have thousands of those. And it's pretty cool because you can zoom in, zoom out, and see it all. I'll have to go back and double check on the clickability. But if it can be done, we'll definitely want to do that. But yeah, that's one of those features I was super into a couple years ago when we had a former system, which I won't name its name, that we replaced with Rock. But we wrote that former system and I was really at that time into social network analysis and it's always been something I've been dying to get back to. And it was just it felt like it was the right time. And especially we have a new person on staff who's gonna be specializing in dashboards and trying to create more metrics. So ERA, think is I love ERA. Think it's a great metric. It's one of the only common metrics that I know in the church space that has a unique has a defined definition that's consistent across all churches. Average weekend attendance, you would think would be that too, but it's not. Every church counts it differently. And we wanna create more insightful metrics like that, and we now have a person who's gonna be helping us with that. And already he's helped us at at a Spark perspective, like the metrics that Emily's talked about and how we're trying to really polish those out and make them very consistent and measurable and accurate. He's really done a lot of work helping us with that in preparation for the conference. And now that the conference is over, he'll continue to do a little bit of that for Spark, but we want to start moving into how do we give metrics out of the box that give you insight into what you're working on. For example, one of the things that we need to know from every instance is what is the what was the weekend attendance for the last weekend? Most of you guys have metrics in your database that measure that. The problem is we as the core developers don't know which metric that is. But we need to know that so we can start creating other metrics, so we can divide that number in a lot of different clever ways. So one of the things we've added into Rockets in pre alpha right now is you can pick a purpose for that metric. So we're going to ship some purposes like which metric is weekend attendance. And because you guys have already installed it, you don't have it picked but you can go pick it. And then once you pick it, it'll unlock other capabilities in the future for us to know that because that's a key number for some of the metrics we want to work on for you. And we have a couple other purposes that we ship out of the box with. So a lot of new thinking going around metrics and how that will work and social network analysis. I'm like just over the moon that it's gonna be in '17. And I'm also shocked more people haven't asked what that does. A few people in Masterclass did. But and I think we had a slideshow a slide in Masterclass in the beginning. It's like pure network and it was a cake that was all like flat. It's like, yeah, that cake is not cooked yet. Any other questions? I think there's one in the back. Oh, okay. Last one. I look forward to coming to these conferences every year, and I hear a lot of churches sharing what they've built or just wanting to share with each other, and they all say the same thing, like, we've built this, but we want this for the community. And a lot of times I feel like there's a gap, like there is the recipes page and stuff like that, but it feels a little clunky. Are there any ways that we're trying to improve just areas that churches can share, best practices for their processes, for things that they've built in Rock? Just any ideas on how to kind of advance that intel sharing between churches because they all want that so much. Yeah. You know, one thing I would say is and I I did a slide, a a session a couple Rx's ago and I had a slide that says you're not done until you shared it. Like, if you're in in the army and you fight your battle, that's great. But if you can pass it to every warrior here, you've magnified your impact. So you're not done with the project until you shared it. What I do personally is I create videos that are then almost like a session here. Like if you go to the Triumph site, there's a ton of architecture videos and I'm not done until I've made the video partly so I can train the team that I work with. But if I'm being honest, I use those videos a lot myself just to refresh myself like how a SQL thing works. So I would just encourage you like you don't have to wait till RX to do a presentation. Right? You can make videos whether they be five minutes, fifteen minutes, or fifty minutes. And I would encourage you to do that as a part of the sharing process. You can post those videos as a recipe. You can post those videos into Rocket Chat. You know, you can do what we did. We we created a page full of those resource videos to share out. And then if you make enough of them, people are like, oh, hopefully they we have we have a way you can like sign up for a newsletter and every time we post a new one, get a you get an update. I would think video content just showing that and not waiting to Rx. A lot of times people are like, I'm gonna wait till Rx and do that. I'm like, well, you don't have to. You could just do it now. But here's what the devil tries to tell you, oh, that's too hard. It has to be perfectly and polished. You can't say, you gotta start over. And I would say don't. Just get it done. Just get her done. It's okay if you say it's okay if you get off track. Like, do you guys care? I mean, when you watch a video like that from the community, you're like, oh, okay. Small problem. But the the value of it is so huge. So don't worry about overproducing it. Yeah. Well, I know we're out of time and we gotta head over to the closeout. So we appreciate for you coming. Appreciate the questions. Hopefully, they're helpful. And we'll see you over in the main hall.