652 karma · joined January 31, 2008
As for calculating the number boxes you will need to do that based on how your warehouse is gonna ship these products. This is the hardest part. Most people usually maintain the dimensions of the actual product. Based on this and how you plan to ship them you will need to figure the number of boxes. The shipping rates that you have negotiated with UPS/FedEx is usually a little lower than what the user will see, so this more often than not should cover your extra costs that you may incur.
Although calculating the number of boxes and their dimension is a little involved it gives you more accuracy. Which is better for you and your customer.
The bright spot of using Silverlight is the programming language, you can code in C# or F#. But considering that you will need to host the solution on a Windows makes it a more expensive to scale. That probably drives away a lot of startups.
You should keep looking for a co-founder irrespective of all this. You should be able to sell your idea to someone smart and intelligent until then you really don't know how good the idea is.
Their philosophy has been to create a great product and sell it in one package. And it has worked pretty good for them with Mac line of products.
With the app store model they still get to control the applications that run on the iPhone. Which does give them the ability to not approve any application that would make the user experience with the device undesirable. This control over the app store is being used for tactical reasons by Apple. But obviously whether it was intended reason from the get go, I highly doubt that. Add to this who knows what legal agreements they are bound by with the Carrier. The carrier may say it wasn't us but when things go bad between them I am pretty certain there will be a few people in both these companies looking at those legal agreements.
Whether this is a good thing for developers, no. Whether it is good for Apple, may be in short term but probably not in long term. A more open policy with the approval process would be ideal.
It isn't about whether it looks like Microsoft designed it not but what works effectively. There are a lot of companies that have created a product that doesn't look like it is enterprise oriented in the area you are working on example, http://www.pivotaltracker.com/. I personally don't think the macbook image would in anyway convince me, hacker & small company, to use your product. I am more interested in your product not somebody else's. Hope that helps.
The macbook screenshot is showing off the laptop more than your application.
On the web development side ASP.Net is really hard compared to other frameworks out there. Until ASP.Net MVC, there wasn't a quick and easy method to implement URL rewriting for example. On the ORM side they seem to be changing their mind every year they ditched Linq to SQL in favor Entity Framework which really doesn't work as seamlessly as they make it out to be. Add to this the fact the startup has to buy licenses for the server, the costs add up as you scale up. I know there is Mono but there it isn't easy to port everything to it, the implementation isn't exactly complete.
.Net has its place for example if you are writing a Windows only desktop application .Net is by far the easiest framework MS had to support it. I believe Xobini uses .Net. Again writing cross platform desktop applications doesn't look as appealing to me. Silverlight 3 is almost here but it still yet to get font rendering and printing right.
May be they are targeting companies that have already been funded.
Once the doctors realize that these current practices are not sustainable they probably will come out with some novel ideas like this one http://hbswk.hbs.edu/item/4585.html.
It doesn't really make sense to have only for profit health insurance companies, look the executive salaries (http://www.prwatch.org/node/8425#comment-4517). With the amount of money the US government is spending on healthcare it would make a lot of sense for us to have a single-payer system.