Protected: Use MotionMedia Email

This content is password protected. To view it please enter your password below:

Advertisements

How to Evaluate Design Ideas

http://www.designorate.com/how-to-evaluate-design-ideas/

 

Design and innovation play an essential role in today’s business success through fueling an organization’s future with creative ideas that in turn, will help maintain superiority in market competition. Investing in business ventures and start-up ideas are other reason for companies to focus on creative ideas and analyze their potential success in the market.

Designers, design managers and educators also need an evaluation process when selecting creative ideas or different design layouts for creative projects. In order to achieve the best output of the selection process, an evaluation methodology should be considered to make sure that the selected creative or design idea is the best choice to achieve the company’s target.

Unlike evaluative business plans or marketing research which deal with statistics, numbers and/or charts, reviewing creative ideas is more complicated as it focuses on the potential success of initial starting ideas. The evaluation methods helps in reviewing a large number of ideas in order to reach the one that is most likely to succeed in the market.

The evaluation method ensures putting the right team in the selection process and understands the problems potentially inherent in a creative idea and seeks to correct them during the implementation process.

Design Evaluation Methods

Mainly, there are three methods that help in evaluating design ideas; pass-fail evaluation, evaluation matrix and SWOT analysis. These methods can be implemented individually or in a sequence-based number of steps on the number of creative ideas and the type of the evaluation required.

Pass-fail evaluation method

This is the first method and can be applied for evaluating large number of ideas based in a simple acceptance or rejection question. Before going into in-depth evaluation methods, this basic step allows eliminating the ideas that do not fit with the basic project requirements such as the budget and target audiences. This method allows reviewing large number of ideas in a short time due to its simple decision-making process based on prime criteria. The criteria can include questions such as:

  • Does the idea comply with company strategy? (Yes/No)
  • Does it talk the company target audience? (Yes/No)
  • Does the idea budget acceptable? (Yes/No)

Although there can be a large number of ideas reviewed in this method, accurate evaluations should be taken into consideration as a priority in order to avoid eliminating good ideas with potential success possibility.

Evaluation Matrix

The ideas that pass through the first method go through the evaluation matrix method. In some cases, the submitted ideas for acceptance are just a few ideas, then when submitted to the evaluation process, the reviewers can skip the first methods and transition directly to this step.

evaluation matrix
Example of the evolution matrix score.

In this method, the reviewers compare the ideas with a specific matrix or set of criteria. The criteria can includes the following:

  • The idea contribution in company’s overall strategic outcome
  • The idea’s potential impact
  • Expected stakeholders
  • Expected budget to apply the idea
  • Timelines to implement the idea

A specified score is given to each criterion. For example the idea contribution in company’s strategic outcome can include the following score set:

  • Score 0: No expected contribution in the strategic outcome
  • Score 1: Direct contribution in one strategic outcomes
  • Score 2: Direct contribution in two strategic outcomes
  • Score 3: Direct contribution in three strategic outcomes
  • Score 4: Direct contribution in four or more strategic outcomes
  • Score 5: Multiple contribution in the organization’s wide strategic outcomes

The comparison factors reflect the project requirement using a score rate. This score measures the potential success of the idea based on a number of factors. After the evaluation process is accomplished, a total score number is assigned to each idea. Each evaluator provides feedback about the idea, which can also be used to improve it.

SWOT analysis

The SWOT analysis refers to the strengths, weaknesses, opportunities and threats of the idea as projected into the marketplace. This type of evaluation seeks to extend the reviewer vision to evaluate the idea based on the four factors, which predicts the potential success of the idea in the market based on the market related factors.

SWOT evaluation
The SWOT evaluation method four factors.

This analysis stage helps evaluating the idea based on the four SWOT factors such as questions to analyze idea’s strengths:

  • What are the idea’s advantages?
  • What can the idea be successful in?
  • What are the current existing idea resources?
  • How others may see the strength of the idea?

Questions to analyze the idea’s weaknesses:

  • How can the idea can be improved?
  • What does the idea lack in term of experience, team and resources?
  • What can prevent the idea from success?
  • How do others see the idea in terms of weaknesses?

Questions to analyze the idea’s opportunities:

  • What opportunities does the idea have in the market?
  • How the company can help the idea to succeed?

Questions to analyze the idea’s threats:

  • What are the obstacles that face the idea?
  • Do the idea weaknesses represent any thread to its success?
  • What are the financial problem that may face the idea?

Approval and Implementation

Once the ideas go through the above three methods, it becomes ready to be taken to the next stage and implemented in the development process. This stage starts with creating the wireframe for the product or the design in order to have visual shape for it. Once the wireframe is reviewed and approved by different reviewers, the idea can be put into a full production development process.

The above evaluation methods help review and select the design ideas that are most suitable for market competency in order to achieve the company goals. These evaluation methods can be used all together or in sequence starting from the first method until the third one or individually based on the company’s objectives and/or requirements.

Related articles:

Best Practices for Idea Evaluation

https://www.kindlingapp.com/best-practices/best-practices-for-idea-evaluation/

Best Practices for Idea Evaluation

A competitive advantage comes with focusing on projects that your business can execute on and deliver the most impact with. In this guide, we show you how to develop and apply idea evaluation best practices to move the best ideas forward and keep people in the loop.

You’ve launched your Kindling program and are now getting amazing Ideas from previously untapped sources throughout the organization—maybe you’ve even begun to use Kindling as a better way to engage strategic customers and partners. Congratulations! Now you’re faced with a new challenge and are asking yourself, How can I manage all of these Ideas? You might even be thinking:

  • The volume of Ideas is overwhelming;
  • What evaluation criteria should I use?
  • How can I evaluate duplicate or under-developed Ideas? and
  • How will I say “no” to some Ideas?

You promoted change, you’ve expressed your desire to listen to your teams to find new areas of improvement, but now you actually have to do something with all these Ideas. Your community is waiting for feedback, waiting for you to make decisions, and, most importantly, waiting for recognition. But where do you begin? How do you make some sense from the insights you’ve received, sort through all the feedback, and begin evaluating?

The good news is you’re not alone. Many organizations struggle with this same challenge, which is why we’ve developed this guide compiling approaches our customers have taken to help their teams tackle the challenge of managing all the Ideas in their innovation programs. Your goal should be to thoughtfully evaluate all Ideas while spending as little time and resources necessary in identifying the Ideas with the best potential. It is then those Ideas, those filled with the most potential to solve the problem at hand, that justify increased attention.

Determining Evaluation Criteria

Consider the evaluation criteria before you begin evaluating Ideas to determine which Ideas show the most promise and which Ideas can be easily put to the side. By investing upfront in identifying these criteria, the evaluation process will be much simpler and more efficient. Think of the Ideas in your Category or Campaign as your innovation pipeline and evaluation criteria as the funnel you put them through to filter.

You may also use different evaluation criteria at different points in an Idea’s life cycle. For instance, your first round of Idea evaluation may rely solely on popularity while your second or third may require you to take a closer look at the timeline or budget for implementation.

Typical questions evaluation criteria might address include:

  • Does the innovation community support this Idea?
  • Did it receive a lot of interest through active conversation, voting, or volunteering?
  • Is this Idea in line with our strategic goals for this year?
  • Is it in line with the goals of this Category or Campaign?
  • Do we have the budget to implement it?
  • Do we have the necessary tools or team to implement it?
  • Can it be implemented within the desired timeframe?
  • Is the executive committee on board with moving forward with it?
Your evaluation criteria will help you determine which Ideas are worth your investment of time and resources, and which are not a good fit and can thus be declined.

There are two aspects to the strategy for evaluating Ideas: your evaluation workflow and your evaluation timeline. Evaluation workflow encompasses the stages your Idea will pass through on the way to a decision being made. This evaluation workflow maps to the evaluation criteria you’ll consider at each stage in the evaluation process. Your evaluation timeline is the pace at which you’ll move Ideas from one stage to the next. Ideally, you’ve determined both your workflow and timeline prior to your Campaign launch, but if you haven’t, the following two exercises will help you determine a process most appropriate for your organization.

Exercise: Define Your Evaluation Workflow

