Writing a Wireless Web Service is currently harder than it should be.

See: http://java.sun.com/developer/technicalArticles/J2EE/j2ee_ws/

The above is too low-level, too complex, and frankly too boring! Instead Web Service design should start with high-level concepts with an element of fun:

1. Postulate - Take a guess what the market wants.
2. Simulate - Don't write the full functionality yet. Write a skeleton that emulates the product.
3. Demostrate - Show some potential customers and some non-potential customers and get their feedback.
4. Integrate (feedback) - Filter what comments are good and change your simulation.
5. Iterate - Go back to step 1 or step 3 and do it all over again.

A better and faster way to design a Wireless Web Services is to simulate the Web services on an actual device with a demo program. This gets you Usability information right way and gets you feedback from people right way so that you can iterate on a design quickly. It lets you know what people think is fun and what is boring about your design, which is important these days in the wireless device market.

Wireless Web Services are not used much now because engineers are making it much too difficult.

I'll walk through an example in the next postings...