LunarLincolnLunarLincolnLunarLincolnLunarLincoln
  • Home
  • Process
  • Services
  • Work
  • Writing
  • About
  • Contact
  • Home
  • Process
  • Services
  • Work
  • Writing
  • About
  • Contact
Sep
26

Initial Questions for a New Mobile App Project

  • Posted By : LunarLincoln/
  • 0 comments /
  • Under : App Advice, Business

It can be daunting to know the first place to start after you know you want to build a mobile app. We are here to help. We can help you focus in your project goals on what makes sense.

Ultimately only you will be able to provide the core vision for what you need. As you ask the questions below, think through the lens of what needs to be in front of users first.

Let’s Build a Minimum Viable Product

Minimum Viable Product

Source: Kunal Naik

Since building technology costs money, having priorities will save you money. So what are the priorities? As we explore this question, keep in mind that it’s always smart to build a minimum viable product (MVP) first. Rather than having a little of everything that works ok, focus on building one aspect of your vision well so that it’s a great foundation. That may mean focusing on one platform before doing both iOS and Android. It may mean we should focus on core functionality before adding extra features.

Have an idea of what’s a must-have versus things that aren’t crucial. This will help you know what you should invest in first. It’s always better to get a smaller, great product in front of users, rather than an app that has more, but doesn’t work great. Having an MVP also helps you get to market faster, which has huge advantages. If you keep launching major updates to your app every 6 months, you’ll be learning what works and what doesn’t. This saves you money since you know which ways you need to pivot your thinking. It often doesn’t make sense to work on a large app for years, without getting feedback from users along the way.

That’s the critical piece of advice I’d give any of my friends who are involved in getting an app built. Keep in mind you’re building a MVP, and not the kitchen sink when considering the questions below. Here are some common questions we get when people reach out for a quote. This should help prepare you for a conversation with us.

Let’s Play Common Questions Bingo

If we wanted to build a Bingo board with the common questions that come up during a conversation about building an app, we’d be winning lots of Bingo. If you don’t know how to answer the questions below, spend some time thinking it over and reach out if you’re stuck. We can point you in the right direction.

You want to know: “How much will it cost?”

We need to know the answer to some of the questions below before we’re able to answer this one for you. In general apps are expensive to build, and zeros are involved. Thankfully a round number can get more focused as we learn more.

So what will we ask to get to the answer for that question?

What’s the big idea?

What makes this app unique and different? What will compel people to use it? What is that one thing that absolutely needs to come across when someone uses this thing?

What kind of features are you envisioning?

What are the core thing someone can do with your app? It can be helpful to see if you can distill your app in 2-3 user stories. A user story is a high-level description of one of the things a user can do with your app. Here are few examples:

  • As a car driver I can swipe my app while paying for gas to earn rewards.
  • At the gas station, I can show my app to redeem rewards at the counter and get a free Coke.
  • As a beer enthusiast I can scan a beer’s barcode to see details about a beer.
  • As a movie buff, I can search for a movie and mark it as watched.

Does this need to be an app?

Hang with me. Sometimes people will have an app idea that may not lend itself to the app format. If you want to build an app for writers that helps them build up their typing speed, it may work better as a website or desktop app, where people are more likely to have a keyboard when using it. What’s the advantage to people having this product on the go?

Who is this app for?

What’s your target demographic? Who will be using this app? This can help decide how the user interface works.

How do you plan to make money with this app?

This may sound a big harsh, but what’s the business plan? If you haven’t considered the longterm plan for how the app makes you money or meets your goal, you may be missing a core feature that needs to be in the app.

What’s the play? Should users be able to subscribe monthly to the app? Are there in-app purchases? Are there ads or messages from you or partners? How does a user give you valuable information such as their email address so you can reach out and tell them about your next rally for saving the rainforest? Does your app help you reach your goals?

Do you have a specific timeline in mind?

Do you have time pressures tied to your app? For instance, are you building an app that helps you create custom emojis that you’d like to release on the same week that the next Emoji Movie releases? Or do you have investors or stakeholders with expectations on when the app will be rolled out?

Based on the timeline, we may recommend what would be doable within your desired time window.

What other apps are your competition?

This question helps in a couple ways. Are you building an app that already exists? If so, what is your competitive advantage? If you’re building something different or better than someone else, how will that inform the features you’re wanting?

If you do have competition, what do they do that you also want to do? One advantage to not being the first on the scene, is that you don’t have to re-invent the wheel. You can likely glean from others what is already working in your space.

How fleshed out is the design?

Do you need a designer? Or is everything already mocked up? If you need some help with the ideation phase, we can help figure out a plan. Knowing how far along you are in this step will inform how long the process may take.

What devices will be able to run your app?

On what devices will your app be able to run? Can it only run on iPhones? Or just on Android phones? Both? What about tablets? Should the app look different for users using larger screen sizes? The answers to these questions greatly impact what needs to be built.

What other technology will accompany the app?

  • Do you also need a website?
  • Does an API need be built so that the app can access the data it needs?
  • Do you need an interface that allows you to edit or see user details?
  • Do you need analytics about the app so you can see reports of how people are using it?

Bingo!

If you have the answer to 5 of these you’re off to a great start. Keep going. If you don’t have all the answers, that’s totally fine. We can help you think through all of the questions above. These are just some introductory questions we often cover so we can start to figure out the size of your project.

Reach out when you’re ready to figure out your app’s next steps!


Feb
15

2015 State of the Union

  • Posted By : Jennifer Bennett/
  • 0 comments /
  • Under : Business, Coding
Clients, Crew Members, Friends, Family, and Fellow Americans: welcome to LunarLincoln’s State of the Union address.

What a difference a year makes. What an incredible rollercoaster ride. We experienced so many highs last year, and we rode out the lows knowing that they were necessary to gain the momentum needed to reach the next peak.

Halfway through 2014, Wiley, Travis, and I (Jennifer) had just joined forces and were working out of a windowless 100 sq ft office attempting to pretend that we knew how this “running a company” thing works while writing code. Here we are taking a group photo and bemoaning moving out of our first office:

IMG_5157 

B5P80yEIgAEUvGf

Since then, we’ve said hello to new team members Todd, Ben, Patrick, and Jack. And then said goodbye again to Todd as he headed off to the big Apple (Cupertino, not NYC).


guysmural  

cityhousedinner


We moved into a palatial residence (bigger than our own house) and we began what has become a pretty impressive collection of moon AND Lincoln memorabilia.

TheOfficePano

But lets get to the interesting stuff:
Code. Apps. Creating Things. Amazing Clients.

We’ve worked on so many interesting projects. Some we can shout from the rooftops and some we can’t. Some of those we can talk about are on our snazzy new portfolio section of the website – go look at it, its beeeyutiful.

Cool things we got to learn more about last year
  • Complicated algorithms for fuzzy, health-based logic
  • GPS tracking and payment systems for the local shuttle revolution
  • Building the world’s most innovative and challenging UI controller
  • Optimizing an app to be energy efficient while constantly running in the background and logging a user’s location
  • Writing algorithms to clean up data given to us by Apple’s sensors
  • Crunching enormous amounts of data into usable insights
  • Magic cards!
  • Streaming video from face cameras
  • Leveraging the JIRA REST API
  • Maintaining native SDKs and their associated APIs
  • Creating a wicked fast PDF renderer to display PDFs in a customized way
  • Making progress at a reasonable rate on legacy codebases
  • Syncing audio output between multiple devices
  • White-labeling
  • Apps to test apps
  • Apps to ship apps
  • Things that aren’t apps but are in fact websites. (We can do them now, but still hate front-end development)
  • Swift!
Items we shipped publicly (mmm, yes shipping)
  • Compass (Beta)
  • Guestbook for Emma
  • Metric for Emma 1.2 for iOS and Android
  • Expo
  • Joyride Backend
  • Joyride Customer for iOS and Android
  • Joyride Driver for iOS and Android
  • Band in Hand 3.0
  • TappedOut for Android and iOS
  • StyleBlueprint 1.3 for iOS
  • Playmaker CRM for Android
  • XOEye for iOS
  • LoLo 2.0 for iOS and LoLo for Android

