Approach

  • WB-Tech develops websites in five distinct stages using a custom process for each individual client. We never use templates or automated solutions, making our approach to web development appropriate for companies who have specs that don’t fit into a pre-packaged solution or companies who need to accommodate evolving requirements in the future. Here’s a brief overview of our five-stage approach ?

    Consulting
    Our initial client interview assesses current IT needs and future plans for expansion. We begin by asking critical questions about the client’s present expectations, and then we combine those expectations with strategic goals to ensure optimal web performance and sales.
    Projecting and prototyping
    Using the information gathered from the initial interview, we create a flexible, interactive prototype — complete with user cases, scenarios and flows. Each prototype is equipped with applicable interface text and HTML.
  • Design
    After settling on an ideal prototype, we start developing attractive layouts with complementary GUI elements. We additionally make anticipated adjustments planned to accommodate different screen widths and varying UX (user experience) concepts.
    Development
    In this stage, we apply a multitude of professional tools and applications to create the frontend. WB-Tech is proficient in: CSS3, SVG, Canvas, Touch Events, jQuery, HTML5 Audio, HTML5 Video, HTML5 Geolocation API, HTML5 History API, HTML5 WebSockets and more. For backend development we; use Python (Django, Flask), Node.js, Socket. IO, Redis, PostgreSQL, MySQL, MongoDB, Memcached, Sphinx, elastic search and more.
    Support
    Since we understand and appreciate how unexpected challenges can alter requirements, even after the final stages of development, we continue the process with on-going support. This allows us to add new features and bug fixes along the way.

Workflow

We launch and release projects using the version model. We additionally use the agile approach so that both WB-Tech and our clients can follow a clear outline of incremental developments. This eliminates confusion about subsequent financial relationships, and it prevents unnecessary work resulting from mistaken revisions. It also gives us a structured approach to making concrete, databased decisions.

The entire process addresses the following:

Projecting
Here, we collect the necessary materials and research to create an effective prototype and briefing. The brief is a Google DOC or PDF file which includes the following points:
    • Project mission and goals
    • Business tasks of the site
    • Use cases
    • Structure, navigation
    • Content
    • Quotes and timing
    • Navigation
    • Page descriptions
    • Interface expressions
    • Sense emphasis, visual recommendations
    • Admin panel description
Prototype
In this stage, we develop a series of interactive prototypes to review the mechanics of user interaction with user cases. The result is a set of HTML pages.
Layouts
Results are presented as a set of INDD or PSD files.
Frontend
While developing the front end, we apply the most suitable layout and design. The result is published on the web and available in a repository branch.
Scope statement
During this part of the process, we specify the document that describes the site’s data model and technologies. We also enable Google Analytics settings (events, goals, user timing, social points, etc.). Issues addressed include:
    • Database model
    • Relevant technologies
    • The basic system logic
    • The logic behind the subsystem’s interaction
    • The logic of interaction with outstanding services
    • Other specifications
    • Query speed
    • Load on the hardware component
    • Horizontal scalability
    • Fault tolerance (including data backup, server backups, etc.)
    • Security (using traffic source encryption, etc.)
    • Architecture project (server architecture)
Backend
During the site’s backend development, we create the server side software. The result is placed onto the web, with ownership of the GitHub repository transferring to the client once everything is completed to spec and all payments are made.
Testing
Here, we search for bugs and fix them ourselves, or, we have an external debugging team fix them.
Post-production.
During the post-production stage, we create a testing and production branch as well as a user manual for the software and the project’s deployment.

Payments

We require full payment of the first stage before beginning a job. Once secured, we require a half payment for each upcoming stage and the remaining half payment for each previous stage. Additional work is billed separately at a rate of $40.00 per hour. The final amount, which is available after the entire technical task document is complete, must not be more than 30%. Any remaining portion of the budget is split among corresponding stages of development. More details about our payments and work terms are in our contract.