Software Product Development Checklist Supreme. SecretGeek with a checklist of 124 to-do’s in creating, selling and sustaining a successful software product. In this case the product is a standalone .EXE, but valuable for a web-based application as well. Most pertinent to-do’s for Sueetie’s current state of development are (more) screenshots of app, drive support costs down, update email signatures so you’re always representing product, faq, policy and privacy pages, bug tracking software, soliciting feedback and testimonials, webcasts, videos and slideshows, email campaigns and communications, product roadmap, plug-in community support, internationalization and localization of product and website.
The Pitch, the Cheat, the Sting. A Branding Gavel post on developing new business suggests we focus on a pitch we’re passionate about rather than diluting our brand by going after every RFP that comes our way. It would also be beneficial according to the author if we based our pitch on a good understanding of what our primary customer market would die for. As for “the Cheat,” we need to look to other markets to see what ideas we can repackage for our target market. The Sting is more business than we can handle—and incidentally an excellent movie that I need to pull of my DVD shelf for another viewing soon.
Gaining Hearts and Minds with your Application. More from Branding Gavel for you tonight. The post is titled How to Guarantee a Brand’s Success, but I’d like to use a web application as the topic since it’s more real to most dbvt.com readers. “Most brands suffer from despair, but [developers need to] stand firm with courage…without losing enthusiasm.” Put quantifiable objectives in place, since no [application] will succeed without a road plan. Have a deep insight in your customers’ psychological and behavioral patterns, appealing to their emotional bonding. Never bore your customers. Add fun, give hope and stir them up to reach their dreams.
ASP.NET – Google Maps API. Two technologies you don’t see together very often, but which the talented Scott Mitchell demonstrates for us. He even shares his code.
Every Site a Mobile Site. “Why would you prefer a site on a smaller screen and with less features?” In his answer, the author of this Drawar article says that mobile web apps are designed for speed of task completion rather than to maximize time on site and revenue like many websites. The author goes so far as to say that most websites are designed to annoy us and keep us there by wasting our time, while mobile versions are actually the ones we like to use because of their efficiency. The article ends by challenging us to streamline our full version sites to function more like our mobile versions.
Mobile Website Makers. Speaking of mobile websites, here are 11 site creation options from WDL. It seems most of them use RSS-feeds for creating mobile layouts. Seems a good approach to non-blog apps as well.
Free-free-free-sell. Copyblogger on How to Monetize Your Site Without Causing an Audience Revolt. Don’t worry. I’m not going to start charging for Everyman Links anytime soon. Interesting monetization considerations like the pattern of reciprocity, where content marketers give a bunch of stuff away for free and prospects feel more obliged to give back. So if monetization is in the plan, it’s important to establish a pattern so that the audience knows you’re here to sell as well as to provide valuable free content. The post concludes with an emphasis on establishing your value. “Free-free-free-sell, free-free-free-sell.” I like that. That model should also work for, oh, I don’t know, software products.