In this paper we identify the fundamental differences between web-­based and conventional software engineering. We express our views about why we think requirements engineering for web-­based application development should be easier than requirements engineering for conventional software development. We will examine the consequences of holding such a position and propose a more effective process model for web­-based application development. Given that we hold such view, we believe that we can do a better job of requirements engineering than is currently being practiced in web-­based application development. We conclude by showing why we believe this is a promising area for investing research efforts.