- To provide a stable and user friendly commercial open source Linux based PDA that can be used by a teenager, but scale for the enterprise. - If a teenager can't use it then the Enterprise wont want to put it in the hands of the fourteen year old in the stock room.
- Have the ability to fit in only 8MB Flash and run in 16MB RAM. - It is easy to expand something, but hard to shrink.
- The primary goal of the project is to be fast, small/stable, and bugfree. (Rather then to be built cheaply/fast) The reason for this is that the applications will run on devices that should not need to be updated.
- Applications should either be a single file/module or file/directory based (palm and OSX respectively), any other choice will cause you pain and dollars in tech support. This allows for easy moving to memory cards, transfer to friends, transfer to another device (irda), transfer to desktop all without installing or having the application have to know about the file system. Also they can be removed without worring about left over files.
- Custom ROMS - With maybe nothing more then a different "Walmart" logo, but there is money to be made here.
- Building Custom Applications - With custom roms come custom applications.
- VPN Intigrated/module - Security always wins points.
- Java Solution - Must be buzzword compliant and let manager take advantage of those cheap undergrads and proclaim JAVA is the one true...oh never mind.
- Jabber - Instant communication using an open protocol that can be secured and wont change or go away three months into your product lunch.
- Application Certification Program - Not meant to be a money maker, but just help recover some of the cost and at the same time improving the quality of the applications running on your device/platform. Some ideas include:
- Check over an applications install/uninstall
- Check name description, for inconsistencies etc and possible better
- Run Valengrind for memory leaks
- If source if provided check over for possible improvements.
- Unique device ID or some other common method for commercial applications to prevent piracy as much as possible. - Shows that you are there to help the developer.
- Host commercial applications. - Provide the hosting for their application so every developer doesn't have to re-invent the wheels while providing a common portale for your users.
- Developers can buy views for their certified application as the homepage's "Featured application".
- Buy/Download applications online and automaticly sync. The package manager can and must be able to buy apps online. The ability for users to just click, ten seconds later the application is installed and their credit card is billed $5 with no hassle. This is a marketing wet dream that is not difficult to impliment.
- Web based agenda sync (for example: http://chronoss.sourceforge.net/)
- Backup PIM data and or all data remotely via Jabber.
- Provide a pda web portal like: http://mobile.yahoo.com/home
- Provide service similar to ziproxy. ziproxy is a forwarding (non-caching) proxy that gzips text and HTML files, and reduces the size of images by converting them to low quality JPEGs.
- PDA applications could be nativly compiled for the desktop side so users could try them for free and then buy them for their pda.
- Open API. There is no reason for the sync software to be proprietary. You sell hardware and services on that hardware NOT sync software! An open api will allow for plugins to sync to palm/outlook/kmail/etc.
- Outlook of course
- Copy the data via any means (ftp, scp, Samba, nfs, jabber etc )
- 2.4.2X And 2.6.X
- On boot using lpp (or similar) to have a "pretty" active user experience that doesn't seem to hang
- Well written GPL'd drivers in the official kernel (Audio, usb, IR, touch screen etc)
- Ability to scale the CPU speed as needed
- USBIO, USBNET, WIFI, IRDA, and serial for connectivity.
- Driver for a VGA CF out is one of those nice things that no one uses, but everyone shows off.
- Ability to boot VERY quickly so it can be shutdown to save power when not used for X amount of time. (Possible even suspend/resume to disk if fast enough)
- Easy to install a new ROM by the user. (One and only one click!)
- With so many very small fast webservers out there there are too many uses begging to be be taken advantage of. Perhaps Displaying the users vCard and any public Docs, allow login to see addressbook/calendar for printing from the desktop webbrowser. Spending ten minutes a hundred ideas could easily be created.
- Finger server - Present what is on the/a specific todo list.
- Multi user - Applications should never crash the system.
- Some sort of factory reset available to users (Union FS with cram fs and jff)
- Windowing system: X11/kfb (both?) I can't decide because I have never seen hard numbers on this. How much memory they use and how long it takes to start are two principle numbers that need to be discovered before a decision can be made. Unless you have real comprehensive numbers on this any e-mails concerning this will be promptly deleted.
- If X11 is used then fun things like:
- Easy Remote Login & Audio
- Easy Remote Application Launch/Running
- Easy way to show applications on desktop side.
- Clean good small fonts are a must.
- GCC 3.X with prelink to help reduce those startup times. Maybe even use uclibc.
- Uses Debian for easy portability and reuse of precompiled and packaged applications along with large number of applications that work together and will have future updates - Customers care where you will be in five years, but Debian will never go away.
- Application launcher should be modular to allow for other designs from the community.
- Launcher has a built in Today screen that is updated (from the db? xml files? other?).
- If using Qt or QtE a mini-kde library should be created allowing for much quicker KDE cross porting. They have plenty of really good classes and there is no reason to not take advantage of them. Along the same lines an open communication should be forged with KDE (or whomever) to help share ideas.
- A clean simple widget theme similar to PocketPC which uses the screen space very well.
- Palm got it right, the "Hardware Pulldown" button that slides menu up/down from off screen should be present. It saves screen space and is just all around good.
- They should talk to each other via a database. For such things as a recuring todo list item that is spawned from the calander saying it is someone's birthday and to buy a present.
- An OPEN API - Is your business only about selling some pim software? If not then open the api and reap the rewards.
- The source for these applications should be open so that other can help improve them. (Note I didn't say GPL)
- Application must be able to link to each other.
- Floating appointments.
- This pim list could go on forever. Just copy DateBK4, they got it right.
In the event that you aren't sure what applications you need for your device here is a small list: