Sure. Update your resume and start pounding the pavement (make use of any contacts you might have first, then hit the usual online boards). Or strike out on your own (maybe take a few friends with you, depending on what you signed when you started) and build web apps as a contractor.
Fact remains that your best chance at a pay (and maybe responsibility) increase is to switch employers.
If you're set on staying where you are, the same kinds of things that you would do to make yourself look good on a resume (e.g., enumerate your accomplishments in terms that can be seen to relate to a company's bottom line - not necessarily in a dollars and cents-specific manner, but in way that makes clear what you built or directed and how you took responsibility) can also help you when talking to your manager.
If you're strictly looking for a raise, first do some research about prevailing pay rates (check ads; check GlassDoor) - if you're underpaid, you have an easier case (you can also try talking to friends at work - good friends, as pay tends to be something people don't talk about and management encourages not talking about it for obvious reasons). Either way, you want to present a case that has something for them, too. Saying "I think I deserve a raise" doesn't help much and creates defensiveness. Better to come to an agreement about a goal. Ramit Sethi has some great advice in How to Hack Your Day Job (short article and a couple of videos).
If you're looking for a promotion, and not so much the money, you still want to proceed along the same lines, but first consider whether the company has openings at the level you're looking at. If you want to go from, say, developer to senior developer, that's likely not a problem since the company defines what "senior developer" means, and you can help yourself by examining others at that level and trying to do what they do as well as you can within the constraints of your present position. However, moving to a lead/manager position will require an opening. For any promotion, try to take on more responsibility where you are - volunteer to write requirements documents, coordinate builds, create tools and processes that streamline or automate poor processes. Keep a log of these accomplishments, even if it's just in a text file, so you can present specific reasons when discussing advancement.
A book I'm reading now called Dinosaur Brains (Albert J. Bernstein) has some interesting observations about office politics and psychology and it may be helpful to you. Avoiding "office politics" isn't really an option, but you can participate on your own terms. Seth Godin's books—Lynchpin (on being indispensable), in particular, in your case, and perhaps The Dip—will also be helpful and help you marshal your arguments and perhaps give you a push to move forward or move on to somewhere that can better use your talents.