RunRev Blog | RunRev

Jul 14 10

Innovation on Android

I was very pleased to read Google's recent announcement of their App Inventor for Android. It seems to me that this is the latest in a series of announcements that demonstrates just how much Google values innovation at all levels. In another pointed example just two months ago at the keynote introducing Froyo at Google I/O in May, Vic Gundotra, Google VP must have managed to mention openness, inclusiveness and innovation just about every two minutes during the presentation! It seems that Google are making a big commitment that's very much in contrast to a certain other mobile OS vendor. They are putting up neon signs around their platform that shout out that all developers are welcome.

One of the features that has slipped into Froyo that may not have garnered as much attention as some of the headlines, is the ability to draw directly into a bitmap from their native code interface. In plain English, that makes it much easier for native code platforms such as Rev to support Android with good rendering performance. There is no question that Google are looking closely at the detail when it comes to attracting as many as possible to the platform.

App Inventor looks like a great way for new developers to get into the platform. It clearly has the potential to inspire a new group of non-programmers into developing Android apps. Some may argue that it could flood the Android Marketplace with "junk" and thus reduce the quality of the end user experience. Of course that's possible, but on the flip side I would argue that surely it's more likely that we can simply rely on market forces to weed out the good and the bad as happens in just about every other industry? Who is to say that one of these App Inventor Apps won't become the next killer app?

There is a certain irony when you consider all of this in a historical context. I recall back in the 80s and 90s, Apple was the platform with the easy-to-use HyperCard programming environment that attracted non-developers and entry-level tinkerers, prosumers and enthusiasts, anyone who wanted to create their own software or get under the hood of their machine and learn how it worked. With the iPhone firmly closed to this sort of creative user it's great to see a new platform open up that positively invites that sort of innovation and learning. It's a major shift in the way-things-are-going-to-be during this next decade.

I'd agree with those commentators who have suggested that many of those starting out in App Inventor are going to want to go on to learn a full programming language such as Java later. The key thing from Google's perspective is that those developers-to-be will all be very much into using Android devices. After having initially been attracted to the Android platform they are likely to stay there. That may not matter much to the more typical Android end-user just now, but as more and more high quality applications get developed for the Marketplace that has the potential to change. Apple should be worried.

The final reason that I'm so excited by App Inventor is of course a little more self serving. Over the last decade we've watched many point and click programming tools come and go and we know they are great for getting people started and certain types of cookie cutter application, but users often outgrow them over time. I'm sure that Google knows that too and is expecting many to step on up to Java or another programming language when they want to do a bit more. However it seems to me that there is an excellent fit for a Rev for Android product here, as a more gentle step up to a fully featured programming language, without the learning curve associated with a language such as Java. We'll be watching App Inventor closely and looking for ways we might be able to interoperate with it in the future.

All in all very exciting times. Stay tuned for more on our Android strategy soon.

I was very pleased to read Google's recent announcement of their App Inventor for Android. It seems to me that this is the latest in a series of announcements that demonstrates just how much Google values innovation at all levels. In another pointed example just two months ago at the keynote introducing Froyo at Google I/O in May, Vic Gundotra, Google VP must have managed to mention openness, inclusiveness and innovation just about every two minutes during the presentation! It seems that Google are making a big commitment that's very much in contrast to a certain other mobile OS vendor. They are putting up neon signs around their platform that shout out that all developers are welcome.

One of the features that has slipped into Froyo that may not have garnered as much attention as some of the headlines, is the ability to draw directly into a bitmap from their native code interface. In plain English, that makes it much easier for native code platforms such as Rev to support Android with good rendering performance. There is no question that Google are looking closely at the detail when it comes to attracting as many as possible to the platform.

App Inventor looks like a great way for new developers to get into the platform. It clearly has the potential to inspire a new group of non-programmers into developing Android apps. Some may argue that it could flood the Android Marketplace with "junk" and thus reduce the quality of the end user experience. Of course that's possible, but on the flip side I would argue that surely it's more likely that we can simply rely on market forces to weed out the good and the bad as happens in just about every other industry? Who is to say that one of these App Inventor Apps won't become the next killer app?

