Ordered List Blog

Open Source Themes for GitHub

2012-04-05T10:31:56-04:00

I had the opportunity to add a couple themes to the recent launch of GitHub Pages. Today I’ve open sourced the HTML/CSS on GitHub for anyone to use and improve.

Modernist

View or fork this theme on GitHub

Minimal

View or fork this theme on GitHub

Back to the Basics

2012-02-28T15:37:13-05:00

Since the acquisition, it’s time to transition this site back to my own personal blog. I’m so excited to have a place to experiment, write, and design as myself, and not as a business.

A New Design

When rethinking and redesigning, it’s best to start simple. I’ve taken a very minimal approach for this refresh. It’s clean, spaced, and responsive. Simple.

Time to Start Writing

I’m looking forward to, once again, posting more informative snippets of design and code. Posts that are more free-form, and outside of a business strategy. I’m hoping this transition will get me back into the habit of writing on a more regular basis. I miss it.

A Renewed Focus

If the idea is indeed to write, the focus of this design should be on the words. To that end, the design is purposefully empty. I hope you enjoy it, and I’m excited to have this space to experiment once more.

Ordered List Acquired by GitHub

2011-12-05T13:02:46-05:00

I’m excited to announce that as of today, the team at Ordered List officially joins GitHub in its quest to build the best developer tools in the world. We’re bringing along our talent, our passion, and our products (Speaker Deck, Gaug.es, and Harmony). And we couldn’t be more excited about our future together.

Why Join GitHub?

For one, we truly believe that GitHub is one of the best software companies in the world. They’ve surrounded themselves with the best people in the industry, and we’re honored to be working along side them.

But even more importantly, we’ll be able to focus 100% on making our products, and GitHub as a whole, as simple and beautiful as we can. This has been our mission for the past 2 years, and now more than ever it can become a reality.

What Happens to Ordered List?

The most prominent change will be the end of our client-service business. We’ll be working solely on our products, and new challenges at GitHub. Our team will stay together as a unit, continuing to build great software. We’ll also have the expertise of the rest of the amazing team at GitHub to help us solve software problems like never before.

What Happens to Your Products?

GitHub cares about their customers, and they care about ours as well. For the short term, it means that not much will change at all. In fact, it means better, more frequent updates and feature additions, more stability, and even better support.

For the long term, just as before, we will continue to evolve our products to best meet the needs of the market and our business.

The Past and the Future

It was just a few weeks shy of 5 years ago that I started Ordered List as my full-time consultancy. I’m proud of what it’s become, and what we’ve built. And I’m proud to join forces with GitHub. Here’s to the future!

Share Presentations without the Mess

2011-09-26T15:30:49-04:00

Around a year ago, tired of posting our presentations to the ad-cluttered and flash-ridden SlideShare, we started hacking on Speaker Deck.

Our focus at Ordered List is simplicity and beauty. We asked ourselves, what is the most simple way to share a presentation? The answer we kept coming back to was a collection of images. This is exactly what Speaker Deck is.

Simply upload a PDF, which every presentation software worth a dime can export as, and we turn it into a collection of images.

We then wrap those images in a beautiful interface that allows you to easily preview and navigate.

Focus on the Presentation

As you can see from the screen shot above, on Speaker Deck the focus of the presentation page is, well, the presentation. It is large and in charge.

For You, By Us

We built Speaker Deck for ourselves, but we have some great news. As of today, Speaker Deck is free and open to all.

We promise that we will never clutter your presentations with ads and we will do our best to keep it free and simple to upload and share your presentations without the mess.

For now, we will include tasteful advertisements for our own products, Harmony and Gaug.es. At some point, we may allow others to advertise, but we promise to always keep it tasteful.

A Big Thanks

Finally, we had a lot of help from over a hundred private beta users. Their patience and feedback as we hammered out some issues was absolutely priceless. If you were one of them, thank you.

What are you waiting for? Sign up for an account, start sharing presentations, and let us know what you think.

Flared Borders with CSS

2011-05-04T14:15:52-04:00

Ever wondered how to create an element that flares into another using only CSS? Here’s a quick tutorial using existing CSS attributes, in combination with CSS generated content, to produce the effect using no images at all, and no additional markup. And it falls back gracefully for older browsers.

Let’s start with a mockup of what we want to build. And, if you want to jump right to the end, here’s the finished demo for you to examine.

So first, we start with our markup. For this demo, it’s a simple unordered list inside an HTML page.

<!doctype html>
<html>
  <head>
    <title>CSS3 Flared Borders</title>
  </head>
  <body>
    <ul>
      <li class="current"><a href="#">Home</a></li>
      <li><a href="#">About</a></li>
      <li><a href="#">Products</a></li>
      <li><a href="#">Services</a></li>
      <li><a href="#">Contact</a></li>
    </ul>
  </body>
</html>

Once that’s in place, we can start with our styles. I’m going to style up the basic, non-flared navigation bar to start, and we’ll add the flares next.

html {
  background:#efefef;
}

body {
  margin:0;
  padding:0;
  color:#222;
  font:13px "Helvetica Neue", Helvetica, Arial, sans-serif;
}

ul {
  position:absolute;
  left:0;
  right:0;
  top:0;
  height:30px;
  background:#959DA5;
  border-bottom:1px solid #333;
  margin:0;
  padding:10px 16px 0;
  list-style:none;
}

ul li {
  float:left;
  margin:0 20px 0 0;
  padding:0;
}

ul a {
  display:block;
  color:#fff;
  text-decoration:none;
  padding:0 15px;
  line-height:29px;
  height:29px;
  font-weight:bold;
  background:#464646;
  border:1px solid #333;
  border-bottom:none;
  -webkit-font-smoothing:antialiased;
  -webkit-border-top-left-radius:8px;
  -webkit-border-top-right-radius:8px;
  -moz-border-radius:8px 8px 0 0;
  border-top-left-radius:8px;
  border-top-right-radius:8px;
  text-shadow:#000 0 -1px 0;
  /* This is to prevent jagged borders in Webkit. */ 
  -webkit-background-clip: padding-box;
}

ul li.current a {
  background:#efefef;
  color:#222;
  height:30px;
  text-shadow:#fff 0 1px 0;
  /* This is to prevent jagged borders in Webkit. */ 
  -webkit-background-clip: padding-box;
}

After that styling, we end up with this.

Adding a bit of Flare

Our next step is to recreate the flare effect. We do this as a combination of two steps. First, we cover up the bottom left and right outside edges with the same background color as our tab. Because we don’t want to put markup in our HTML for this effect, we’ll use CSS generated content, which has surprisingly good browser support¹. ¹ Quirksmode has more information on CSS before and after psudo elements.

So let’s grab the :before and :after of our list item, and create these blocks. Note, that because I’m positioning these psudo-elements absolutely, I’ll need to position the list items relatively to keep them in line.

ul li {
  position:relative;
}

ul li:before, ul li:after {
  content:'';
  width:9px;
  height:8px;
  position:absolute;
  z-index:2;
  bottom:0;
  background:#464646;
}

ul li:before {
  left:-8px;
}

ul li:after {
  right:-8px;
}

ul li.current:before, ul li.current:after {
  background:#efefef;
  bottom:0;
  -webkit-background-clip: padding-box;
}

Let’s walk through that a little. First, I select both the :before and :after psudo elements, and set their content to an empty string, so they’ll appear on the page. Next, I position them to the bottom of the li, set the width and height to something slightly larger than our border radius, and set the background color to the same as the tab. Next, I position each :before and :after separately, sending the :before to the left, and the :after to the right. The result looks something like this.

The next step here is to cover up these new blocks with another set of :before and :after psudo elements (this time from the a) colored the same as the ul background, and use a border radius on the bottom corner to ‘reveal’ the tab color beneath it. Then we apply the same border color to the bottom and left/right of the element to blend in with our border on the list item, and the bottom of the list itself.

ul a {
  position:relative;
}

ul a:before, ul a:after {
  content:'';
  width:10px;
  height:8px;
  position:absolute;
  z-index:3;
  bottom:-1px;
  background:#959DA5;
  overflow:hidden;
  border-bottom:1px solid #333;
  -webkit-background-clip: padding-box;

}

ul a:before {
  left:-11px;
  border-bottom-right-radius:8px;
  -webkit-border-bottom-right-radius:8px;
  -moz-border-radius-bottomright:8px;
  border-right:1px solid #222;
}