To determine the appropriate workflow stages or states, start by pinpointing what needs to happen to make the Idea a good fit—ask yourself, What are my must-haves? What characteristics must this Idea have in order to move forward to the next stage? And what are my deal-breakers? Which attributes make this Idea a no-go? Go through the exercise of writing these down! These characteristics are your evaluation criteria and will help you define your Idea workflow for Kindling.

For example, if all Ideas must pass through the legal review team, Legal Compliance is an evaluation criterion and should be a state in your workflow. If all Ideas must cost less than $10,000, cost should also part of your evaluation criteria with the potential to become a workflow state such as Cost Analysis.

Examples of workflow states used by Kindling customers:

  • Cost Analysis / Budget Analysis: An analysis of implementation cost is necessary to determine whether you can more forward with this Idea.
  • Legal Compliance: An analysis by the legal team is necessary to determine whether you can more forward with this Idea.
  • Executive Review / Committee Review: Ideas that you would like to move forward with that require executive approval or approval by a review committee.
  • Innovation Team Review / Under Evaluation / Expert Assessment: This Idea shows potential and is currently being evaluated or assessed to determine whether it can move forward.
  • More Information Required / Needs Elaboration: Ideas that require more information before they can be evaluated.
  • Duplicate: Another participant has already suggested a similar Idea.
  • Mid- to Long-term / Some Day / Backlog / Parked: Ideas that should be reviewed at a later date but are currently paused.
  • Declined / Not Progressed: Ideas you want to decline that don’t make sense for your organization at this time.
  • Previously Attempted: Declined because it was previously attempted by your organization but was not successful.
  • Approved: Ideas that you plan to move forward with.
  • Prototyping: Approved Ideas that you are attempting to implement as test cases.
  • Completed: Ideas that have made it through the implementation phase.

Exercise: Map out Your Evaluation Timeline

Your evaluation timeline depends on a number of factors including the type of challenge you’re running (Category or Campaign), whether a limited number of Ideas can be approved or “win” the challenge, and whether your Moderators are empowered decision-makers. First identify whether you’ll be using a Category or Campaign to collect Ideas. For Categories, Idea submission can be ongoing with no set deadline, while in Campaigns, the timeline is fixed with Campaign start and end dates. Idea evaluation can happen at specific points, such as a week after a Campaign ends or at a quarterly committee review meeting.

Next, consider whether there are a limited amount of Ideas that can be approved. If there can be only one or two winning Ideas, then you’ll need to wait until the end of the Campaign or until a designated time before closing a Category, when all Ideas have been submitted, to make your final decision. Finally, think about who will ultimately make the decision about Ideas submitted. If Ideas must be approved by a review committee (budget, legal compliance, executive), then your evaluation timing will need to take into account the frequency and timing of committee meetings. However, if your Moderators have full decision-making power and budget approval, they may have more flexibility with timing than a committee that meets at specific intervals.

Define your criteria and strategy for evaluation prior to Campaign launch and be sure to share them with all Moderators.
Share your evaluation criteria with innovators, too, in a Kindling Post about your Campaign. This will provide added context to your Category or Campaign and help to make sure that you get the most relevant Ideas in response.

Managing the Volume of Ideas

It’s important to remember that the purpose of evaluating Ideas is not to simply reduce the volume, but to try and identify, as soon as possible, and with minimal resources or distractions, which Ideas warrant further consideration.

An effective process that we have seen from many of our customers is to evaluate your Ideas in rounds or stages. Begin with an easy to apply filter that will help you determine which Ideas to respond to first. For example, you might use built-in metrics like votes, views, comments, or time of last activity to determine which Ideas are in most need of response, which ones are potential winners, and which can easily be taken out of the mix. Ideas that have broad support from your participants through votes or volunteering show promise for implementation and are good candidates to move to more comprehensive stages of evaluation, while Ideas that linger and draw minimal engagement may be prime for declining or deferring for future consideration. Using Kindling’s Moderate features, you can select and make decisions on multiple ideas at once. Then, after you’ve reduced the volume of Ideas, you can spend more time on an in-depth evaluation for those remaining Ideas.

Another approach to handling the volume of Ideas is by scheduled Moderator check-ins. These meetings can be a great way to spread the responsibility of managing a high volume of Ideas. Moderators can collaborate with each other, evaluate Ideas as a team, and discuss any challenges or questions they have about evaluation criteria. Designating a specific time for your Moderators to evaluate Ideas increases the likelihood that it will be accomplished and, by working together, your Moderators can move through Ideas more quickly and ensure a consensus about which Ideas make it to the next stage.

A third approach is to engage other Kindling participants in your decision making, drawing on the wisdom of the crowds to help reduce the volume of Ideas. With Kindling Evaluations, you can crowdsource the validation process allowing you to rapidly identify the best Ideas. Imagine you’re a Moderator in the Private Wealth division of your Finance organization, and you have 8 popular candidate Ideas to consider. So you quickly build an Evaluation and send it to your best 10 engineers to see which Ideas could be built the fastest. Then you go to lunch, and when you come back, 6 of them have replied and now you know the 3 easiest Ideas to build. So you put the other 5 Ideas aside and ask your top 4 business managers which of the 3 remaining Ideas will have the biggest impact for your clients. And before you go into a late afternoon meeting, you have your answer. Relying on other Kindling participants for Idea evaluation means moving more quickly through the evaluation process and ending up with better, more informed decisions.

Avoiding Under-developed Ideas

The best way to pre-empt incomplete or under-developed Ideas is to be as specific as possible about what you’re looking for when starting a Category or launching a Campaign. Establish a strong context and use the Category or Campaign description along with a Kindling Post to state what your goals are and what factors you’ll need to evaluate Ideas. By being transparent about your evaluation criteria, you can help ensure that participants propose Ideas relevant to the challenge and include all of the information you’re looking for.

If you’ve already launched your Campaign and you’re finding that you keep coming up against under-developed Ideas, you can share a Post reminding participants of the evaluation criteria and expectations for Idea submission and highlight a well-developed Idea that better illustrates what information you’re looking for.

View Ideas with vague details as an opportunity to reach out to the submitter. Suggest a revision to the Idea where you outline the missing information, or use a Kindling Assessment for a structured set of questions you’d like the author to address. To engage the community, add a comment to the Idea eliciting contributions from other participants. With additional feedback from your participants, each with their unique experience and perspective, Ideas can evolve into more fully formed concepts.

Always write a Post describing a new Campaign. Use this as an opportunity to catch people’s attention enough to get them to participate, and provide enough context so that people’s submissions best meet the goal of the Campaign.

Managing Duplicate Ideas

Kindling helps cut down on duplicate Ideas by scanning for similar content and informing the user during the submission process. Even so, duplicate Ideas will occasionally make it into your program. An easy way for Moderators to address redundant discussions is to create a workflow state named Duplicate and move the most recently entered or least fully formed Idea into that state. Then, add a comment to the Idea marked as a duplicate that you will be continuing the conversation in the Idea you are keeping open, and include a link to that Idea. You might also contact the owner of the Idea that will persist asking them to work with the duplicate Idea owner to include them as a contributor and to capture their unique aspects of the concept.

Saying “No”

People are realistic and understand that not all Ideas can be approved. We hear regularly that people want their Ideas considered—they want to be listened to—but understand the constraints of the organization.

Saying “no” is a necessary and important part of the Idea evaluation process. Declining an idea is as much a decision as approving it. Close the loop on the conversation and steer clear of that void where submitters never learn if their Ideas were even considered.

An Idea can be declined for any number of reasons: it’s not feasible, for example, or it doesn’t align well with established goals, or it has already been tried without success before. Since not all Ideas will be implemented, it’s important to design a strategy for declining Ideas that cannot move forward. An Idea that is deemed to be impractical but stays in its open state indefinitely appears no different to a participant than an Idea that has never been looked at. Participants need feedback, especially when their Ideas won’t be implemented.

To respond “no,” you may choose to use the built-in Declined state, or to create custom states that provide additional detail about why an Idea is being declined. Some examples are:

  • Exceeded Budget Limit;
  • Turned Down by the Executive Committee;
  • Rejected by Client; and
  • Failed End-user Testing.