There is a certain irony when you consider all of this in a historical context. I recall back in the 80s and 90s, Apple was the platform with the easy-to-use HyperCard programming environment that attracted non-developers and entry-level tinkerers, prosumers and enthusiasts, anyone who wanted to create their own software or get under the hood of their machine and learn how it worked. With the iPhone firmly closed to this sort of creative user it's great to see a new platform open up that positively invites that sort of innovation and learning. It's a major shift in the way-things-are-going-to-be during this next decade.

I'd agree with those commentators who have suggested that many of those starting out in App Inventor are going to want to go on to learn a full programming language such as Java later. The key thing from Google's perspective is that those developers-to-be will all be very much into using Android devices. After having initially been attracted to the Android platform they are likely to stay there. That may not matter much to the more typical Android end-user just now, but as more and more high quality applications get developed for the Marketplace that has the potential to change. Apple should be worried.

The final reason that I'm so excited by App Inventor is of course a little more self serving. Over the last decade we've watched many point and click programming tools come and go and we know they are great for getting people started and certain types of cookie cutter application, but users often outgrow them over time. I'm sure that Google knows that too and is expecting many to step on up to Java or another programming language when they want to do a bit more. However it seems to me that there is an excellent fit for a Rev for Android product here, as a more gentle step up to a fully featured programming language, without the learning curve associated with a language such as Java. We'll be watching App Inventor closely and looking for ways we might be able to interoperate with it in the future.

All in all very exciting times. Stay tuned for more on our Android strategy soon.

Share this using:

Jul 9 10

revSelect Continues Growth Surge

In recent months revSelect, our marketplace for affiliated vendors and Rev addon products, has signed no fewer than three new vendors and gained five fine new products to add functionality to Rev. We're delighted to welcome on board Andres Martinez of baKno Games [link to http://bakno.com/], Curry Kenworthy [link to http://curryk.com/consulting/] with his excellent Wordlib, and Hugh Senior from The Flexible Learning Company [link to http://www.flexiblelearning.com].

Andres Martinez is originally from Colombia and worked at Apple Colombia for five years before moving to Miami to study for an MBA. After 10 years working for a networking technology distributor he founded baKno Games. He brings his newly created external, IntelAble to revSelect. This allows Rev developers to easily publish their apps to the Intel App store, a growing new market.

Curry Kenworthy is a seasoned computer software developer and shareware publisher with a wide variety of applications under his belt. He provides web page design, SEO, data manipulation, and other technical consulting services. His WordLib library for importing Word and Open Office files into Rev is already proving popular in the Rev community.

Hugh Senior is an educationalist, software architect and already known in the Rev community as the author of The Scripter's Scrapbook, an invaluable utility for programmers everywhere. We're delighted to welcome his latest library ChartMaker 2 into the revSelect family.

[optional additional sentence] To celebrate all these new products RunRev are offering a Summer Kit [http://www.runrev.com/mailers/RS/rs-2010-7-summerkit.html] throughout the month of July.

In recent months revSelect, our marketplace for affiliated vendors and Rev addon products, has signed no fewer than three new vendors and gained five fine new products to add functionality to Rev!

We're delighted to welcome on board Andres Martinez of baKno Games, Curry Kenworthy with his excellent Wordlib, and Hugh Senior from The Flexible Learning Company.

Andres Martinez is originally from Colombia and worked at Apple Colombia for five years before moving to Miami to study for an MBA. After 10 years working for a networking technology distributor he founded baKno Games. He brings his newly created external, IntelAble to revSelect. This allows Rev developers to easily publish their apps to the Intel App store, a growing new market.

Curry Kenworthy is a seasoned computer software developer and shareware publisher with a wide variety of applications under his belt. He provides web page design, SEO, data manipulation, and other technical consulting services. His WordLib library for importing Word and Open Office files into Rev is already proving popular in the Rev community.

Hugh Senior is an educationalist, software architect and already known in the Rev community as the author of The Scripter's Scrapbook, an invaluable utility for programmers everywhere. We're delighted to welcome his latest library ChartMaker 2 into the revSelect family.

We also welcome in revSelect the latest new products by existing vendors. NativeSoft this month added the great new utility GeometryManager. Also new is Franklin 3D, from Mirye, a powerful external that adds a complete, professional 3D game engine to the Rev development environment.

To celebrate all these new products RunRev are offering a Summer Productivity Kit throughout the month of July, including all of these products bundled at a discounted price.

Share this using:

May 10 10

RunRev CEO Kevin Miller on revMobile and Apple's new iPhone SDK Agreement

revMobile and Apple's new iPhone SDK Agreement

As you may know, on the 8th of April, Apple changed the iPhone Developer Program License Agreement, which impacts our development of revMobile. The new agreement added a clause which required that applications be originally written in Objective-C, C++ or JavaScript. As revMobile applications are originally written in revTalk, not in one of these languages, their policy changes effectively prohibit revMobile on the iPhone/iPad. The new clause also prohibits frameworks and compatibility layers, which also describes revMobile in its present form.

This change took us, and thousands of other iPhone developers, by surprise. We greatly value our customers and we know how much you depend on us to provide an outstanding and reliable service. Since this announcement, we have been working around the clock to develop a strategy for that will allow us to continue to provide you with the service that you expect and deserve. The surprise from Apple’s announcement is heightened by the fact that Apple’s policy seems to be at odds with recent comments from Steve Jobs himself.

In response to a question in a recent Apple shareholder’s meeting, Jobs said that a HyperCard-like product for the iPad would be a good idea “though someone would have to build it”. Many blog posts suggested that Apple's intention with this change was to ban cross-compilers and ensure high quality, fully native iPhone apps. Jobs all but confirmed [http://techcrunch.com/2010/04/10/steve-jobs-responds-to-iphone-sdk-complaints-intermediate-layers-produce-sub-standard-apps/] the analysis on John Gruber's site [http://daringfireball.net/2010/04/why_apple_changed_section_331]. The Mac platform in particular has a long legacy surrounding HyperCard and as virtually the last man standing in this space. We believed we were in a position to offer Apple something they wanted.

It makes perfect sense to have a high quality, rapid application development system available for the iPhone and iPad. Our customers agree. revMobile, even its pre-alpha form, received some of the strongest and most positive feedback from our customers that we've ever seen. We are aware of numerous exciting applications being developed even at this early stage. For example, one of our customers, EuroTalk interactive, have government funding to deploy thousands of iPads to schools in Malawi [http://www.scotland.gov.uk/News/Releases/2010/03/18130728] in a pilot project that will expand to tens of thousands of users. They intend to deploy hundreds of small teaching applications to iPads. It makes no sense for those applications to be developed in Objective-C or JavaScript, and EuroTalk will be looking seriously at other tablet manufacturers if they are unable to use revMobile.

Our Pitch to Apple

In order to support our active and growing revMobile customer base, we submitted an in-depth proposal to Apple that we create an iPhone-only product that uses native Cocoa objects, supports 100% of their API, works perfectly with multitasking and battery life, but uses a variant of the revTalk language to use these objects and APIs, and then translates those into native code. While a significant engineering departure for us from the current revMobile path, this solution would have resulted in perfect-quality iPhone-only applications impossible to distinguish from native applications. It would have been impossible to tell these applications apart from native iPhone applications because they would be native applications. As native applications running directly without a compatibility layer, there would have been no battery life issues, multitasking and iAds would work perfectly, and new APIs would be supported as they came out. In other words, we set out to offer Apple what they wanted by raising our game in response to their stricter requirements, while dropping the other mobile platforms we originally intended to support.

Apple's platform would have benefited immeasurably from a high-level, iPhone/iPad-only development tool that is 10x more productive than Objective-C and honors the HyperCard legacy still present on their Mac platform today. So strong is this platform legacy that millions of applications are shipped using Rev technology, and one of the investors in RunRev was himself a co-founder of Apple. With our proposed solution, tens of thousands of our customers would have been able to continue to use revMobile to develop these exciting applications and solutions in much the same way as was possible with our existing Rev product line, albeit at the cost of cross-device compatibly. There would have been no risk to Apple in any such agreement as we would comply with their terms in their entirety. Apple approves applications all the time for their store; ours simply would have been one more.

Steve Jobs has now rejected our proposal and made it clear that he has no interest in having revMobile available on the iPhone or iPad in any form.

Obviously, this is a huge disappointment for us and our customers. The analysis we read both on Apple.com [http://www.apple.com/hotnews/thoughts-on-flash/] and on many blogs [http://developer.appcelerator.com/blog/] suggest that their main target might be Flash. Clearly this is not the case. We know that like any other company, Apple has the right to make decisions they deem necessary to maintain their competitive edge and protect shareholder value. However, had they made their decision public earlier in the evolution of the platform, it would have saved us and thousands of other developers what must add up to millions of dollars of wasted engineering budget. Their strategy makes it impossible for us to provide revMobile at the same feature set and service level currently in use by our loyal customers.

The Path Forward

Some of our customers have suggested that we continue to develop the version of revMobile that outputs entirely native code (as detailed above). However such a solution--even though it would create perfect applications--would be in violation of Apple's agreement, which states that code must originally be developed in one of their approved languages. As such, we cannot risk hundreds of thousands of dollars of further engineering budget to create a solution that does not guarantee Apple acceptance to the app store.

We will continue to offer revMobile as an excellent prototyping tool for iPhone and iPad applications. A large proportion of development time is spent during the design phase of any application and revMobile offers an unbeatable solution for that. We will also continue to offer revMobile to those who are members of the Apple Enterprise developer program (including educators who are part of the program) who want to deploy applications to their own devices and in-house.

However we cannot make any guarantee, now or in the future, that revMobile will be in compliance with Apple licensing provisions. It is impossible to make such guarantees as Apple reserve the right to change their terms at any point, and have clearly demonstrated their willingness to exercise this right to make sweeping changes without notice. It is up to individual customers to satisfy themselves of Apple requirements.

While we will be shipping revMobile as a product, we reluctantly have no choice but to scale back development on it. We can no longer create the native interface objects layer, but rather invite our community to develop a set of emulated objects. We also will no longer build the native-code compiler, as this is a vast engineering project that’s purpose was to facilitate submission of applications to the app store.

Given these business changes, we are pushing back our RunRevLive.10 conference to April next year, and are focusing on developing significant and exciting enhancements to the Rev platform. We have many exciting projects in the pipeline including an overhaul to our Unicode support, enhanced text display, improvements to the revWeb plugin, the rollout of revServer and much more. We are turning our mobile sights to the Android platform, and will unveil an aggressive strategy for supporting Android development projects. We will also roll out the updated Rev platform roadmap for our revEnterprise customers shortly.

The industry we work in moves quickly and we have always worked tirelessly to make sure the Rev platform enables you to take advantage of new and innovative technologies. That change has been particularly quick over the past month. But there are many new opportunities out there and we look forward to finding ways to enable you to take advantage of them. And all these changes notwithstanding, we still believe that revMobile remains the most sophisticated iPhone/iPad prototyping and Enterprise development tool in the world. We’ll be posting more updates and lessons for it shortly.

We have always worked hard to be a trusted partner for the many thousands of customers and businesses that use Rev. We’re going to continue to take care of everyone in our community. We will be redoubling our efforts to move forward in a new direction that enables you in new ways. I hope you’ll stay with us through this transition. Our customers are the reason we are here and we thank you sincerely for the unwavering commitment and support you’ve shown us.

Keep your eyes on exciting new developments from us in the coming months.

Kevin Miller

RunRev CEO, 10th May 2010

As you may know, on the 8th of April, Apple changed the iPhone Developer Program License Agreement, which impacts our development of revMobile. The new agreement added a clause which required that applications be originally written in Objective-C, C++ or JavaScript. As revMobile applications are originally written in revTalk, not in one of these languages, their policy changes effectively prohibit revMobile on the iPhone/iPad. The new clause also prohibits frameworks and compatibility layers, which also describes revMobile in its present form.

This change took us, and thousands of other iPhone developers, by surprise. We greatly value our customers and we know how much you depend on us to provide an outstanding and reliable service. Since this announcement, we have been working around the clock to develop a strategy that will allow us to continue to provide you with the service that you expect and deserve. The surprise from Apple’s announcement is heightened by the fact that Apple’s policy seems to be at odds with recent comments from Steve Jobs himself.

In response to a question in a recent Apple shareholder’s meeting, Jobs said that a HyperCard-like product for the iPad would be a good idea “though someone would have to build it”. Many blog posts suggested that Apple's intention with this change was to ban cross-compilers and ensure high quality, fully native iPhone apps. Jobs all but confirmed the analysis on John Gruber's site. The Mac platform in particular has a long legacy surrounding HyperCard and as virtually the last man standing in this space. We believed we were in a position to offer Apple something they wanted.

It makes perfect sense to have a high quality, rapid application development system available for the iPhone and iPad. Our customers agree. revMobile, even its pre-alpha form, received some of the strongest and most positive feedback from our customers that we've ever seen. We are aware of numerous exciting applications being developed even at this early stage. For example, one of our customers, EuroTalk interactive, have government funding to deploy thousands of iPads to schools in Malawi in a pilot project that will expand to tens of thousands of users. They intend to deploy hundreds of small teaching applications to iPads. It makes no sense for those applications to be developed in Objective-C or JavaScript, and EuroTalk will be looking seriously at other tablet manufacturers if they are unable to use revMobile.

Our Pitch to Apple

In order to support our active and growing revMobile customer base, we submitted an in-depth proposal to Apple that we create an iPhone-only product that uses native Cocoa objects, supports 100% of their API, works perfectly with multitasking and battery life, but uses a variant of the revTalk language to use these objects and APIs, and then translates those into native code. While a significant engineering departure for us from the current revMobile path, this solution would have resulted in perfect-quality iPhone-only applications impossible to distinguish from native applications. It would have been impossible to tell these applications apart from native iPhone applications because they would be native applications. As native applications running directly without a compatibility layer, there would have been no battery life issues, multitasking and iAds would work perfectly, and new APIs would be supported as they came out. In other words, we set out to offer Apple what they wanted by raising our game in response to their stricter requirements, while dropping the other mobile platforms we originally intended to support.

Apple's platform would have benefited immeasurably from a high-level, iPhone/iPad-only development tool that is 10x more productive than Objective-C and honors the HyperCard legacy still present on their Mac platform today. So strong is this platform legacy that millions of applications are shipped using Rev technology, and one of the investors in RunRev was himself a co-founder of Apple. With our proposed solution, tens of thousands of our customers would have been able to continue to use revMobile to develop these exciting applications and solutions in much the same way as was possible with our existing Rev product line, albeit at the cost of cross-device compatibly. There would have been no risk to Apple in any such agreement as we would comply with their terms in their entirety. Apple approves applications all the time for their store; ours simply would have been one more.

Steve Jobs has now rejected our proposal and made it clear that he has no interest in having revMobile available on the iPhone or iPad in any form.

Obviously, this is a huge disappointment for us and our customers. The analysis we read both on Apple.com and on many blogs suggest that their main target might be Flash. Clearly this is not the case. We know that like any other company, Apple has the right to make decisions they deem necessary to maintain their competitive edge and protect shareholder value. However, had they made their decision public earlier in the evolution of the platform, it would have saved us and thousands of other developers what must add up to millions of dollars of wasted engineering budget. Their strategy makes it impossible for us to provide revMobile at the same feature set and service level currently in use by our loyal customers.

The Path Forward

Some of our customers have suggested that we continue to develop the version of revMobile that outputs entirely native code (as detailed above). However such a solution--even though it would create perfect applications--would be in violation of Apple's agreement, which states that code must originally be developed in one of their approved languages. As such, we cannot risk hundreds of thousands of dollars of further engineering budget to create a solution that does not guarantee Apple acceptance to the app store.

We will continue to offer revMobile as an excellent prototyping tool for iPhone and iPad applications. A large proportion of development time is spent during the design phase of any application and revMobile offers an unbeatable solution for that. We will also continue to offer revMobile to those who are members of the Apple Enterprise developer program (including educators who are part of the program) who want to deploy applications to their own devices and in-house.

However we cannot make any guarantee, now or in the future, that revMobile will be in compliance with Apple licensing provisions. It is impossible to make such guarantees as Apple reserve the right to change their terms at any point, and have clearly demonstrated their willingness to exercise this right to make sweeping changes without notice. It is up to individual customers to satisfy themselves of Apple requirements.

While we will be shipping revMobile as a product, we reluctantly have no choice but to scale back development on it. We can no longer create the native interface objects layer, but rather invite our community to develop a set of emulated objects. We also will no longer build the native-code compiler, as this is a vast engineering project that’s purpose was to facilitate submission of applications to the app store.

Given these business changes, we are pushing back our RunRevLive.10 conference to April next year, and are focusing on developing significant and exciting enhancements to the Rev platform. We have many exciting projects in the pipeline including an overhaul to our Unicode support, enhanced text display, improvements to the revWeb plugin, the rollout of revServer and much more. We are turning our mobile sights to the Android platform, and will unveil an aggressive strategy for supporting Android development projects. We will also roll out the updated Rev platform roadmap for our revEnterprise customers shortly. 

The industry we work in moves quickly and we have always worked tirelessly to make sure the Rev platform enables you to take advantage of new and innovative technologies. That change has been particularly quick over the past month. But there are many new opportunities out there and we look forward to finding ways to enable you to take advantage of them. And all these changes notwithstanding, we still believe that revMobile remains the most sophisticated iPhone/iPad prototyping and Enterprise development tool in the world. We’ll be posting more updates and lessons for it shortly.

We have always worked hard to be a trusted partner for the many thousands of customers and businesses that use Rev. We’re going to continue to take care of everyone in our community. We will be redoubling our efforts to move forward in a new direction that enables you in new ways. I hope you’ll stay with us through this transition. Our customers are the reason we are here and we thank you sincerely for the unwavering commitment and support you’ve shown us.

Keep your eyes on exciting new developments from us in the coming months.

Kevin Miller

RunRev CEO, 10th May 2010

Share this using:

Apr 13 10

RunRev Initial Response to Apple's iPhone OS 4.0 SDK announcement

As part of Apple's iPhone OS 4.0 SDK announcement last week, Apple have posted updated iPhone Terms of Service. The specifics of these changes are under NDA so we cannot discuss them at this point. We have an excellent relationship with Apple and we will be working with them to address any specific issues that may need clarification in relation to their proposed changes. We will do everything possible to ensure a speedy and positive resolution that allows our customers to deliver outstanding apps on the revMobile platform in full compliance with Apple policies. We will communicate further information over the coming days as our discussions develop.

Share this using:

Mar 31 10

revMobile Development Proceeding Fast

Today we bring you the revMobile pre-Alpha 7 for iPhone, with several great new features:

• 'launch url': Now you can place voice calls, open the 'Maps' application or launch URLs in Safari using this feature

• 'beep': performs an alert based on the user's settings

• 'the beepSound': configure the sound to use for 'beep'

• 'play': basic support for playing sound files has been added, so you can play a single sound once or as a loop.

These features have been added to our new iPhone & iPad Supported Features page.

The new pre-Alpha also implements the following useful and important items:

• 'the fontNames'/'fontStyles()': find out what fonts are installed

• system date/time: use the user's configured locale to format dates and times

• uniEncode/uniDecode: convert between different text encodings

• specialFolderPath('engine'): get the folder containing the engine and other bundle resources

Today is the last day to get our very special pre-order revMobile package including revLive 2010 Simulcast access and the 2010 conference DVD box set. If you haven't already signed up you can do so here. Read more about revMobile at our newly updated revMobile Website.

Share this using: