We have some of our own software resources. Why should I work with Outr.Net?

Software projects are notorious for missed schedules and blown budgets. How do we avoid this for my application?

What are the common pitfalls, and the keys to success, for my application?

Is my intellectual property protected if I work with Outr.Net?

Whatís the best device? Whatís the best network?

Should I use a thin-client ("browser-like") solution for my application, or is a native application more appropriate?

Whatís your business model?

Do you sell devices or airtime?

How long does it usually take to create an application?

What middleware or messaging gateway do you use?

Outr.Net has already developed applications for other clients in a market that I'm interested in. Is there any conflict of interest if Outr.Net develops my application?

Can you provide me with a few referrals?

Answers

Question: We have some of our own software resources. Why should I work with Outr.Net?

Answer: Even if you have available internal resources with some experience in related development environments, you should engage someone on at least an advisory basis that has real-world experience in ALL of the wireless devices, networks and all other components required for your solution.

Compared to traditional development environments, the Wireless Internet is at an immature state: many parts donít work exactly as advertised. We draw heavily on a codebase of well-tested modules to help develop robust solutions for our clients quickly.

The cost of outside technical consulting is insignificant compared to the real costs of missed schedules, incorrect platform choices, or product recalls.

Question: Software projects are notorious for missed schedules and blown budgets. How do we avoid this for my application?

Answer: There are several parts to the answer. Beginning at the concept and design stages, we have continuously refined processes for early prototyping, technical risk assessment, and project scoping.

During development, our developers and project managers use online systems for project tracking and communication that have been developed specifically for Wireless Internet applications.

Of course, execution is always critical, and the culture throughout Outr.Net emphasizes the importance of quality and meeting of commitments. This is an issue that we take very seriously at Outr.Net.

Question: What are the common pitfalls, and the keys to success, for my application?

Answer: Our downloadable newsletter discusses the common pitfalls of Wireless Internet applications. We can provide a technical or business risk assessment for your particular application - please contact us at info@outr.net.

Question: Is my intellectual property protected if I work with Outr.Net?

Answer: Absolutely. We engage in a bi-lateral NDA with all of our clients, and our livelihood depends upon the protection of our clientsí intellectual property.

Question: Whatís the best device? Whatís the best network?

Answer: Thereís no single "best" device or network for all applications. It depends upon the details of your application, the profile of your market, and how the pros and cons of each device and network match your requirements. Increasingly, target end-users have already established usage patterns with cell phones, wireless PDAs or two-way pagers, so your solution may be most successful if it is deployed on more than one platform.

Question: Should I use a thin-client ("browser-like") solution for my application, or is a native application more appropriate?

Answer: This is an important and complex question that we have addressed in a downloadable presentation. To discuss this in the context of your application, please contact us at info@outr.net.

Question: Whatís your business model?

Answer: We prefer to work on a time and expenses model, because it has proven to be the least expensive for our clients. We generally provide a detailed estimate of scope early in a project, and we pride ourselves on our ability to predict work requirements. However, our projects often involve multiple phases because our clients and the end-users discover the power and the potential of the Wireless Internet after they begin to use an application, even in itís early stages.

Question: Do you sell devices or airtime?

Answer: No. We deliver applications, but we work closely with the people that provide devices and airtime, and can help match you with the ones who can best support your application.

Question: How long does it usually take to create an application?

Answer: This is varies tremendously by project, but we can typically deliver a functional prototype a few days to a few weeks, depending upon the complexity of the project.

Question: What middleware or messaging gateway do you use?

Answer: Whatever is most appropriate for your application. We are familiar with all of the popular solutions.

Question: Outr.Net has already developed applications for other clients in a market that I'm interested in. Is there any conflict of interest if Outr.Net develops my application?

Answer: Absolutely not, we maintain strict firewalls inside Outr.Net between projects. Our livelihood depends upon our protecting the confidentiality of our clients. We liken ourselves to carpenters who may build a house to a clientís specification, but that does not preclude us from building another house to another clientís specification.

Question: Can you provide me with a few referrals?

Answer: Of course, contact us at info@outr.net.