I'd suggested installing Eclipse and follow the Android documentation to get a development environment up and running, this allows testing your apps on a virtual Android device, you can alter the hardware specification and Android version for testing/benchmarking purposes.

As for SL4A, this looks quite interesting, I'll play around with this when I get home this evening. The only problem I can see is that your application will have a much larger filesize than a native JavaApp, which impacts device performance (most people don't have Apps2sd**) and as you say, potential impact on bandwidth use, which may result in a cost.

The FAQ suggests that you can install (pure) Python modules by coping them to the appropriate place, perhaps this is the same for (pure) Perl modules.

Update: Do you have a terminal emulator installed on your phone? You could have a look around to see if cpan is part of the perl packages SL4A downloads.

Update 2: Also, I'd be curious as to know if when publishing a script, what the access permissions will be? The SL4A requirements (essentially wanting full hardware control and access to all your data) may be off putting to end users.

** Note that with most Android builds, applications are installed to the phones internal memory, which reduces the free RAM available to the system. I use Cyanogenmod, which allows me to specify where things get installed to, among other improvements.


In reply to Re: cpan android by marto
in thread cpan android by Boldra

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.