This document discusses the mobile app development of Invokit, a SaaS invoicing software. It describes how Invokit transitioned its web app to being mobile in 6 months using the PhoneGap framework and jQuery Mobile. This allowed them to package the web app as a native mobile app across all platforms using the same codebase. The mobile app saw quick adoption, with 30% of customers using it, and benefits like a 20% increase in leads and international reach.
2. What
is
Invokit
?
Saas
invoicing
so;ware
Invoicing
Contacts
Catalogue
Prices
3. Why
going
mobile
?
• Smartphones
and
users
are
ready
• Real
benefit
for
the
end
user
4. Technology
constraints
Mobile
apps
in
2009
• Low
level
languages
(ObjecIve
C,
Java)
• Developers
in
high
demand
• Complex
app
to
code
• No
real
benefit
from
naIve
5. Technology
evoluIons
PhoneGap
framework
• Open
source
framework
• Package
web
apps
as
naIve
apps
• Same
code
for
all
plaPorms
6. Technology
evoluIons
jQuery
mobile
• Open
source
framework
• Touch
interface
builder
• Easy
to
use
and
deploy
7. Technology
choice
Use
your
API
• Don’t
mess
with
your
core
so;ware
• Improve
your
API
8. Technology
choice
Think
small
• Start
with
core
features
• Focus
on
Ime
to
market
9. App
stores
sales
channel
Android
• Quick
process
–
no
human
validaIon
Apple
• Long
process
(2
weeks
to
1
month)
• Business
model
conflict
10. New
business
model
Separate
mobile
billing
from
web
billing
• Use
in
app
purchases
for
mobile
subs
• 30%
cut
for
stores
editors
11. MarkeIng
benefits
• Free
download
• No
acquisiIon
cost
for
stores
users
• Standalone
mobile
users
• Mobile
users
will
likely
test
the
web
app
12. First
results
• 30%
of
customers
use
the
mobile
app
• 20%
increase
in
leads
generaIon
• Quick
internaIonal
reach
13. Going
further
• Use
phones
naIve
features
(GPS,
camera…)
• Local
storage
(offline
mode)
• Extending
to
new
plaPorms
(RIM,
Windows)