Standard SDK across all ereaders?

mike_bike_kite · 07-07-2010, 05:11 AM

Ereaders are just slow computers with even slower screens. Some ereaders have a Software Development Kit (SDK) that allows developers to create applications for them. The small issue for developers at the moment is that if you develop an application for say Pocketbook then this application will only run on Pocketbook devices and you'll have a very limited market.

Is there no possibility of having a standard SDK across all platforms that would allow the same program to be run on all ereaders? Sure devices differ but most are Linux based and all have pretty much the same choice of inputs whether it's a keyboard, a touch screen or perhaps just a 5 way controller. Screen sizes also differ from 5" to 11" with additional options for landscape and portrait modes but the program just needs to know the X,Y dimensions of the current screen. So providing a standard Java interface should be straightforward and it would also provide the most security.

Could this standard SDK then be a selling point for future ereaders because buyers know that they would have access to a wide range of applications rather than having to wait for enthusiasts to create them (if indeed they do at all). Is this possible?

Jellby · 07-07-2010, 06:56 AM

That sounds like the OpenInkpot project.

mike_bike_kite · 07-07-2010, 09:12 AM

Quote:

Originally Posted by Jellby

That sounds like the OpenInkpot project.

OpenInkpot is an alternative firmware (or operating system) for devices. It was produced because the existing firmware on some devices was quite poor. I don't believe OpenInkpot allows you to create installable applications other than those that are required to view books or images. Also OpenInkpot is usually installed on a few older ereaders and then only by quite adventurous individuals which doesn't translate to a huge market even if OpenInkpot could run applications. In short I'm not suggesting anything like open inkpot

The current market leaders of ereaders are selling their devices as cheaply as possible at the moment with the aim of recouping profits through book sales - allowing users to install a different firmware like OpenInkpot would loose them future ebook sales so it just won't happen. All this means that OpenInkpot is interesting but it's unlikely to be the way forward.

The idea I'm suggesting of a standard SDK wouldn't harm sales but would instead make their ereaders look more attractive as users can run more applications. Users would benefit because they get a wider choice of applications (if they want them). Developers could also spend more time on producing interesting applications because they know they can sell to a wider market. Win-win-win.

fjtorres · 07-07-2010, 09:16 AM

Pocketbook Global is using this approach to competitive advantage. Seems to be working for them.

The main reason you don't see much movement in this direction (especially across vendors) is that ebook readers are *not* PDAs or webpads or slow computers. That is not why they sell. And the future evolution of the category, if it is to survive long term, is by specializing and optimizing, not by trying to be something else. The future of ebook readers is in going cheap and small, not in adding non-reading features.

Cheap, in particular, means minimizing complexity, both at the hardware level (single-chip readers are coming and soon) and at the software level. Especially the latter because the more sophisticated and more complex the software, the less predictable the interactions.

What you are proposing *is* happening, however; just not to eInk readers. Instead, there is a good chance that WebPads will standardize on Android. Whether this is good or bad depends on what your opinion is of Android and Java but it is going to happen.

So, essentially, the part of the market that wants a small cheap multifunction Tablet will go with a webpad and the associated app catalog and the part of the market that wants an optimized reader device will go with hard-wired eink readers. The middle ground is going to be a very narrow market; its doubtful the added sales will offset the cost of supporting and maintaining the app environment. In other words: the reader market will resemble the DMP market; hardwired pure music players at the low-end and PDA-like pocket computers at the high-end with no significant middle ground.

I'm guessing that by the time somebody cooks up a robust "universal" platform and SDK for eink readers there will be no market left for it to address.

07-07-2010, 05:11 AM	#1
mike_bike_kite Digitally confused Posts: 500 Karma: 1500000 Join Date: Mar 2010 Location: London, UK Device: KPW, K2i, Nexus 7 32gb, Kobo Mini	Standard SDK across all ereaders? Ereaders are just slow computers with even slower screens. Some ereaders have a Software Development Kit (SDK) that allows developers to create applications for them. The small issue for developers at the moment is that if you develop an application for say Pocketbook then this application will only run on Pocketbook devices and you'll have a very limited market. Is there no possibility of having a standard SDK across all platforms that would allow the same program to be run on all ereaders? Sure devices differ but most are Linux based and all have pretty much the same choice of inputs whether it's a keyboard, a touch screen or perhaps just a 5 way controller. Screen sizes also differ from 5" to 11" with additional options for landscape and portrait modes but the program just needs to know the X,Y dimensions of the current screen. So providing a standard Java interface should be straightforward and it would also provide the most security. Could this standard SDK then be a selling point for future ereaders because buyers know that they would have access to a wide range of applications rather than having to wait for enthusiasts to create them (if indeed they do at all). Is this possible?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SDK available	hakim	HanLin eBook	25	09-10-2011 04:17 PM
Que ProReader SDK?	chr	Deals and Resources (No Self-Promotion or Affiliate Links)	0	02-12-2010 12:34 AM
SDK ?	KimJ	PocketBook	1	01-01-2010 01:04 PM
Is there really no SDK for eReaders out there? Other ideas?	TechScout_SF	Lounge	7	04-16-2008 07:00 AM
SDK?	foo	Gen3 Developer's Corner	18	12-27-2007 11:01 AM

07-07-2010, 06:56 AM	#2
Jellby frumious Bandersnatch Posts: 7,546 Karma: 19001583 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	That sounds like the OpenInkpot project.

07-07-2010, 09:16 AM	#4
fjtorres Grand Sorcerer Posts: 11,732 Karma: 128354696 Join Date: May 2009 Location: 26 kly from Sgr A* Device: T100TA,PW2,PRS-T1,KT,FireHD 8.9,K2, PB360,BeBook One,Axim51v,TC1000	Pocketbook Global is using this approach to competitive advantage. Seems to be working for them. The main reason you don't see much movement in this direction (especially across vendors) is that ebook readers are not PDAs or webpads or slow computers. That is not why they sell. And the future evolution of the category, if it is to survive long term, is by specializing and optimizing, not by trying to be something else. The future of ebook readers is in going cheap and small, not in adding non-reading features. Cheap, in particular, means minimizing complexity, both at the hardware level (single-chip readers are coming and soon) and at the software level. Especially the latter because the more sophisticated and more complex the software, the less predictable the interactions. What you are proposing is happening, however; just not to eInk readers. Instead, there is a good chance that WebPads will standardize on Android. Whether this is good or bad depends on what your opinion is of Android and Java but it is going to happen. So, essentially, the part of the market that wants a small cheap multifunction Tablet will go with a webpad and the associated app catalog and the part of the market that wants an optimized reader device will go with hard-wired eink readers. The middle ground is going to be a very narrow market; its doubtful the added sales will offset the cost of supporting and maintaining the app environment. In other words: the reader market will resemble the DMP market; hardwired pure music players at the low-end and PDA-like pocket computers at the high-end with no significant middle ground. I'm guessing that by the time somebody cooks up a robust "universal" platform and SDK for eink readers there will be no market left for it to address.

Advert