One of the first ones would be this.....
To put it simply. The app would behave primarily as a content browser.
- Can be branded / perhaps display banner ads
- Multi lingual
- Browser would display content dynamically from a backend server, most
likely via XML feed. (perhaps SSL encrypted)
- Most graphics would naturally be built in.
- Preview possibility for audio content, but securely so that it can not
be easily stolen
- Ability to order / purchase - download - install/set as ringtone or
wallpaper etc... from within the app. (purchase/payment control is
handled on the backend server)
- If needed, launch the native wap/web browser
- As small footprint as possible
We actually did have app very much like this written in java, but the
biggest problem there are the phones themselves. Key mappings vary
between countries / phone models / phone manufacturers. Another drawback
with the app was that it needed a windows executable to work as a proxy.
(STOOOPED thing!!!!, whomever decided/created that monstrosity.) + I
have no access to the source code.
Usage:
A customer or Operator installs the app in the phone. After launching
the application, they should be able to choose between the content
types. Then browse available content in each type. Each content type
also have categories, which the user may choose to use to limit the
selection. Search function lets them further make finding the desired
content easier. Eventually if a desired content was found, the purchase
and acquisition of the content should be as effortless as possible.
Perhaps like only hitting a "buy" button.
Some of the background activity:
The program should be able to send some information about the phone, as
eventually there will be multiple different android based devices
available. Also it is important to know the phone number of the
customer..... If this can not be automatically detected, then a
customer should be able to input it via configuration or something
similar. (Some sort of verification process is needed if customer has to
input the number by themselves.)
Eventually there may be many others, as the original ideas mature....
Petri
Dennis J Harrison Jr wrote:
> Petri, care to share a use case for your app?
>
> I might be able to help out.
>
> On Sat, Dec 6, 2008 at 11:00 PM, Petri Laihonen <pietu@weblizards.net> wrote:
>
>> For android, probably the first app would be a brandable multi-lingual
>> client which would interface with my content platform.
>> While not in possible here in US (Due to shitty mobile operators), but
>> in other countries also place orders directly from the client.
>>
>> Another project I have been dreaming on, I already referenced about in
>> my earlier post.... To have SMPP client system running in Linux box.
>> With this one I don't care about what language it was made with as much
>> as the functionality it would have.
>>
>> A friend of mine, whom also praises Python over many other languages, is
>> currently looking into some open source options for SMPP client. He just
>> happens to be quite busy at the end of the semester due to his studies
>> of robotics and such....
>>
>> Petri
>>
>>
>> Dennis J Harrison Jr wrote:
>>
>>> I would be happy to help you grok python(1). Or really, anything for
>>> that matter.
>>>
>>> There are plenty of ways to get your app running in android. What
>>> types of apps are you looking to dev?
>>>
>>>
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 12/07/08
This archive was generated by hypermail 2.2.0 : 12/19/08 EST