 It's an arms race. There's lots of apps for my iPhone that even two years after the iPad's been out still haven't been re-released for the iPad, yet in higher ed we have this sense that if we didn't build it, it doesn't have a lot of value. Are we going to develop for specific devices or are we going to develop for sort of a web-centric application? So students today are using apps in all types of different ways. So they're really wanting more and more. And I think they'll see things from other schools or in apps, you know, and different things they're doing and they'll assume that we can and we'll do those for them as well. We did take one side of the religious argument. We've come down on web-based apps. We don't think that we have the resources, honestly, to keep up in the native app arena. Well, I was going to say I think the administrator's mindset so far is that we've put a big effort into websites and they kind of think that's good enough right now. But the students are, this younger generation of students are much more into their phones than desktop web browser. But native applications are forking the web in many, many ways. So we have an iPhone app. Well, only people with iPhones or iOS can actually see that or use that part of the web. That's now carved out. An Android application, same thing. It also places a lot of power in new hands. So for example, the iPhone app store has notoriously had cases of publishing or refusing certain items of content as acts as a sensor. The primary things we're seeing are what you might think of as obvious. Students want to see their schedules on their mobile devices, see syllabi on their mobile devices. So they want to be able to have a map of the campus on their mobile device. Those things are what I would call non-differentiating. We have now got to figure out ways to have, we have to have mobile applications that differentiate the experience that we're offering to our constituents. I think in higher ed, we've always been in this buy versus build tug of war. And it's had, we've had slow maturity cycles. I mean, you look at the systems that higher ed is typically run. Those systems were there for a long period of time. We could make investments in developers and build an application and we were going to get five years, six years. We could do the ROI on that model, I think, very easily. And so we've got to look at that and we've got to look at new phones that hit every 18 months and say, are we really going to invest our staff, our development in doing that? It's really an argument that we had years ago in IT when we looked at what we could do with client server applications versus, you know, the web-based applications and where we could take advantage of the operating system and the other features of the device. I think you can make something. And I think those of us that are familiar with some of the apps that we download to our iPhones or our Droids know that they can be quite functional. A lot of campuses, I think, are seduced by the sexiness of having an application just for a phone. It's very, very difficult at a kind of global policy level to support that. This is a very crowded marketplace, device marketplace. And while there's some obvious leaders, I think there's a lot of shaking out that needs to happen, and I think investing in the web apps is a way to preserve our options.