Each decline action should always be accompanied by an explanatory message, even if it just shows that the Idea was considered. Some examples are:

  • “This does not meet the budgetary limits for this Campaign but we’re open to reconsidering if you have ideas for cost reduction.”
  • “This Idea isn’t projected to meet the minimum cost-saving requirements.”
  • “We can’t purchase the software you’ve recommended at this time.”
  • “This technique was attempted several years ago, but with little result.”

Being transparent about your reasoning helps mitigate disappointment about an Idea being declined. More than having every Idea approved, most users are concerned that their Ideas are heard and given due consideration. So, don’t be afraid to say “no,” just do it transparently and thoughtfully.

Work with your Moderators to design a strategy for saying “no.” This will empower them to take action more quickly and consistently while providing ways to acknowledge the effort put in by the Idea author.

Conclusion

Every business is faced with constraints and most organizations don’t have the luxury of allocating valuable resources to projects that don’t stand a strong likelihood for success. A competitive advantage comes with focusing on projects that your business can execute on and deliver the most impact with. Through a thoughtful evaluation process, teams can eliminate wasted expenditure on Ideas that aren’t a great fit and focus on those Ideas that best meet the issues at hand. Everyone is busy, including your Moderators, so create a process that maximizes people’s time while still providing feedback to everyone who took the time to contribute an Idea to your program.

 

AngularJS Best Practices: Directory Structure

https://scotch.io/tutorials/angularjs-best-practices-directory-structure

 

We spend a lot of time writing code. In the early phases of a project, the directory structure doesn’t matter too much and many people tend to ignore best practices. In the short term, this allows the developer to code rapidly, but in the long term will affect code maintainability. AngularJS is still relatively new and developers are still figuring out what works and doesn’t. There are many great ways to structure an app and we’ll borrow some principles from existing mature frameworks but also do some things that are specific to Angular.

In this article, I will cover best practices regarding directory structures for both small and large AngularJS apps. This may be a hot button issue with some developers and while there is no “perfect” way to structure an app, I will be writing from experience and lessons learned from projects I’ve worked on.

#Standard Structure

First of all, let’s go over what not to do. Many AngularJS tutorials show an app structure that resembles the code below:


app/
----- controllers/
---------- mainController.js
---------- otherController.js
----- directives/
---------- mainDirective.js
---------- otherDirective.js
----- services/
---------- userService.js
---------- itemService.js
----- js/
---------- bootstrap.js
---------- jquery.js
----- app.js
views/
----- mainView.html
----- otherView.html
----- index.html

This is a very typical app structure that I see. On the surface, it seems to make a lot of sense and is very similar to a lot of MVC frameworks. We have a separation of concerns, controllers have their own folder, views have their own folder, external libraries have their own folder, etc.

The main problem with this directory structure is not apparent when you are working with only a handful of views and controllers. In fact, it is preferable to follow this approach when writing a tutorial for example or for smaller application. This structure makes it very easy for the reader to visualize and conceptualize the concepts you are covering.

This approach falls apart, however, when you start adding additional functionality to the app. Once you have more than 10 controllers, views and directives, you are going to have to do a lot of scrolling in your directory tree to find the required files.

For example, say you are building a blog with Angular. You decide that you would like to add the author information to the bottom of each article. Well now, you have to find the blog directive, controller, potentially the service and finally the view before you can even look at the whole picture and start making edits.

Learn Angular

Related Course

Say a few months down the line, you are adding additional features to your blog and want to rename a particular feature, again it’s a hunt throughout the directory structure to find the affected files, edit them, make sure they are all in sync, and then make the changes.

#A Better Structure and Foundation

Let’s get to best practices and what you should be doing to build scalable and maintainable AngularJS apps that your coworkers will love you for. An ideal AngularJS app structure should be modularized into very specific functions. We also want to take advantage of the wonderful AngularJS directives to further compartmentalize our apps. Take a look at a sample directory structure below:


app/
----- shared/   // acts as reusable components or partials of our site
---------- sidebar/
--------------- sidebarDirective.js
--------------- sidebarView.html
---------- article/
--------------- articleDirective.js
--------------- articleView.html
----- components/   // each component is treated as a mini Angular app
---------- home/
--------------- homeController.js
--------------- homeService.js
--------------- homeView.html
---------- blog/
--------------- blogController.js
--------------- blogService.js
--------------- blogView.html
----- app.module.js
----- app.routes.js
assets/
----- img/      // Images and icons for your app
----- css/      // All styles and style related files (SCSS or LESS files)
----- js/       // JavaScript files written for your app that are not for angular
----- libs/     // Third-party libraries such as jQuery, Moment, Underscore, etc.
index.html

This directory structure is much harder to read and understand from the get go. A newcomer to Angular may be completely turned off by this complex approach, and that is why you see tutorials and examples in Angular following the simpler directory structure found in examples earlier. Let’s dive into the directory structure above and see what’s going on here.

index.html

The index.html lives at the root of front-end structure. The index.html file will primarily handle loading in all the libraries and Angular elements.

Assets Folder

The assets folder is also pretty standard. It will contain all the assets needed for your app that are not related your AngularJS code. There are many great ways to organize this directory but they are out of scope for this article. The example above is good enough for most apps.

App Folder

This is where the meat of your AngularJS app will live. We have two subfolders in here and a couple JavaScript files at the root of the folder. The app.module.js file will handle the setup of your app, load in AngularJS dependencies and so on. The app.route.js file will handle all the routes and the route configuration. After that we have two subfolders – components and shared. Let’s dive into those next.

Components Folder

The components folder will contain the actual sections for your Angular app. These will be the static views ,directives and services for that specific section of the site (think an admin users section, gallery creation section, etc). Each page should have it’s own subfolder with it’s own controller, services, and HTML files.

Each component here will resemble a mini-MVC application by having a view, controller and potentially services file(s). If the component has multiple related views, it may be a good idea to further separate these files into ‘views’, ‘controllers’, ‘services’ subfolders.

This can be seen as the simpler folder structure shown earlier in this article, just broken down into sections. So you could essentially think of this as multiple mini Angular applications inside of your giant Angular application.

Shared Folder

The shared folder will contain the individual features that your app will have. These features will ideally be directives that you will want to reuse on multiple pages.

Features such as article posts, user comments, sliders, and others should be crafted as AngularJS Directives. Each component here should have it’s own subfolder that contains the directive JavaScript file and the template HTML file.

In some instances, a directive may have it’s own services JavaScript file, and in the case that it does it should also go into this subfolder.

This allows us to have definitive components for our site so that a slider will be a slider across the site. You would probably want to build it so that you could pass in options to extend it. For example, you could have:


<!-- user a slider directive to loop over something -->
<slider id="article-slider" ng-repeat="picture in pictures" size="large" type="square">
</slider>

Now this slider is accessible from any part of our site so we’re not reinventing the wheel. We also just have to change it in one place, the shared folder and it will update sitewide.

#Best Practices (For Huuuuge Apps)

If you are developing a really large application in AngularJS, you will want to go even further and modularize your app. Here are some additional tips on how to accomplish this.

Modularize the Header and Footer

A good practice here would be to create a Core subfolder under components, and then a subfolder for the Header and Footer and any additional components that will be shared across many pages.

Modularize the Routes

In the structure above we didn’t do this, but another good practice for very large apps is to separate the routes into separate files. For example you might add a blogRoutes.js file in the /views/blog/ subfolder and there include only the routes relevant to the blog such as /blog/:slug, /blog/:slug/edit, blog/tags:/tags, etc.

Don’t Forget to Minify

If you do decide to opt in and build your AngularJS apps in a modularized fashion, be sure to concatenate and minify your code before going into production. There are many great extensions for both Grunt and Gulp that will help with this – so don’t be afraid to split code up as much as you need.

You may not want to necessarily have just one giant .js file for your entire app, but concatenating your app into a few logical files like:

  • app.js (for app initialization, config and routing)
  • services.js (for all the services)

This will be greatly beneficial for reducing initial load times of your app.

If you need some more tips on minifying, check out our guide: Declaring AngularJS Modules For Minification

Keep the Names Consistent

This is more of a general tip, but this will save you a headache in the future, when writing components and you need multiple files for the component, try to name them in a consistent pattern. For example, blogView.html, blogServices.js, blogController.js.

#Benefits of the Modularized Approach

The example above shows a modularized approach to building AngularJS. The benefits of this approach include:

Code Maintainability

Follow the approach above will logically compartmentalize your apps and you will easily be able to locate and edit code.

Scalable

Your code will be much easier to scale. Adding new directives and pages will not add bloat to existing folders. Onboarding new developers should also be much easier once the structure is explained. Additionally, with this approach, you will be able to drop features in and out of your app with relative ease so testing new functionality or removing it should be a breeze.

Debugging

Debugging your code will be much easier with this modularized approach to app development. It will be easier to find the offending pieces of code and fix them.

Testing

Writing test scripts and testing modernized apps is a whole lot easier then non-modularized ones.

#In Conclusion

To conclude, this article covered some of the best practices in regards to structuring an AngularJS app. It is easy to ignore good practices in order to save time upfront. We all have a tendency to just want to start writing code. Sometimes this passion can hurt us in the long run when our awesome apps grow and become popular and then we’re stuck rewriting or even worse maintaining badly thought out code. I hope this article had some helpful tips.

I plan on building a barebones AngularJS application structure that should follow the best practices outlined in this article that will help you get started building Angular apps quickly and efficiently. Keep a lookout for that in the coming weeks. Stay tuned for Part 2 where we put these concepts into practice!

In the meantime, be sure to check out John Papa’s AngularJS Style Guide for additional tips on AngularJS best practices and while you’re add it give Todd Motto’s AngularJS Guide a look too.

20 useful tools for web developers

http://www.creativebloq.com/web-design/must-have-tools-developers-31411174

 

Improve your website’s performance, validate your code and more with these handy tools.

Life as a web developer may offer many rewards, but when project managers are asking you to do more and more in less and less time, it can become frustrating. So it’s always good to find tools that can make your work faster and more productive. Here we’ve gathered together some of the most useful.

ADVERTISING

Some you’ll have heard of, others you’ll already be using, but hopefully there’ll be at least one or two that can lighten your workload and brighten your day…

01. Browser Calories

Get the page weight of whatever you’re looking at

In a time when more of us are doing more of our browsing on a flaky mobile connection than ever before, as designers and developers we need to be keeping an eye on our page weights. This browser extension places an icon next to the address bar that, when clicked, lets you know the page weight of whatever your looking at, broken down by resource if you like.

02. Visual Studio Code

Visual Studio Code

A free, open source code editor from Microsoft that runs anywhere and has lots of smart features for making coding quicker and easier. Built-in Git commands, debugger and much more.

03. Firebug

Firefox add-on Firebug is a must-have for devs

From the developers at Firefox, the amazingly useful add-on Firebug enables you to debug, edit and monitor HTML, JavaScript and CSS live, all in the browser. One of the very best web development tools out there, this is a must-have for anyone working in web development.

04. HTML Entity Character Lookup

HTML Entity Character Lookup

HTML Entity Character Lookup helps you ensure all the characters on your page are validated

Using HTML entities is essential to ensure all the characters on your page are validated. However, often finding the right entity code requires scanning through 250 rows of characters. It’s also available as a widget on the Mac Dashboard.

05. -prefix-free

Prefix free

-prefix-free helps you break free from CSS prefix hell

This cool tool from Lea Verou lets you use unprefixed CSS properties. It essentially works behind the scenes, adding the current browser’s prefix to any CSS code, only when it’s needed.

06. Cloud9 IDE

Cloud9 IDE

Cloud9 IDE enables developers around the world to edit the same code and chat together

Cloud9 IDE is a tool to help you collaborate with others on big-scale code projects. Letting developers around the world edit the same code and chat together in realtime, it’s fast emerging as one of the best browser-based IDEs. Features include code completion and editor, drop-document trees, smart drag and FTP integration.

07. Foundation

Foundation3

Foundation 6 makes it “crazy fast” to code responsive designs, say its makers ZURB

Made by develpopers for developers at ZURB, this prototyping tool acts as a blueprint for your responsive design projects. Its latest version is an easy grid-structure that makes styling even more convenient and flexible. It works with both SASS and CSS.

08. Fontello

Fontello

Fontello offers an easy way to generate icons in web font form

This icon generator is truly one of a kind. Pick the icons you want and Fontello will compile them into customized web fonts. You can also edit and customize the symbol codes and names.

09. Cloud Comp

Cloud Comp

Share sites and apps with ease using Cloud Comp

This lightweight and easy to use tool helps you share website and apps with others. It’s been specifically built to give designers and developers a way to present comps to their clients inside of a realistic device shell.

10. BLOKK

BLOKK

BLOKK replaces dummy text with blocks

BLOKK is a fun-to-use font for “clients who do not understand Latin”. In other words, it replaces all text with blocks to suggest generic text instead. That way you can create good looking mock-ups and wireframes without confusing people with Lorem Ipsem.

11. Basecamp

Basecamp

Basecamp is the project management of choice for much of the web design industry

Developed by 37signals, Basecamp is a popular online tool to help you manage collaboration and project management with ease. It all runs in the cloud and most people working in web design and development will be familiar with it.

12. Browser Shots

Browser Shots

Browser Shots takes screenshots of your sites in different browsers

Browser Shots generates screenshots of how websites appear at 800×600 and 1024×768 resolution in six commonly used web browsers. Just submit the web address and a group of distributed computers will access and open it, then upload screenshots of the site for you to check out.

13. FavIcon Generator

FavIcon Generator

FavIcon Generator

A favicon (‘favorites icon’) is a small, 16×16 image that’s shown inside the browser’s location bar and bookmark menu when your site is called up. This tool makes it easy to create them for your site.

14. Web-developer toolbar

Web developer toolbar

The Web Developer extension adds a range of handy tools to the browser

This Firefox plug-in feature provides a number of useful tools that web developers use on a day-to-day basis. It’s particularly useful when inspecting your HTTP header information or when you need to validate your XHTML.

15. Load Impact

Load Impact

Load Impact simulates large amounts of traffic to test your site’s performance

A successful website is one that loads faster and quickly. Load Impact is a cloud-based service for load testing and website optimization that generates traffic load by simulating users. In other words it lets you test how your website, web app, mobile app or API will perform with up to 1.2 million concurrent users.

16. Lorem Ipsum Generator

Lorem Ipsum Generator

Lorem Ipsum Generator does exactly what you’d expect

If you’re not impressed with BLOKK (see 10) and want to stick with Lorem Ipsum, this reference site about the subject, giving information on its origins, also includes a random Lorem Ipsum generator.

17. W3c Markup Validation Service

W3c Markup Validation Service

W3c Markup Validation Service checks your documents for conformance to the relevant specification

Validating web documents is an important step that can dramatically help improving and ensuring their quality. This free service from the W3C helps you to check the markup validity of different web documents, in HTML, SMIL, XHTML and MathML and more.

18. Typetester

Typetester

Take fonts for a spin with Typetester

The Typetester is a browser tool for comparing different kinds of fonts, Choose the typeface you want to test out, along with your chosen size, tracking, colour etc, and Typetester applies it to a set piece of text so you can see what it will look like.

19. Pingdom

Pingdom

Pingdom is a great tool for monitoring your site’s performance

Pingdom is a service that tracks the uptime, downtime, and performance of websites. Upload a full page in HTML and it will mimic the loading process of the entire website, incorporating all the elements (namely JavaScript, RSS, CSS and images), thereby enabling you to check and monitor the efficiency of your site.

20. CSS Sprite Generator

CSS Sprite Generator

CSS Sprite Generator can help improve your site’s performance

By reducing the number of HTTP requests, this tool aims at increasing the loading speed of your website. Images are combined into one larger image at defined X and Y coorindates. Having assigned this generated image to relevant page elements the background-position CSS property can then be used to shift the visible area to the required component image.