<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Shibuya and Sharify</title>
	<atom:link href="http://www.kelvinluck.com/2009/10/shibuya-and-sharify/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/</link>
	<description>a stroke of luck</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:32:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-73220</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 12 Aug 2011 19:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-73220</guid>
		<description>Kevin - 

I notice you have a recent post... do you have a expected date for the public release of Sharify?

thanks!</description>
		<content:encoded><![CDATA[<p>Kevin - </p>
<p>I notice you have a recent post... do you have a expected date for the public release of Sharify?</p>
<p>thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin Luck</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-67412</link>
		<dc:creator>Kelvin Luck</dc:creator>
		<pubDate>Wed, 08 Jun 2011 19:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-67412</guid>
		<description>I can&#039;t comment on Adobe Market Place but I can assure that Sharify certainly isn&#039;t dead. In fact, we are very close to releasing an update to the members of our private beta...</description>
		<content:encoded><![CDATA[<p>I can't comment on Adobe Market Place but I can assure that Sharify certainly isn't dead. In fact, we are very close to releasing an update to the members of our private beta...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-67323</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Tue, 07 Jun 2011 17:42:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-67323</guid>
		<description>Just stubmled upon this post again today. Sometimes a recap is nice :)

So, 2 years later where are we at?
- Sharify is dead
- Adobe Market Place is pathetic
-- Sales / Traffic are horrible
-- The approval process is slow, and uni-directional (no email updates, no correspondance at all)
-- This admin console is pathetically simple (1 graph, with no totals, or any real useful info)
-- The customer support is basically non-existant


Adobe, if you&#039;re going to kill something off, then at least replace it with something you&#039;re willing to fund properly.

I stuck with Shibuya/Melrose/InMarket/Adobe MarketPlace for over a year, and saw almost no development whatsoever on the admin console. And this is when you&#039;re in beta and should be rapidly iterating!?

What ,do you have a single dev, working part-time on this thing? It&#039;s ridiculous...</description>
		<content:encoded><![CDATA[<p>Just stubmled upon this post again today. Sometimes a recap is nice :)</p>
<p>So, 2 years later where are we at?<br />
- Sharify is dead<br />
- Adobe Market Place is pathetic<br />
-- Sales / Traffic are horrible<br />
-- The approval process is slow, and uni-directional (no email updates, no correspondance at all)<br />
-- This admin console is pathetically simple (1 graph, with no totals, or any real useful info)<br />
-- The customer support is basically non-existant</p>
<p>Adobe, if you're going to kill something off, then at least replace it with something you're willing to fund properly.</p>
<p>I stuck with Shibuya/Melrose/InMarket/Adobe MarketPlace for over a year, and saw almost no development whatsoever on the admin console. And this is when you're in beta and should be rapidly iterating!?</p>
<p>What ,do you have a single dev, working part-time on this thing? It's ridiculous...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Seyfi</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-21609</link>
		<dc:creator>Philip Seyfi</dc:creator>
		<pubDate>Sat, 31 Oct 2009 14:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-21609</guid>
		<description>@TAD: Flashden sells ready-made files that allow clients to use (or even create) Flash files without purchasing Adobe Flash IDE which potentially lowers the sales of the software.</description>
		<content:encoded><![CDATA[<p>@TAD: Flashden sells ready-made files that allow clients to use (or even create) Flash files without purchasing Adobe Flash IDE which potentially lowers the sales of the software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tad</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20916</link>
		<dc:creator>Tad</dc:creator>
		<pubDate>Thu, 22 Oct 2009 17:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20916</guid>
		<description>I thought that Adobe was &quot;cooler&quot; than this.
I feel a little heart broken. 
What of other words like actionscript? 
Are they going to make actionscript.org change their name?

They just made Flashden change, but the other, not so popular, places have been left alone as of now. 
What&#039;s up with all of these name games?

Doesn&#039;t it help Adobe that others want to use and enhance their platform?

Take a  C++ developer for instance, say one day that developer stumbles upon Flashden (Activeden) or Sharify and sees that they can make money using the Flash platform;  they are probably going to have to eventually buy an Adobe product if they want to seriously develop for the platform.
So, why does Adobe have any beef with sites that direct people to their own products?
Really seems counter intuitive.

In 2002 I fell in complete love with the Flash platform and in &#039;06 I thought the Adobe take over was a very good thing.. but what&#039;s happened to Kelvin seems a bit shady to me.
 
The Adobe community only gets hurt by these kinds of things, &quot;A house divided by itself cannot stand.&quot;</description>
		<content:encoded><![CDATA[<p>I thought that Adobe was "cooler" than this.<br />
I feel a little heart broken.<br />
What of other words like actionscript?<br />
Are they going to make actionscript.org change their name?</p>
<p>They just made Flashden change, but the other, not so popular, places have been left alone as of now.<br />
What's up with all of these name games?</p>
<p>Doesn't it help Adobe that others want to use and enhance their platform?</p>
<p>Take a  C++ developer for instance, say one day that developer stumbles upon Flashden (Activeden) or Sharify and sees that they can make money using the Flash platform;  they are probably going to have to eventually buy an Adobe product if they want to seriously develop for the platform.<br />
So, why does Adobe have any beef with sites that direct people to their own products?<br />
Really seems counter intuitive.</p>
<p>In 2002 I fell in complete love with the Flash platform and in '06 I thought the Adobe take over was a very good thing.. but what's happened to Kelvin seems a bit shady to me.</p>
<p>The Adobe community only gets hurt by these kinds of things, "A house divided by itself cannot stand."</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Christensen</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20726</link>
		<dc:creator>Rob Christensen</dc:creator>
		<pubDate>Mon, 19 Oct 2009 07:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20726</guid>
		<description>@Kelvin 

1. Thank you for responding back and accepting my apology. 

2. Again, please let me know when you come out of beta. 

3. I apologize if the &quot;tone of my emails&quot; seemed short. Looking back at our conversation, I believe the only email that appeared short was the last one and that was because I was responding from my phone and, to be honest, did not have anything more to add at the time. 

4. With regard to your points around Shibuya, I will relay your feedback to the team as your request is quite reasonable. So you know, in my role, I am focused on the lower level API&#039;s that make up the AIR runtime.</description>
		<content:encoded><![CDATA[<p>@Kelvin </p>
<p>1. Thank you for responding back and accepting my apology. </p>
<p>2. Again, please let me know when you come out of beta. </p>
<p>3. I apologize if the "tone of my emails" seemed short. Looking back at our conversation, I believe the only email that appeared short was the last one and that was because I was responding from my phone and, to be honest, did not have anything more to add at the time. </p>
<p>4. With regard to your points around Shibuya, I will relay your feedback to the team as your request is quite reasonable. So you know, in my role, I am focused on the lower level API's that make up the AIR runtime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bigelow</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20603</link>
		<dc:creator>David Bigelow</dc:creator>
		<pubDate>Fri, 16 Oct 2009 20:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20603</guid>
		<description>Kelvin (sorry been slamming your spelling all along),  :(

We are in fundamental agreement on all of this.

On a related note (and this could be a blog entry on it&#039;s own) - I think that until Flex/AIR are able to be held up as something other than a perception of &quot;Flash&quot; it will be hard to go beyond a perceived value of FREE &#039;entertainment&#039; or low cost &#039;do-dad&#039; application.  &quot;Flash&quot; does not cast an impression of &#039;mission critical&#039; or &#039;essential&#039; for customers/end-users on a regular basis.

I think Adobe &#039;stepped on their own&#039; with that decision to standardize on the name of &#039;Flash Platform&#039;.  That forces us to fight the &#039;snickers&#039; in the Enterprise when they hear &quot;Flash&quot;.  This is an unfortunate knowledge gap that has been deepened within the enterprise in my own opinion that will prolong commercial acceptance of Flex/AIR applications - and keep prices and perceived values LOW....

So only time will tell - true value should have a price.  If an Application is is needed, customers will not have a problem paying for it, or re-paying for it over time.  If it is nothing more than a passively used &#039;widget&#039; or screen decoration, that is a different story/purpose/existence.

Cheers!

Dave</description>
		<content:encoded><![CDATA[<p>Kelvin (sorry been slamming your spelling all along),  :(</p>
<p>We are in fundamental agreement on all of this.</p>
<p>On a related note (and this could be a blog entry on it's own) - I think that until Flex/AIR are able to be held up as something other than a perception of "Flash" it will be hard to go beyond a perceived value of FREE 'entertainment' or low cost 'do-dad' application.  "Flash" does not cast an impression of 'mission critical' or 'essential' for customers/end-users on a regular basis.</p>
<p>I think Adobe 'stepped on their own' with that decision to standardize on the name of 'Flash Platform'.  That forces us to fight the 'snickers' in the Enterprise when they hear "Flash".  This is an unfortunate knowledge gap that has been deepened within the enterprise in my own opinion that will prolong commercial acceptance of Flex/AIR applications - and keep prices and perceived values LOW....</p>
<p>So only time will tell - true value should have a price.  If an Application is is needed, customers will not have a problem paying for it, or re-paying for it over time.  If it is nothing more than a passively used 'widget' or screen decoration, that is a different story/purpose/existence.</p>
<p>Cheers!</p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin Luck</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20600</link>
		<dc:creator>Kelvin Luck</dc:creator>
		<pubDate>Fri, 16 Oct 2009 19:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20600</guid>
		<description>Hi Dave,

Thanks for the detailed reply and the further information on Nitro LM!

I can definitely see the market for apps/ services protected by Nitro LM and I think that what you say makes a lot of sense in that marketplace. I would definitely recommend companies building a large, complex applications which ARE their product to check it out. 

On the other hand, I think that there is a large market for apps which are simpler and cheaper and sold for a one off fee (as seen by the massive success of applications in Apple&#039;s App Store). And I feel that the advantage of AIR is that it empowers lots of developers trained in the ways of the web to create exactly these simple yet desirable applications.

Basically I feel that Nitro LM and Sharify serve completely different markets. It just remains to be seen where Shibuya fits into all of this - hopefully all three solutions can co-exist but we shall have to see...

Kelvin.</description>
		<content:encoded><![CDATA[<p>Hi Dave,</p>
<p>Thanks for the detailed reply and the further information on Nitro LM!</p>
<p>I can definitely see the market for apps/ services protected by Nitro LM and I think that what you say makes a lot of sense in that marketplace. I would definitely recommend companies building a large, complex applications which ARE their product to check it out. </p>
<p>On the other hand, I think that there is a large market for apps which are simpler and cheaper and sold for a one off fee (as seen by the massive success of applications in Apple's App Store). And I feel that the advantage of AIR is that it empowers lots of developers trained in the ways of the web to create exactly these simple yet desirable applications.</p>
<p>Basically I feel that Nitro LM and Sharify serve completely different markets. It just remains to be seen where Shibuya fits into all of this - hopefully all three solutions can co-exist but we shall have to see...</p>
<p>Kelvin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bigelow</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20599</link>
		<dc:creator>David Bigelow</dc:creator>
		<pubDate>Fri, 16 Oct 2009 19:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20599</guid>
		<description>Kevin,

Nothing from our end from a notice standpoint regarding Shibuya - just noticed it by accident. (God works in mysterious ways) :)  Adobe did take notice of our solution about 2 years ago and we have a good working relationship with them.

Nitro-LM has several levels of capability and service level:

- &#039;Lite&#039; Versions for unlimited usages with encryption support,
- Standard for licensing and encryption,
- Enterprise for the whole enchilada!

Nitro-LM is designed for customer&#039;s who &#039;actually&#039; are trying to make money.   While it can be used by and for anyone, we are providing a &#039;service&#039;, something that needs to be paid for (typically annually).

This assumes that the Customer&#039;s Product(s) that we are licensing/protecting is -ALSO- providing value, and that our Customers have an expectation for some type of recurring revenue (e.g. upgrades, maintenance, SaaS, etc.).

The &#039;hip&#039; trend of creating/running Micro-ISV&#039;s (i.e. congratulations you created and own a &#039;job&#039;) that place emphasis on a ONE-TIME purchase with FREE upgrades for life are probably -NOT- a good relationship with us... 

Why?  Because their OWN business model works AGAINST themselves!  

Specifically, they will eventually saturate their customer base and not be able to generate more revenue to keep the lights on in order to react to demands from existing customers for &#039;new&#039; features that they have obligated themselves to provide - &#039;forever&#039;...   It does not matter how many customers are obtained or in what timeframe; more customers means a bigger support cost down the road - the business model just does -not- work in the medium/long run.  The feeling of accomplishment is short lived, and the opportunities that are missed are significant.

Hope that makes sense.  There are so many screwed up ways people/companies are conducting their business it is hard for us to identify the &#039;perfect&#039; customer - but if the customer fundamentally is designed to produce a &#039;recurring&#039; revenue, we will probably have a great relationship.  If they are designed to self-destruct, we will advise alternatives (things to consider any why), but in the end will be happy to sit back and watch the destruction.  After all, everyone loves to watch &#039;implosions&#039;... :)

Dave</description>
		<content:encoded><![CDATA[<p>Kevin,</p>
<p>Nothing from our end from a notice standpoint regarding Shibuya - just noticed it by accident. (God works in mysterious ways) :)  Adobe did take notice of our solution about 2 years ago and we have a good working relationship with them.</p>
<p>Nitro-LM has several levels of capability and service level:</p>
<p>- 'Lite' Versions for unlimited usages with encryption support,<br />
- Standard for licensing and encryption,<br />
- Enterprise for the whole enchilada!</p>
<p>Nitro-LM is designed for customer's who 'actually' are trying to make money.   While it can be used by and for anyone, we are providing a 'service', something that needs to be paid for (typically annually).</p>
<p>This assumes that the Customer's Product(s) that we are licensing/protecting is -ALSO- providing value, and that our Customers have an expectation for some type of recurring revenue (e.g. upgrades, maintenance, SaaS, etc.).</p>
<p>The 'hip' trend of creating/running Micro-ISV's (i.e. congratulations you created and own a 'job') that place emphasis on a ONE-TIME purchase with FREE upgrades for life are probably -NOT- a good relationship with us... </p>
<p>Why?  Because their OWN business model works AGAINST themselves!  </p>
<p>Specifically, they will eventually saturate their customer base and not be able to generate more revenue to keep the lights on in order to react to demands from existing customers for 'new' features that they have obligated themselves to provide - 'forever'...   It does not matter how many customers are obtained or in what timeframe; more customers means a bigger support cost down the road - the business model just does -not- work in the medium/long run.  The feeling of accomplishment is short lived, and the opportunities that are missed are significant.</p>
<p>Hope that makes sense.  There are so many screwed up ways people/companies are conducting their business it is hard for us to identify the 'perfect' customer - but if the customer fundamentally is designed to produce a 'recurring' revenue, we will probably have a great relationship.  If they are designed to self-destruct, we will advise alternatives (things to consider any why), but in the end will be happy to sit back and watch the destruction.  After all, everyone loves to watch 'implosions'... :)</p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin Luck</title>
		<link>http://www.kelvinluck.com/2009/10/shibuya-and-sharify/comment-page-1/#comment-20593</link>
		<dc:creator>Kelvin Luck</dc:creator>
		<pubDate>Fri, 16 Oct 2009 17:44:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.kelvinluck.com/?p=826#comment-20593</guid>
		<description>Hi David,
 
I agree with you that Sharify and Nitro-LM serve different segments of the market and that there is plenty of space for them to co-exist. I have looked into Nitro-LM before and it seems to be a well built and robust solution. One thing that I wasn&#039;t clear on even after reading through your material is how much it costs for the developer to include. It seems like the licenses are rented from your company and need to be renewed every year? 

I&#039;d also like to clarify that the latest version of Sharify includes encryption for code protection. I&#039;m interested in whether you guys had any notice from Adobe that they were developing Shibuya?
 
Thanks,
 
Kelvin.</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>I agree with you that Sharify and Nitro-LM serve different segments of the market and that there is plenty of space for them to co-exist. I have looked into Nitro-LM before and it seems to be a well built and robust solution. One thing that I wasn't clear on even after reading through your material is how much it costs for the developer to include. It seems like the licenses are rented from your company and need to be renewed every year? </p>
<p>I'd also like to clarify that the latest version of Sharify includes encryption for code protection. I'm interested in whether you guys had any notice from Adobe that they were developing Shibuya?</p>
<p>Thanks,</p>
<p>Kelvin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 5.179 seconds -->

