linux phone framework

    somebody says:

Applications

- PIM data exchange via OBEX (Hiker Exchange manager?)
- More flexible homescreen and application launcher.
- File manager (in progress, use gpe-filemanager / GnomeVFS)
- Task switcher
- gpe-phonepanel plugin to select and display the ptim input method
- Text input method for devices with numeric keypad
- Camera application
- Control panel (power down, wifi on/off, gsm on/off - maybe profile selection)


Configuration

- connectivity setup and control (GSM, UMTS, Wifi, Bluetooth...)
- audio preferences
- IP network configuration
- screen calibration, backlight control
- time, date and language / locale
- GSM settings
- sounds and eyecandy (ringtones, themes, wallpapers)

The configuration tasks that do system level settings need to be designed for
privilege separation: The UIs should not run as root user while the backends
need to have additional privileges. Considering to use a part of the Hiker
framework that's a must anyway.


Framework

- hotkey configuration (should be a static, system wide configuration)
- event manager, idle detection (button and hardware events, might become part
of application launcher and machined)
- filesystem abstraction to avoid exposing the whole filesystem to users
- application lifecycle management (Hiker)
- use of a unified settings API (Hiker?)
- phoneserver + TAPI improvements (e.g. stability, portability, delivery of dbus
status signals)
- network connectivity management (Maybe based on NetworkManager, we have a
modified one for PDA use somewhere.)
- introduction of security mechanisms
- power management notification and awareness (It might be worth to take a look
at Maemo here.)
- alarm framework (Hiker?)
- evaluate usable theme engines, create at least one decent example theme
(Sapwood theme engine?)