(631) 759 3900 info@avi.com

CEOs Guide to creating great software

You need to build a software application. Now what?
What should you do? How should you do it? What should you look out for? This guide will help you spot the most common pitfalls and avoid them. Advice you won’t find elsewhere.

Applied Visions Inc. was founded in 1987 by Frank Zinghini. Since then, we’ve grown into a family of companies, including Jybe Mobile and Software Design Solutions. We blend our substantial experience in software development with our knowledge of how to make an application that actually makes money.


User Interface and User Experience (UI/UX)

Applications shouldn’t just look spectacular, they should be intuitive and easy to use— few things can affect an application’s success or failure more. While good design isn’t always recognized, bad design always is.

Our user experience experts understand what makes an application enjoyable, productive, and hassle-free, and we make sure that the end product won’t result in a wave of complaints. We identify the users involved, what their goals are, what work they hope to do with your product. We interview them, do surveys, and study the user community. Once we have that information, we can then start to find the common denominators (because no single product can do it “all” – one has to pick the most important functions) and develop the guidance that leads to a successful application. And then you have to make sure you don’t kill your users with improvements. This is especially true when you are building applications for devices, because every decision is going to impact millions of devices.

Building an application is a customer-driven endeavor. Our philosophy is that to make a great application, you need to get real data from customers. Here are the facts we want to work with clients to learn when building software:

What you need to know about your customers before you can sell

  1. What the customer is doing now to solve the problem, and how they feel about it. If they’re ambivalent, because their current method (including “doing nothing”) is good enough, it will be harder to sell your solution.
  2. What else the customer has looked at, and how they felt about the solutions they found.
  3. What competitors have promised them, and what they believed or didn’t believe about what they were told.
  4. What they might pay for your product, and how they want to pay. Yes, you can ask about this. You need to know if they insist on up-front licensing, or would be open to a subscription model.
  5. How they prioritize the features and functions. Which of them are essential, which ones are “nice to have,” which ones are “standard” and “assumed,” and which ones are not really necessary.
  6. Which of those “must have” features are things they really use, and which ones are just “checklist” items. You’ll be surprised how often those “must have” features never get used. We separate features into two categories: “buying criteria” and “using criteria.”
  7. How they feel about these types of applications in general—in terms of larger trends. Do they still feel that this type of application is critical, or is interest in this waning? Are people finding other ways to solve the problem, or is the problem less critical than it used to be?
  8. What other applications—similar to yours—excited them, and why.
  9. The things that would make your customer say, “I have to have that,” or, “I’ll never buy that.”

If you agree that customers come first when building a piece of software, and if you don’t want to build a frustrating application, we can help. If you want a user-friendly piece of software, please contact us!