Anatomy of a Mobile App


My name is Gal Oppenheimer. I’m a Product
Manager at raw engineering, the company behind built.io. Today we’re going to talk about
the anatomy of a mobile application. The first thing to think about when you’re building
your application is what you want to build. You probably have an idea, like, an app for
dog lovers, or a new take on music discovery. You want to take that idea and hone it down
the origin. Figure out the purpose of your application, what the problem is, and what
you’re trying to solve. Once you’re figured this out, you want to build the process that
the user goes through. Things like logging in, account management, sign up, how they
bring their friends in, what they do. So you want to build every screen your application
will have and figure out all the ways they connect with one and other. This is called
wireframing. Once you’ve finished the wireframing process, you know exactly what your application
will do, and it’s time to identify what features your application will need. You application
might need things like push notifications, user management, analytics, integration, all
kinds of things like that that most mobile applications need. Once you’ve figured this
out, you have an idea, you know how you’re going to follow that idea, you know what you
need, and it’s time to figure out what platforms you want to target. We recommend starting
with either iOS or Android, but if you think you’re going to want to target both, you may
want to build an HTML5 application. Overall, what you’ve just created is the user experience
for your application. You know what your problem is, how you’re solving it, the specifics of
how you’re application will function and solve the issue, what platforms you want to target,
and what you’ll need to target those platforms. Your application is actually split into two
parts. There’s the frontend and the backend. The frontend is what your end user interacts
with on their phone; the backend sits in the cloud and powers your application. It has
features like push notifications, analytics, user management, all your login functionality,
and more. There are some things you have to think about for both the frontend and the
backend. On the frontend, are you going to build it natively,or are you going to build
it in HTML5? Are you going to each application custom per platform? So first focus on iOS
or Android, then the other platform, and then build it separately for every other platform
you’re targeting, or are you going to use a tool like Xamarin or AppGyver to build your
application? On the backend, there are a few things to consider, as well. You already know
what functionality your app needs from the wireframing stage. You next need to decide
if you’re going to build your platform and your backend from scratch, or if you’re going
to use an existing one. We’ve developed built.io, but there are also many other platforms, such
as Firebase and Parse. We personally recommend using an existing backend. When you build
a backend from scratch, you often spend months just working on your backend, and then by
the time you’re ready to get started building your application, the market may have changed,
someone else may build your application, you might already run out of money. When you use
an existing backend as a service, you’re able to get started building your application immediately
and have a prototype done in just a few weeks. Want to learn more about built.io? Get started
by creating an account at built.io/signup then check out the documentation and developer
community. If you have any questions, shoot an email to [email protected] Thank you, have
a great day!

Leave a Reply

Your email address will not be published. Required fields are marked *