No problem, and awesome. My reply is geared toward you and any other folks who finally want some insight into me, development, my approach to ideas and threads here, and some additional thoughts on this project), so tl;dr: Don't be lazy. Read on if you're interested!
Originally Posted by Remy X
Respectability will come with time, consistent effort, and passion for what you do. When I was 22, I was a couple of years into my career (think "dot-com boom"), excited about the industry and and its future, dressing like I wanted and three sheets to the wind on occasion.
I actually work in the same industry as yourself, so all of the concerns are quite familiar to me. The only difference is that you have your own team, working for big-name corporate clients while i personally keep up with the new developments but can't quite translate it into the same sort of respectability. At my age (22), i still look like a teenager (not that i dress like one) and will always be "the kid", unless i make a name for myself and have something to show.
Today, I'm 35, and yeah, I lead a growing team of really good, sane developers that I rely on to produce great stuff and keep me in check from time to time when the situation warrants it. However, I'm a little (a lot, I mean) more mature than I was then...but I'm still excited about this industry and its future, still dress like I want, and still can be found three sheets to the wind on occasion (when I don't need to worry about my year-old son for the night). I also look about 26 according to my friends, so I get those "kid" comments often enough myself.
In the meantime, experiment. A lot. Post it all online; your successes and failures. Describe your approach and hypothesis for all to see so they have some insight into how you work. It builds respect on its own; it shows effort, thought, and deliberation in execution. When I interview someone, having someone share that kind of insight before the interview even kicks off is what I look for in a prime candidate--and something I rarely ever get anymore.
But yeah, life's awesome like that if you choose the path you really have passion for, and if I had a dollar for every developer I watched wither because they became complacent or didn't look at things holistically and realistically (crushing them slowly from the inside out each time they became disappointed), well, I'd have a pretty good second savings account right now. Always keep moving, and if you lose the passion, do yourself a favor and examine your career options.
We're more alike than you think, just coming from different angles more or less.
I hope that explains my at times defensive attitude. I'm actually pretty easy-going for the most part and like working on interesting projects and concepts that actually take some thinking.
Here's a secret: If I lay down a good hard look at reality in a thread, and you look at the idea from all points of view and still decide the idea is a good one, then there's no harm in pursuing it, right? In order to push the limit, know the limit by looking at it realistically. It'll serve you well.
You'll notice that Rod, when he pops up, often deflates expectations that aren't grounded in reality--even those that come from the most ardent and vocal webOS devotees. That's the kind of guy I really dig around here; keep pushing forward, but with expectations in complete check. Even more respect because everyone's looking to him for answers; he could easily work everyone up into a lather without lifting a finger, but he doesn't. Archetypical no-bull**** man, he is.
Many veterans are realists because they know what happens when unsubstantiated ideas and fantasy goes unchecked, and the long-term damage that can do to colleagues--or a community like this one--can be devastating. Long-term disappointment is never worth the cost that unchecked short-term excitement brings with it. Realists lay down the facts precisely because they care despite being considered negative or pessimistic. Even if sometimes it comes across as bluntly (or tactfully) as a sledgehammer in a china shop, often to the disappointment of people that didn't want to accept the reality of the situation in the first place. (Those that face reality and are patient enough to see things through are the ones that generally stick it out for the long haul.)
Good first pass. Keep thinking it over and poke holes in it until you don't have any left. Always be your own devil's advocate and don't cut yourself any slack. Kill your darlings, and invite others to come after them with guns blazing also. It goes for ideas as well as your code. And never be offended when someone constructively tears your idea apart.
The question of piracy is not a new one, so that and content monitoring will definitely have to be taken care of before the system becomes open to the public. Of all apps, the ones already in the HP Catalog would be the first in line for approval, and i'm thinking that as time goes on, we can put together an automatic submission system that flags all of the areas that need particular attention before handing over the app to the actual, paid content monitoring crew. While the load is light, the crew can be rewarded with access to all paid apps for free, and later on a fee structure can be put in place for code review and testing priority. I think Preware will remain as the place for patches and Beta feeds, so for now, we'll mostly be dealing with more-or-less trustworthy code.
I know that it doesn't seem like I addressed what you wrote there, but I did.
Never underestimate the power of a government when there's money involved. Get advice before pursuing your train of thought. I have a personal dedicated server in Amsterdam, so not only do I have to comply with U.S. law, I have to comply with EU directives and Dutch law as a general rule if I distribute anything--which I really don't do at the moment, so I don't worry much about it. You might be on the right track, but it still pays to be absolutely certain of jurisdictional quirks and especially anything involving money.
I have always thought that international taxes and fees were a matter of jurisdiction. Considering that the hosting servers will be based in the US and the app store will only present warnings and disclaimer contracts for apps that are not allowed in the buyer's country, we don't really have to comply with local laws. The customer has to, and will be warned, but it's up to the local ISPs to block a US-based site that does business in US dollars, intended for a US-based audience. We don't advertise or have a storefront or even a web server in the other jurisdictions, so it's a matter of "don't ask, don't tell" and of verbal contract.
Stripe accepts international cards, so along with its ease of implementation and competitive transactional fees, it's a good choice for an up and coming project.
Thanks for the heads up though, and i appreciate the interest. I'll be sure to check out Stripe