A new group of App developers have stepped up and announced plans to apply for the .APP new gTLD and is going about raising the money for the application in a very unusual manner.
According to the site to promote the application:
“.app Project” is a community funded and executed project to obtain rights to the .app gTLD when ICANN makes them available in 2012.”
“Our aim is to keep the .app gTLD open and accessible such that it becomes an entity that properly support the app software development community, particularly in areas of intellectual property protection.”
However the most interesting part of the plan for .APP is how the sponsor is trying to raise money for the $185K application fee:
We’re looking to raise 67% of the $185,000 ICANN evaluation fee through sales of memberships in the .app Project. This is the most important way in which individuals can help us make the .app Project a reality.
There are three membership levels. Each includes a number of domain registrations, priority service in domain allocation and the right to use special .app Project logo on electronic and printed materials forever.
Domain registrations represent at least a 75% discount over the expected cost of domains when the .app Project is up and running. Our current proposed cost for a .app domain is $25.00.
Silver Gold Platinum Fee $25 $50 $100 Number of free domains 2 4 10 Term of free domains 24 months 24 months 24 months Effective cost of domain per year $6.25 $6.25 $5.00 Discount 75% 75% 80% Priority allocation service Yes Yes Yes Rights to use special .app Project logos online and in print Yes Yes Yes Pre-registration limits (more) 2 domains in a 5 day period 4 domains in a 5 day period 10 domains in a 5 day period Links in member profile without ‘nofollow’ 1 2 4 25% off an Apress ebook (more) Yes Yes Yes Add to
However, the bad news is that ICANN’s fee is an evaluation fee, not a license fee. This means we still have to pay it even if we do not win. So it could be that we never get to a position to give you the domains that you want.
If we go ahead with the application to ICANN and we lose, we will get some of the money back. If this happens we will split what we get back with members on a pro rata basis, minus payment processing costs and any tax that we have to pay in the process of collecting your money.
Or, it could be that we do not put the application in to ICANN at all. (This will only happen if we do not believe that we will win.) If this happens, we will refund your fee to you, again minus payment processing costs and any tax.
We are using currently using PayPal as our payment provider, so in terms of payment charges their current fees are 3.9% + $0.30 per transaction. We will also reserve the right to take $1 for each membership that we do have to refund so that we can cover our own costs. (Remember, we may end up having to process refunds to 10,000 people and it may be that we have to pay someone to do this administrative work.)
Of course I see a lot of problems with this approach.
Anyone in the domain industry who has followed the new gTLD proocess will tell you that .App is going to be one of those generic TLD that has a huge probability of having multiple applicants.
IMHO The chance that one company is going to get this extension for application fee is less than 1%.
If the applicant is planning on applying for the string as a community, statements made at the ICANN meeting make this seem quite unrealistic, plus there is sure to be opposition to the application which will increase the costs even further.
Moreover the costs of meeting ICANN’s criteria and getting the application through is going to cost much more than just the application fee.
“”Or, it could be that we do not put the application in to ICANN at all. (This will only happen if we do not believe that we will win.)”
Since the applications will have to be submitted in the blind, meaning that know one will know what other applications have been submitted for a string until the application period closes, its impossible to make a judgement on success. The only way to be somewhat certain of success when going after a highly sort generic like .APP will be if you have a LOT of money in the bank, or contingent financing in case you need to win it at an auction.
The new gTLD program is challenging enough.
IMHO, taking $100 from 1,200 people or $25 from 4,800 people without full disclosure of the process will just get a lot of people pissed off at the process.
Mike Law says
It’s going to be a epic fail tld. Where are they going to get the money to promote the tld even if they get approved?
some of my domains says
a TLD for Apps is a contradiction
Apps don’t need websites, but could kill all them
also, when it will be available, may the web still exist, as we know it?
Don’t forget Apple and Microsoft are still feuding over the App Store trademark, so good like with .app as a communal app-lication! 😀
some of my domains says
a TLD for Apps is a contradiction, Apps don’t need websites, but could kill all them, also, when it will be available, may the web still exist, as we know it?
ICANN pro says
i don’t use any apps and so far don’t need them . and i don’t have iphone. so what?
ICANN pro says
somefunkyapp.com/.net would solve their “problem”
Typo in my post: “good luck with the .app”
This is yet another example of how failed the ICANN process has been with regards to gTLDs. They should raise the application fee to at least $250k.
I believe its Apple and Amazon fighting over App store
Wonder if a successful “.app” gTLD would preclude Apple Computer, Apple Records, or an apple growers association from registering “.apple”.
Love it another of my funky project B…S apps
man..getting lots of offers of malawareapp.com
“MHB” “The chance that one company is going to get this extension for application fee is less than 1%.”
I am sure your being more than generous, with the less than 1% chance you give them “MHB”…with all due respect.
Not a bad idea…if they had more than say a 80% chance to get it…IMHO
But, really with ‘below zero’ chance of getting it…
Micheal is right, It is just going have a lot of pissed off investors…wanting their money back.
This will come down to 4-8 companies, and go into auction…for the ‘exclusive rights’ to own and run the domain extension…and I would imagine it will remain that way…to whom the extension finally goes to.
I will give these guys credit, as they are really trying to fight to keep the .app “Open”…so everyone down the line would get chance to register a .app domain name.
This still could happen, if “Go Daddy” or some other very deep pockets registrar, or investment group…ends up with it…but they really do not have the ‘firepower’…if say “Apple” wants it, as is willing to pay almost anything for it.
IMHO… ‘exclusive rights’ will win day for one company.
IMHO… Sure, the winner could license out the use of a “few” specific .app domains to other company’s, for some great some of money.
But, most likely…. the winner is going to keep the extension 100% for its own use.
It will end up in auction…and going for multi-millions+ to a company like Apple or Google, Amazon, Microsoft or maybe to any number of ‘deep pocket’ telco companies…out there, that may want to jump in.
BTW: If they are coming out with .APP are they also coming out with .APPS?
“”will give these guys credit, as they are really trying to fight to keep the .app “Open”…so everyone down the line would get chance to register a .app domain name.”
Well yes if you pay them now.
Most generic extensions are going to be open, that is most of the domains will be available.
I don’t expect that many of these generic to be closed for the use of only one company
” I believe its Apple and Amazon fighting over App store”
Looks like both may not be able to claim this as there “own”…as it looks like there are a lot more ‘dogs’…in this ‘dog fight’ 😉
“Most generic extensions are going to be open, that is most of the domains will be available. I don’t expect that many of these generic to be closed for the use of only one company”
But with a very specific few…IMHO the winner will keep it closed. There is no way I see a company like “Apple inc”, opening up the .app extension to anyone, if they end up owning it…as an example.
People may want to learn more about how the OLD DNS works and also the NEW DNS…
It is all based on Software that humans install…
People write the Software … no one approves the code … and people install it and run it…
TLDs do not come from cargo planes or earthquakes
*** NEWSFLASH ***
Announcing the greatest new thing to hit the wire since lunchtime, Linny Enterprises is pleased to introduce dotSCAM!
Yes, thats right folks – for a small one time fee you can be part of this amazing $$$investment opportunity$$$!
We will be applying for the new .SCAM tld (unless we decide not to) and will promise to give you back some of your money, if there is any. This is YOUR chance to grab your .SCAM domain ahead of the rest, apply now before theyre all gone!
Seems like their largest concern is that a single entity may monopolize the space and not allow outside use. This could be possible, though MHB thinks it unlikely. If the .APP registry keeps the TLD open, their concerns are abated.
Interesting though, some question the viability of niche TLDs, saying that the target markets will not be interested. Here however, is a target niche TLD whose target audience is willing to FIGHT for the ability to use the space.
Not a good sign for legacy domainers and .FAIL advocates IMO
Adapt or Perish
Did I not say in a previous comment on a previous post somewhere that companies should presell to cover the app fees as If they can get their app fees covered then they are more likely to succeed. Heck at least a huge chunk of 1st year expenses are paid.
TheBigLie Society says
“For twenty-five years, Audio Precision has designed the finest audio analyzers in the world”
The new DNS Software queries the NameServers (NS) for the NS records for the .AP Top Level Domain
Most people get their DNS from the DNS Software in their CPE Router/Modem
All 2-Letter Top Level Domains “exist”
“it’s all based on software that people install”
yep. and in the old days computers came without software. they were kits.
but… enter microsoft. they convinced the computer makers to put software on the computers before selling them. surprise, people accept this!
then… enter dell. they assemble computers out of dirt cheap parts and sell them for $350 and up.
the ultimate computer is one that
1. you can build yourself – imagine building one that has a form factor even better looking that apple.
2. which comes without pre-installed crapware. you put your own software on it. you install an “os” that suits what you like to do.
#1 is a pipe dream at this stage. but give it time.
#2 is not far away. at present, you have to remove the crapware. this annoyance will eventually lead to it being removed for you.
if you install someone else’s software and you don’t understand what it does (you don’t look at the code and you don’t know the code of your compiler) then the software author can do with your computer as he pleases. so think twice before installing stuff by people who won’t let you see the code.
the dns we are used to is one approach to a very simple task. under ipv4 you have a 6 to 12-digit number that you need to type in to reach another computer, e.g., your favourite website. kinda like dialing a telephone number.
incidentally, what’s the difference between a phone and a computer? it’s getting harder to see that difference. pretty soon they’ll all use the same network- because it’s cheaper- it’s inevitable. so the distinction will continue to blur.
an obvious idea for making this number dialling (typing) task easier is to give the number a name (or “alias”), like speed dial. very, very simple thing. the software code is not complex.
ok, so we’ve done that.
now, here’s where it gets interesting. how often do these “phone numbers” for other computers change? does your bank change it’s phone number every week, every day, every few hours?
today, most publically accessible computers don’t either. if they did, there should be good reason. unless someone is trying to be evasive, there’s only a few good reasons the numbers need to be changed. and advance notice of the change should be provided to the public. common sense.
but guess when the dns we’re using was created? the 1980’s. at that time, things were different. there were new numbers coming “online” (participating in the new, public “internetwork”) every week.
at that time, internal networks, where numbers have to changeable easily, were perhaps even more important than the new, public “internetwork”. one had to have flexibility to deal with constantly changing network numbers. a solution for this was needed.
the conditions are different today. we know what all the assigned network numbers are. they’ve all been handed out (with few exceptions). in fact, if a new block of network numbers suddenly comes online, it’s cause for _suspicion_. with ip addresses, things are very _static_. we know who has the numbers.
so in the 80’s with new numbers appearing constantly on this new, public “internetwork”, how did we solve that problem? stop distributing the “phonebook”. discourage using it and discourage using a phonebook. in nerd speak: “deprecate”.
instead, everyone was to dial “directory assistance”. every time. no phonebook necessary.
in a community effort, we can maintain a volunteer directroy assistance service. no one is accountable- we all play a role in keeping the name->number info current. it’s a community effort. we cooperate so the internetwork works smoothly.
great. it worked. and it still works today, 20+ years. amazing.
but times have changed. that spirit of community is gone. in the nerd community, no one trusts anyone. they are obsessed with cryptography. the network is huge. “the numbers have all been handed out”. no more new ones (is what they want you to believe).
but we still dial “directory assistance” every day, 100’s even 1000’s of times! why? even though everyone agrees the environment is untrustworthy, still no one is accountable for the system, “the dns”, that we use. the info might be accurate, or it might not.
it still relies on the “internet community” (the _1980’s internet community_) to be honest, to only provide accurate info. but are they honest? the “community” is not small. it’s largely anonymous. you make the call.
with today’s internet such a system is ripe for abuse. and that’s what you see. the people biglie talks about… many of them are from that 1980’s community. what’s amusing to consider is: are they honest with the public, now, like they were with each other in the 80’s?
anyway, hats off to them for cashing in.
however, could we still go back to the “phonebook”? would it work? you bet it would. and there’s other ways to do the simple number->name task too. this is not secret knowledge. it’s published all over the ‘net. these alternaives are always there, looming in the wings, waiting to be rediscovered, when it becomes prudent to use them.
so laugh at the .app people if you want. but to think the 1980’s crowd is going to keep a hold on this very simple number->name task _forever_ is also laughable. eventually it’s going to be replaced. because the abuse of the current 80’s dns will reach a breaking point. gtlds are a move in that direction.
if the dns continues on its present course, the breaking point _will_ come. the only question is when.