We volunteered a ton. We pulled all-nighters at hackathons. We explained how pocket computers work to high schoolers. We gave talks to our fellow developers and also exchanged heated words at usergroup cage matches.

  • Vandyhacks – Building Epic $*&%^
  • East Highschool Magnet – What does it take to build apps?
  • CocoaHeads – Creating Custom Views
  • Nashville Mobile Usergroup – Native versus Cross Platform Cage Match


12087275_1005315902852421_2662332177277726035_o

22962232300_c8e64b8d79_o 

We made a ton of new friends at events around town and across the country

  • Sponsoring Creative Mornings & Nashville CocoaHeads
  • Going to SF for Quantified Self Conference and pitching our hearts out
  • Becoming a finalist for the Nashville Next Awards!!!
  • Watching Expo compete at Pandoland with an app we built for them

giphy-2

We did a bad job podcasting. We did a better job making our internal processes even stronger. And we’re building things for ourselves.

  • Finally finishing our own internal CI/CD system
  • Building a reporting platform to augment our JIRA instance
  • Starting on some products of our own (more details on that coming soon)
  • What happened to NSVille? (Ask @microchip128 & @ianbroyles to get back on the wagon)

 

It was a good year. Based on everything above – I’m not sure how we’re alive, but I can’t wait to do it all over again.

200-2

Love, love, love (and code),
Jennifer (and the guys) (and Abe)


May
06

A Fever of Painting

  • Posted By : Jennifer Bennett/
  • 0 comments /
  • Under : Business

You may have noticed a few sliiiight changes around here. Like a totally new website, an intern, some new business cards, and….drumroll please, we’re moving beyond the home office to a legit office (that may actually be smaller than our home one, but at least it’s not 5 feet from the rest of the living quarters).

LunarLincoln 2.0 peoples. The past few months have been absolutely breakneck. When people speak of famine or feast in small businesses, it’s been all feast over here. So much feasting. No more, not even a little wafer please. We are looking for some help, we are ready to grow, and man it’s exciting – if not a little nerve wrecking.

We spent the last few weeks touring various offices about town. There was a lot of goldilocks impressions going on “too old” “too big” “too hard to reach, sheesh return my call, worst office manager ever”. But we finally found the “just right”. Or at least just right – for now. We’ll see what the future holds.

So office-search-2014 finally over, last weekend we got in there to paint. Wiley was coming down from a fever which he promptly gave to me and we both had what sounded like the plague. So we painted in an unwindowed, 125 sq ft space, completely out of our minds on fumes, dayquil, and exhaustion. And did I mention we didn’t get enough paint? Yeaaaaaah. Maybe we should stick to our desk jobs – it’s more our forte.

It’s a great start to a new adventure. We’ll keep you posted on future developments. For now, I’ll just leave you with this:


Recent Posts
  • Copious Communication
  • Initial Questions for a New Mobile App Project
  • Gif TV: A LunarLincoln Product
  • Onboarding other peoples code
  • What’s in a name?
  • Don’t build it all. Picking a Platform.
  • Talk to your Users
  • Design for Fat Fingers
  • A new look
  • Hourglass for Jira
Archives
  • May 2021
  • September 2020
  • November 2019
  • October 2019
  • June 2019
  • April 2019
  • February 2019
  • January 2019
  • October 2018
  • August 2018
  • June 2018
  • April 2018
  • January 2018
  • October 2017
  • August 2017
  • June 2017
  • February 2017
  • January 2017
  • September 2016
  • July 2016
  • April 2016
  • March 2016
  • February 2016
  • October 2015
  • September 2015
  • July 2015
  • May 2015
  • February 2015
  • December 2014
  • November 2014
  • September 2014
  • May 2014
  • April 2014
  • January 2014
  • December 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • December 2010
Categories
  • Agency
  • App Advice
  • Branding
  • Business
  • Business
  • CaseCollage
  • Coding
  • Design
  • Design
  • NSVille
  • Uncategorized
  • Web Design
Copyright LunarLincoln 2023. All Rights Reserved