Every business owner knows a Web presence is a necessity and getting it done right is paramount (though what "right" is will vary depending on who you talk to, but that's another article). Just as important as getting it done, however, is long-term maintenance. Just like a new house built from the ground up, Web projects require maintenance to keep them running smoothly.
I was in a meeting regarding a possible and the inevitable question came up regarding how estimates work. As I've mentioned in the past, we are a custom development firm and don't perform project work on a fixed bid because application development, especially redesigning existing applications, always comes with a surprise or two - usually small, but sometimes not so small. The response I received was eye-opening: "I don't like surprises."
When you talk to an architect about building your dream home, you can get a rough idea of the cost by providing some preliminary information. It's not until they dig into specifics - the kind of countertops, number and size of bedrooms, and other important details - that they can provide you with an exact number. The same is true when creating a custom Web site or application. Estimates are often based on little more than an hour-long conversation and a few general examples.
When it comes to technology, many clients ask me about the advantages of one platform over another. Often, they're focused on one platform or they read somewhere that one platform is better than the other. I'm here to dispel some of the myths and offer some advice on how to pick the best technologies to launch your next idea.
Once an application is finished and you're using it, that's all there is to it, right? Doubtful. Technology changes quickly and some issues don't show up until after the application has been live for days, months or even years. Recently, we started troubleshooting resource alarms on a client's production application and discovered some underlying issues that didn't begin to appear until the system had over a thousand users managing hundreds of thousands of unique data elements.
Too often, I meet people who started a project with another designer or developer and have spent a lot of money and still aren't happy with the result (or haven't even seen a result). Business owners are great at what they do: running their business. If they don't have a background in Web technologies and digital marketing practices, it's hard to figure out who to listen to. So, here are three phrases that should be red flags and trigger a deeper evaluation of the individual or company you're interviewing to create your Web site.
When it comes to solving our client's business challenges with software, there's a lot that has to happen to make it a reality. The first stage is the proposal and we want our estimate to be as accurate as possible so the client can plan accordingly. To that end, when planning out a custom solution, we focus on four key items: keeping the timeline short, prioritizing features, talking about our client's problems, and talking about the end result.
I've talked about development projects and how we create customized, proprietary software for our clients. We do that by leveraging the open source software community which lets us build great software faster and with widely-used libraries that are designed to be reused and, as such, are tested quite thoroughly. Open source benefits our clients in three very important ways: better quality, shorter timelines, and lower costs.
Let's face it, when it comes to Web design and development, most business owners just know they need it. It's all a big mystery what their designers and/or developers do every day to market and build a client's brand identity online. There are often misconceptions about the benefits we provide to businesses and, as a business owner, it's important to understand them so you get the best outcome for your project.
With this article, I'll continue a series on the lexicon of app development. In this post, I'll cover something that comes up during many stages of a project, particularly Web applications. When we talk about Web sites, software, and apps, developers often reference "bugs" in the code or mention "enhancements" or "features". If you'd like to know more about the difference, you should keep reading.
I often forget that, when I'm in "developer mode", I speak a language foreign to many people. For that reason, this is will be my first article discussing concepts and/or jargon that come up frequently during or about projects. First, you may find it helpful to know that when developers talk about Web sites, Web applications, and mobile apps, we are referring to three different, albeit related, types of projects. Carry on if you'd like to find out more.
So you're a new business and you need to establish your presence online. Or perhaps you've been in business a while and your online identity could use a bit of an upgrade. But where do you start? It can be intimidating talking to someone about your Web site. It's your livelihood and outsourcing the creation and/or maintenance to someone else that may or may not understand your business is known to cause heartburn until trust is established.