will the apps running on Android or iOS be expecting to communicate with the "hub" in JSON over RESTful URLs?

If JSON is a standard for REST I don't know, but both ends *can be made* to communicate with anything you want. JSON is convenient (except that you must url-encode it and you send binary data only as base64-et-al). Surely Perl backend can convert a JSON to a Perl data structure very easily. And vice versa. The client-app will coerce you to using a library for converting that JSON to objects (for example Gson) but you don't have to as you can have it converted to polymorphic hashtables. So, yes JSON is convenient on both sides. And an app, from personal experience, gains greatly by RESTing with JSON. I found Retrofit library useful for communicating with a server. If you are programming the app, your biggest problem will be placing all data requests using asynchronous logic. And that leads you to RxJava (for example). And that's some learning curve. Alternatively, you have a WebView component. Basically a browser inside your app, just a shortcut with lots of deadends.

In reply to Re: Web application framework and Smartphone apps by bliako
in thread Web application framework and Smartphone apps by monx663

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.