Excellent point with regard to placing priority on "dumbphone" and
based solutions ahead of those that require more costly voice/data
The basic outline you've provided is great, and I can think of a
possible added features/tweaks offhand.
At this point, considering how much discussion there has been of
in getting our message directly to the public and facilitation of
intra- + inter-Occupy communications, I'd say a basic phone tree &
VM-to-email setup is a definite need. A regularly updated info
even toll free?) for each Occupy would reach a lot of people that
have or aren't in the habit of using portable data services as
On Sat, Nov 12, 2011 at 5:27 PM, <firstname.lastname@example.org> wrote:
The reach into mobile is critical, however we caution you
leading with smartphones, a strategy which will tend to exclude
those without the economic means to buy the devices / plans -
those without the time or personal freedom to participate in OWS
events in - person. That would tend to disadvantage those most
need of the tool, we think.
We would instead recommend a mobile roadmap that starts from the
most widely available, data plan-friendly, and interoperable
Universal Dumbphone Solution:
1) Voice Portal: we are developing a prototype of a voice portal
system for #Occupy* as part of our Peoples' PBX project. We
done an initial use case/system mockup here:
Another alternative is SMS, though reliable & performative
tend to be have high variable costs relative to the cost to the
host of serving voice or a low-bandwidth xHTML site to users
entry-level data plans.
High End Feature Phone Solution (eg. Brew Devices):
2) xHTML Web Site: since ~2007, if a device supports mobile Web,
supports ~xHTML 1.0(ish).
3) Webkit (/ HTML5-ish) lowest common denominator Site (cross-
smartphone solution: iOS, Android, RIM, W7, Palm...)
4) Hybrid Application: using the Webkit core site, develop
app shells for iOS, Android, RIM, etc as needed; majority of app
simply renders Webkit views, 'shell' takes advantage of native
capabilities like local storage, notifications, add'l security,
voting client, etc.
Even over time as the mobile sln gets more refined, we believe
use cases / features will still more logically live in the
weight, more easily updated & maintained, & independent of
update Web hybrid zone.
As mentioned we are already working the voice portal concept in
We would be willing to contribute to systems design, UX,
potentially server space & even devices. We may also be able to
rally a few folks to get their hands dirty code-wise but no
We hope you'll consider a modest / incremental / mass approach
this - given who #Occupy* claims to be & represent, we at
think it's very important to place extraordinary priority
to those users most impacted by the greed and oppression we have
united to combat.
yours in solidarity,
On Fri, 11 Nov 2011 23:27:38 -0800 Matthew Lepacek
Tech ops is currently seeking mobile platform developers to
development of such an application. There is a wealth of ideas
of implentation available but a first step is collecting actual
resources so we can determine a platform for development, with
creating one framework-product that will work on most
android/iphone/blackberry devices. After we have gathered a
development-programmer resources we will conveign a series of
hash out the best platform solution. After a universal
we can engage in the idea exchange of features and advisories.
The goal at
this time is not to change a single thing about GA process, but
compliment it 1:1 for our beta app.
I'm attaching an example concept mock-up of a system proposed
professional voting keypads at a cost of $13/ea. We are
system of a few commercial audience polling systems from
enjoy-ars.com, powervote.com, and clickapad.com but we are
develop our own unique smartphone solution using WIFI for the
Part of this smartphone platform is ensuring that we have
for everyone to participate, which will involve donations of
smartphones from the public. Our hope is that the publics
be suplimented by donations from manufacturers/retailers.
a compatible smartphone will be able to use it, but whose who
not--we wil make them readily available. At this time there is
discussion as to whether this will be adopted by the GA, we
present the option and develop it with the hopes of it being
There are no guarantees.
Anyone who has experience developing mobile applications please
On Wed, Oct 26, 2011 at 2:06 AM, Naqeeb Memon
I would like to propose that we build an iOS / Android app
Occupy Wall St (OWS) to be directly connected to the people
the movement. Facebook is a great tool but a Facebook Post /
have the same reach as an app installed on a user's phone and
lost in the stream. Please review and provide any
1. Allow Users to follow/participate in OWS events in
prospective cities. We will begin with NY and expand to
2. Notify Users of the next OWS planned protest through
3. Notify OWS of arrests during the protest. The user
be able to
report an individual arrest or their own arrest
4. Allow OWS to share latest updates/content/requests with
their prospective cities.
1. Reach out to the Media Work Group to get their feedback
2. Prototype iOS / Android functionality and look and feel
3. Find developers
Ows_solutions mailing list