ul a:after {
  right:-11px;
  border-bottom-left-radius:8px;
  -webkit-border-bottom-left-radius:8px;
  -moz-border-radius-bottomleft:8px;
  border-left:1px solid #222;
}

ul li.current a:before, ul li.current a:after {
  bottom:0;
}

And that’s all there is to it. The finished product.

And the great part about this, is it falls back gracefully in any browser that doesn’t support border-radius, without have to do any form of detection or JS sniffing. Simple and easy.

Try it for yourself. Here’s the final demo for you to explore.

Welcome Matt Graham

2011-05-02T18:37:48-04:00

I’m excited to announce the fifth member of Ordered List, designer Matt Graham. Matt brings a world of talent in graphic design and user interface, and is a welcome addition to the design side of the company.

Personally, I’m looking forward to working with another designer day-in and day-out, and to be able to see ideas visually through someone else’s creativity. Since the beginning of Ordered List, I’ve been the sole designer. And while that means I get to exercise some creative control, it will be a welcome relief to have another eye to help guide our work.

Matt will be a great asset to both our products and our clients. We’re looking forward to seeing what new thoughts and ideas he brings to the table. So join me in welcoming Matt to the team!

Gaug.es

2011-03-01T17:32:10-05:00

Today we launched our latest product, Gaug.es. Gaug.es is a hosted application that tracks your web traffic in real-time and displays it in a simple, gorgeous interface.

Gaug.es focuses on the information that matters most: who is visiting your site, where are they coming from, and what are they looking at. These are the aspects that we think are most important, and they get lost in other analytics tools.

All of the data that Gaug.es collects is available in real time. When you view your reports, the data is accurate to the second.

With Gau.ges, you don’t have to deal with installing it, updating software because of security patches, or worrying about shared hosting slowing down your site. Everything is hosted for you, and all of your sites can be tracked in one place.

First commit to launch in 38 days

Our entire team has been excited about this project. The first code for the project was written on January 22. In 38 days of evenings and weekends, on top of our existing client work load, we designed, built, and launched Gaug.es.

We intentionally gave ourselves constraints on both the code and design. These constraints kept us focused on shipping a product with value, instead of dreaming up features.

While we have a lot more to say about the building of Gaug.es, we will keep this post short and sweet. Head on over to Gaug.es and give it a try!

Design, Focus, and Constraints

2011-02-21T10:45:35-05:00

We’ve been busy lately at Ordered List. The past 4 weeks have seen the start, and near first-draft completion of our newest application, Gauges. It was a unique design challenge that really got me thinking about designing for usage, not just the content.

We’ve always wanted to build a stats application, but it was always one of those ‘eventually someday’ ideas. Recently John had reason to start on a prototype, and was rewarded by giving himself some pretty tight constraints.

And that got me thinking: What constraints can I put on the design to create a more focused interface, so it’s faster and easier to use?

Gauges needed to provide basic overview data as quickly as possible. The first problem is that with stats information, there’s temptation to show lots of data, because it’s there, it’s interesting, and graphs can be really cool. But showing lots of data makes things difficult to scan and absorb quickly.

So I decided to purposely limit the amount of space for content. I fixed the width at 670 pixels. And that constraint kept me thinking about just what information was absolutely necessary, what could be pushed off to other areas, and what could be dropped entirely.

It’s been an invaluable, if not sometimes frustrating, restriction. And I couldn’t be happier with the results. It’s allowed me to think more clearly about priority, space, and contrast within my design. I have to focus more attention on details, because when everything is contained in a smaller space, every pixel counts.

2011 Redesign

2011-01-03T23:07:06-05:00

A new year, a new design. Interestingly enough, this redesign wasn’t because I got tired of the last one. It was because, with the addition of Hoyt and Brandon, I wanted to refocus the priorities of the site.

Focus on Products

Since the last redesign, we’ve launched Harmony and started Speaker Deck. We wanted to give those the attention they deserve. We’re proud of our work on these applications, and wanted to show them off more than just a small link or a blog post or two.

Emphasize Development

With our recent hires, I’m finally ready to admit that Ordered List, which started as a design and front-end studio in 2007, is now a full-service development and production shop. So I felt it was necessary to put more focus on our team’s extraordinary development skills.

A Fresh Start

Lastly, I felt with all the change that was happening in the company, that I wanted to rethink and refine our message. I’m really happy with the results, and I hope you enjoy the redesign.

Four

2011-01-03T15:12:24-05:00

The end of 2010 brings me to think about what Ordered List has been, and what it’s becoming. It’s been nearly four years since I started out on my own. And this milestone aligns with another, the arrival of our fourth team member.

One

When I started Ordered List as my full time business back in January of 2007, I really had no idea of what I wanted the company to be in the long term. I knew that I loved designing and building web sites and applications. I knew that I wanted to make a go of it on my own. And when it came to growing, I knew that I never wanted to grow just because there was work. I’d rather turn down work than grow and shrink with demand. But I also knew that if I found the right people, I’d find the work to pay for them. And that started with John.

Two

It was in the middle of my second year of business that I found out that John Nunemaker was planning to leave Notre Dame, and was interested in joining me at Ordered List. I jumped at the chance to work with, without hesitation, one of the best programmers I have ever known. What he may lack in programming depth, he more than makes up for in thoughtfulness, usability, and simplistic creativity. And today, I value John even more for his honesty, his passion, and his dedication to building amazing things.

Three

The third year of Ordered List saw us burrow down, and build the foundation of Harmony, our first major product. Working on client work in bursts helped us pay the bills, sometimes just in time, while we bootstrapped our own product. Along with the reduction in incoming funds came a quiet spell on our blog. It was tough to find the time to write when every available ounce of creativity was spent perfecting our product. Some months were exhilarating, others testing. But we pushed through, and the beginning of our fourth year saw us bring Harmony to the surface.

Four

2010 has been our best year by far. John and I have had the privilege of working with some amazing clients on projects that have stretched us to learn things well beyond our previous skill set. It also saw Harmony launch in beta, then publicly. The response has been amazing, and we’re so excited to continue building the best CMS we’ve ever used.

With our successes John and I discussed growing, but wanted to stick to the vision of ‘the right people at the right time.’ And fortunately for us, the end of 2010 brought us two amazing people.

Jonathan Hoyt joined us in mid December. Hoyt’s development experience is young, but his technical skill is broad, and his vision and enthusiasm have challenged both John and I to step up our game. And starting the beginning of January, Brandon Keepers will bring his wealth of programming experience to help us serve clients, and build Harmony in ways we couldn’t have otherwise. Brandon’s depth of knowledge is perfectly balanced with his vision for simplicity, a skill I value more than any other.

And Five?

To put it simply, I couldn’t be any more exited about 2011. Excited about what we’ll help our clients accomplish, about what we can communicate better on our blog, about how we can grow Harmony, and about launching our next product, Speaker Deck.

But more importantly, I’m thrilled to be surrounded by such talented, enthusiastic, and genuinely awesome people in John, Hoyt, and Brandon. I’m so proud of what we’ve built, and what we can do with this team.

Here’s to a great 2011!

Welcome Brandon Keepers

2011-01-03T11:47:09-05:00

We’re growing again, and thrilled to announce that Brandon is officially the fourth member of the Ordered List team.

We’ve been working with Brandon for years, while he worked at Collective Idea, on various client and side projects. When we learned he was leaving, we jumped at the chance to work with him full time. And to our excitement, he accepted and starts on January 3rd, 2011.

Brandon has some serious Ruby and JavaScript chops, and will be helping us better serve our clients, build out new Harmony features, and push our open source software forward. He also has a keen eye for design, and a firm attention to detail. We couldn’t be more excited to have Brandon join the team. It’s going to be a great 2011!

Welcome Jon Hoyt

2011-01-03T11:47:09-05:00

It is our pleasure to introduce Jon Hoyt as the third member of Ordered List. As often as he works out of our office, some may have thought he was already working with us.

Jon was formerly a partner in a successful IT consultancy, but lately has felt his passions swing towards the software side of things. He started building applications for clients and, most recently, has been helping us get Speaker Deck off the ground.

Steve and I decided from the beginning that we did not want to hire simply because of work load. Instead, when opportunities arise to work with people we want to work with, we will find the work for them. Jon is the first instance of this. He expressed interest in doing something new and we were more than happy to figure out how to make it happen.

In fact, we get along with Jon so well that sometimes we dress like twins. Please take note of the juxtaposition of Jon’s hair and my beard in the picture below as well.

Improving Harmony Support

One of the most exciting aspects of adding Jon is his background in customer service. From the beginning we were really impressed with his patience and timeliness as he supported the customers at his previous job.

While Steve and I love helping our customers, occasionally we let things slip through the cracks. Part of Jon’s new role is being a first responder for Harmony ensuring this does not happen. This means Harmony support will be even better than it is now. Great news!

Please join us in welcoming Jon aboard.

The Work Is Never Done

2011-01-03T11:47:09-05:00

Have idea. Build application. Launch application. Profit. Those are the steps, right? Maybe we could throw another step in, like Add New Feature. Yep, that is it.

If you have a great idea, execute it in some fashion, and add new features people will start using your application and paying you for it. They will flock in droves and you will retire to an island.

Naively, I thought something pretty similar to this up until a few weeks ago. I mean, sure, if you asked me, I would say that I thought it would take Harmony a year or two to really take off, but deep down, I crazily thought it would explode instantly.

The Missing Piece of the Formula

Why would I expect any different? 37signals became an overnight success, right? Oh, and there is GitHub. Man did they explode! The list goes on. The thing is, neither of these companies were actually an overnight success. They were both a year or years in the making. Oh, and there is another item they share — communication.

The tricky thing is that communication is hard work. You have to communicate with your customers through support requests. You attempt to communicate with new customers who you think would benefit from your application. Why do so many marriages end in divorce? Because communication is not always easy.

Communicating in Different Ways

Successful businesses do not just build great products. They also tell you about those products. They iterate not only the product, but the ways in which they get that product in front of your eyes.

I have always been impressed with 37signals rise to fame (how can you not be?), but never more than in the past few weeks as I began to realize all the ways they share their products with you. From design decisions to technical challenges, they continually blog about not just what their applications are or what they do, but why and how they built them. They collect all those thoughts and share them in a book or workshop.

Shared Excitement

The work is never done. It takes a lot to build, launch, and support a product. I am not sure how, but if you stop iterating, if you stop talking about your product, the customers will sense it. Subconsciously, they see that you are tired and not as excited about the product as you once were, so why should they be. Why should they sign up? Why should they continue to pay you?

Here is the great thing though, the flip side is also true. The more excited you get about your product, the more you spend an hour here and there tweaking things, and the more you talk about it, the more excited customers and potential customers will get. The more they will take the time to sign up and try it out, which is all we really ask for. Just give it a try, right?

Applicability

Realizing this, Steve and I have been hard at work — a lunch break here, an evening there, and occasionally pulling out the laptop while watching football on Saturday (and Sunday). We have started stealing wasted hours to do the little things that we know will get people excited about Harmony.

A Month Ago

We started about a month ago, by releasing custom image sizes. This took time from both of us, but was all completed over the course of a few evenings.

We followed that up with theme preview caching, which decreased load time for the administration area. This was surprisingly easy and I completed it on a Friday evening with the TV on in the background.

A Week Ago

Last week, I took some time out of my Sunday to explain how important context and navigation is for your application. I have no problem admitting that the goal of this post was two fold. First, to share an important point. Second, to peak more people’s interest in Harmony, hopefully to the point that they would try it out. It worked. Signups were up for a few days following the post.

Earlier this week, Steve added line numbers and syntax highlighting to our already sweet theme editing area. This was a big win for our customers and ended up not taking more than a couple hours.

Yesterday

Yesterday, we stayed at the office a bit longer than usual and worked on tweaks to the Harmony website. The first thing we did is split the navigation a bit. The left side focuses mostly on new customers (features, pricing, sign up), whereas, the right side focuses mostly on existing customers (documentation, support, sign in).

The second adjustment was geared toward making sign up as simple as possible. We only require email, name and password to sign up and try Harmony. Prompted by an article, we removed the rather large sign up buttons we had and replaced them with the actual sign up form on the home and pricing pages.

We also added tracking to each of the forms so that we can figure out which one people are actually using to sign up. In a few weeks or a more, we will know if having the sign up form on the home page helps us or if the real estate would be better spent on something else. Personally, I think it is going to be worth it.

The third tweak was to emphasize communication. Previously, the blog was in the middle of the navigation, but now it is number two. Also, we are now showing recent posts on the home page. We are working hard on additions to Harmony and have been very conscious to update the blog as we go. What we did not do, was emphasize these updates on the website. Now they are.

Only one of these modifications took more than a few hours (image sizes). The majority were TV or internet time converted into something productive towards a product we really care about. Although it is true that the work is never done, I think you would be surprised with what is possible by squeezing a few hours here and there.

I write this post not to toot our horn (though I am stoked), but to encourage you to stop using lack of time as an excuse. Get inspired, execute, and communicate and see what you can build.

Oh…and sign up for Harmony if you have not yet.

Conference Badge Design

2011-01-03T11:47:09-05:00

This week Steve and I attended MongoChicago, a one day conference dedicated to MongoDB. If you are not familiar with MongoDB, it is an open source, document database and it powers Harmony. One of the things that impressed me most was the layout/design of the conference badges.

Complimenting the badge design might seem odd, considering it was a database conference, but the badges were obviously well thought out. Badge design is something that has bothered me for a few years now. My main issues are the conference name is always huge and the name of the person is always tiny.

Everyone knows what conference they are at. There is no need for the name/logo to be epic in size. If nothing else, this is stereotypical “make my logo” bigger moments that need to stop. On the flip side, names are always very small. I believe, in part, that this is because some people have large names.

The problem with making the name small is that the attendees do not all know each other. There are times when you think you recognize someone, but you are not sure. If you saw their name, even their first name, you would know and bounce right over to say hi. Instead, you have doubts and linger in a corner by yourself (maybe not quite this bad).

Instead, the folks at 10Gen, organizers of the conference, made the MongoDB logo small. Even better, they made your first name huge. This made it really easy to spot peoples names from a far. Check out a quick picture I snapped with my iPhone.

Little details like this often go unnoticed, so I wanted to be sure to bring it up. Way to go 10Gen. Hopefully more conference organizers will take this cue and run with it.

Context and Navigation

2011-01-03T11:47:09-05:00

In the beginning, we were outspoken about why we were building Harmony. I feel like our opinions driving Harmony design decisions are getting stronger, but we are sharing less. This stops now.

Navigation

Whether you are talking about navigating a website or an administration area, navigation is really important. One of the first decisions we made was that the Harmony administration area would be navigated in the same fashion as the front side of your website.

To set the stage of this point, lets look at the navigation of a few other CMS’s administration areas.

Wordpress

Mephisto

Obviously, there are a ton of CMS’s out there and I didn’t feel like taking screenshots all afternoon, so I just picked two that were well known and represented the point I want to make.

The point is that almost every major CMS out there separates content by type — posts, pages, articles, sections, events, etc. This always really bothered us.

Do we separate content by type on the front side of websites? When you visit a website, do you first think, I would like to view a page. No! You think, I want to learn more about this site, so I am going to click on the about page. Why should the administration area be different?

My guess is because developers think like developers. All the pages are stored in the pages table. All the events are stored in the events table. In a developers mind, the content is organized by type when stored, so lets organize it by type when presented. Wrong.

Harmony

In Harmony, the navigation you see is the same as what you see on the front side of the site. There is no separation of content into types, such as pages, blogs, sections, etc.

We feel this is much easier for the people managing the site. Instead of having to think first about the type of content you are creating or changing and then actually finding it, you just have to click through your site as it is organized for everyone else that visits your site, which one would assume is the optimal way.

Context

Along with mirroring administration and front side navigation, we also put a lot of thought into context. When we say context, what we mean is what is presented to you when you are trying to do a given task.

The first context we support is global. No matter where you are in Harmony, there is a thin, dark bar at the top with global actions.

From this bar, you can switch to any other site you have access to, get help from support or documentation, view your profile/account, or log out. These are all global actions across all of Harmony and are not specific to a given site.

The second context is on a per site basis. This is the sidebar that is used to navigate all of the details related to a site — content, assets, settings, etc. Below is a screenshot of the context you get first when viewing an individual site in Harmony.

From here, lets say you select ‘Manage Content’. Instantly, Harmony slides into the next content, which is the site’s primary navigation. No full page refresh, just a quick, simple context switch.

Notice that we no longer show navigation to change your settings or update your theme. When you choose to manage content, we show you only things related to that — your content. The assumption is that when you are working on your theme, that is all you want to do and when you are working on your content, that is all you want to do.

Next time you are working on a project, either personal or for a client, think long and hard about navigation and context. More than anything else, they can dictate the ease or difficulty of using your application.