LunarLincolnLunarLincolnLunarLincolnLunarLincoln
  • Home
  • Process
  • Services
  • Work
  • Writing
  • About
  • Contact
  • Home
  • Process
  • Services
  • Work
  • Writing
  • About
  • Contact
Apr
19

Let it go – Building a real MVP

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

In Startupland, the most valuable product is the Minimum Viable Product (MVP). Why? Because you didn’t blow your entire budget/savings getting there.

People often come in and start throwing this term around “MVP”. Requesting something along the lines of:  iOS and Android apps, a web portal, and a full dashboard for all users and grandma! Oh and an admin portal with state of the art features as well.

This is not an MVP. This is your wish list. Your nice to have list. Your 2 years in list.

“But…but… I NEED to have these things or I won’t be successful.” you say.

Hogwash. Success is based on building the RIGHT thing. Not ALL the things. I know it’s exciting to start building but slow your roll!

While it’s not too hard to trim an initial feature list down by pairing some low hanging fruit, oftentimes you’re still not at your target budget. You may need to drastically slash costs to get to market or not get there at all. At this point we’re not talking about removing 2 questions from the signup page or changing out how fancy search is, we’re talking about removing entire areas or better yet – entire platforms. 

Prove your business model before investing in it in multiple tech stacks.

Do you rrrrreally need that admin portal for your 25 users?  Can you hold off on Android to see if what you have in iOS is really what users want? Do users really need to have both web and mobile access?

 

What should I cut when I don’t want to let go?

1. Assess features & users to find platform launch targets

Where are your users hanging out? Are they older? Younger? Are they turning to the web for this service? Is this something they need on the go? Assess your audience and the core features of your product to determine whether this is a web or mobile play to start (you can add more entry points later! This isn’t forever!)

2. Sweat Equity for Behind the Scenes

Even the great and powerful OZ understood the value of manual effort.

Do you really need all the management stuff automated? Weigh your time versus your cost of development. Is hiring a $10 an hour intern to review applicant profiles cheaper than building a machine learning service? Can you keep track and manage payments with excel and quickbooks instead of a custom point of sale system? Only upgrade/build your tools when the workload demands it not before.

3. Tech debt can be your friend (in the beginning)

Don’t polish and deeply invest in a feature if it isn’t proven yet. High traffic areas can be improved upon once their value is clear. What if you spend half your budget on a feature that when launched collects cobwebs from your so-called target audience? Make pivoting painless with lightweight development decisions.

 

Infinite runway? A budget as deep as the Grand Canyon? You may not have the make these hard choices, but I would still advise you to do so. It’s healthier for a product to be able to grow based on real world user experience. Give yourself the flexibility to change features and change messaging without having to visit 6 different codebases and remove 8 months of work. A simple product launch isn’t easy or straightforward, but it’s a smart one to start with.

Still having a hard time slimming your MVP? We’re here to help! We love creating products that built for success and don’t have a problem saying no (or strongly judging you for not being able to say no to yourself).

Need someone to question all your decisions and make helpful suggestions?

 


Oct
31

A Brand New Android Studio – 3.0!

  • Posted By : Travis Smith/
  • 0 comments /
  • Under : Coding

There are few events in life that give developers such bliss and excitement as when their favorite tools receive a healthy refresher. Earlier this week the kind and hard-working folks over at Google released the official version of their long-awaited upgrade to Android Studio. It wasn’t an unusually long wait (Google seems to release new major versions roughly every 6 months), but the anticipation of diving into its new features has kept me watching Android Studio’s Stable Channel for months.

In the events leading up to Google I/O in May, the Android Studio team had teased the community with some incredible new features for Android Studio 2.4. Many developers, myself included, had our collective fingers crossed for a surprise release at the event and were shocked when Google announced official support for Kotlin in Android development. Additionally, they boldly nixed the 2.4 version of Android Studio from existence, bumped to a clean version 3.0, and continued pushing out numerous betas and release candidates. Now, many moons later, we’re blessed with a well-tested and feature-packed development environment ready for production use.

Without any further ado, let’s talk about some of those new features.

Kotlin

A few years ago, Kotlin burst onto the Android scene and was met with both praise and skepticism. JVM languages like Kotlin aren’t uncommon and most aren’t well suited for Android development (with the notable exception of Groovy, which Gradle uses). However, continued Kotlin development attracted more and more followers. Plugins were made for Android Studio and soon Kotlin became a common concept for cutting edge developers. Google must have been keeping its eye on Kotlin as well, and for the first time in Android’s history, Google announced full first-party support for another programming language to sit alongside Java (ignoring the NDK, since Google most certainly does!). Kotlin’s concise syntax shares similarity with numerous other languages, notable Swift, Apple’s preferred iOS and Mac OS development language. It addresses numerous Java shortcomings such as null safety, a lack of class extension functions, and easy threading support via coroutines. The full list of Kotlin features is long and you can read about them here!

Java

On the topic of languages, Java got some love this time around as well. For a multitude of reasons, Android’s Java doesn’t always have the same functionality as the base language. One of the most common criticisms of Java is its verbosity, especially with anonymous classes. You know, the ones you make to implement callback interfaces like View.OnClickListener. Java introduced support for lambda expressions, which are essentially abbreviated functions to reduce repetitive boilerplate code, in Java 8. However, Android struggled to provide support for lambda expressions; you had to use the experimental (okay, buggy) Jack toolchain or the 3rd party Retrolambda library. Finally, Android developers can use natively-supported lambda expressions. This is a huge plus for libraries like RxJava which rely on numerous single-method interfaces, making them prime candidates for lambda expressions and drastically reducing code length.

 

Android Studio

The last new piece I’ll talk about is an upgrade to Android Studio itself. For as long as I can remember, I’ve been using the Android Device Monitor to profile the performance of my apps. It was a little ugly and a little hard to use, but it got the job done. Google used its magic and transformed it into the Android Profiler. Earning a proud place next to the Build and Stop buttons, the Android Profiler button opens CPU, memory, and network monitors right within the Android Studio window and sits nicely next to Logcat and your other bottom toolbar menus. You can monitor performance, view payload information, find laggy parts of your apps, admire the very pretty interface this amazing suite sits within, and more. I’m eagerly looking forward to testing my apps and improving my code using these upgraded profiling tools.

I could go on but instead you should go download the new version of Android Studio yourself and play around!


Mar
22

Mobile Madness – The Indie Experts

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

The initial results are in and the winners are: Steve Ballmer, Steve Jobs, Jony Ive and Felix Kraus. Here is your updated Bracket.

[separator type=”” size=”” icon=””]

On to the second bracket of Mobile Madness 2016 with a continuation of the people that contribute to the mobile landscape. Some of these indie darlings have made the jump to the big leagues but for the rest, they soldier on one awesome book, blog post, or tweet at a time.

First up: Master Makers

Ayah Bdeir vs Limor Fried

Ayah Bdeir is the founder and CEO of Little Bits everyone’s favorite snap and play electronics toys. We’ve been geeking over the space kit for a while now and constantly suggest these as a great intro-to-electronics. Limor Fried is the founder of Adafruit the one-stop shop for all the whosits and whatsits to make your maker-dreams come true. Adafruit materials power our christmas tree and gif tv (really!).

littlebits-Ayah-Bdeir_37757

maxresdefault

So who build better tools for the builders? Big builders? Little builders? Answer the twitter poll here

[separator type=”” size=”” icon=””]

Second Bracket: All things Swift 

Natasha Murashev vs Erica Sadun

Natasha Murashev more commonly known as Natasha the Robot is everywhere all at once with her talks, advice, and tutorials on all things iOS. She’s been a key figure in brining Swift to the masses, including help organize the try! Swift conference. Meanwhile, Erica Sadun has been a major contributor when it comes to Apple’s latest language, Swift. While her skills with Swift are only matched by her wit, according to the Swift Evolution project, she has by far the highest number of accepted pull requests. You can be sure her ideas are not taken lightly in Cupertino.

Both are rocking it with the new Swift language and have build a massive following for their questions, comments, and observations.


OFRHu0o9

32688

 

Who is the true education maven? Answer the twitter poll here

[separator type=”” size=”” icon=””]

Third Bracket: All things Android

Jake Wharton vs Roman Nurik

Jake thrust himself into the spotlight with his incredibly famous open source Android libraries such as ActionBarSherlock and NineOldAndroids, as well as his contributions to Square’s massive catalogue of open source libraries such as Butterknife and Retrofit. He continues to deliver enlightening talks and presentations about Android and its continued evolution as a platform. While also an experienced developer, Roman is most famous for his work with the UX aspect of Android development. As one of Google’s most popular designers, Roman helped bring the beauty of Material Design to the Android world. He has also crafted a collection of open source libraries focusing on improving user interactivity and experience with your Android projects.


imgres

unnamed

Answer the twitter poll here

[separator type=”” size=”” icon=””]

Fourth Bracket: iOS

Jake Marsh and Mattt Thompson

When it comes to iOS developers, Mattt with three Ts is virtually a household name. His brain children AFNetworking and NSHipster are still widely used and respected to this day. Go check out his other projects too for a host of other useful libraries and services. When it comes to the best tutorials in the shortest amount of time, Jake Marsh is your guy. His little bites of cocoa has become an overnight success, and is a great place to learn fun new iOS tricks that can be used in every day development. Both these guys have made their mark when it comes to contributing to the development community.

Answer the twitter poll here


Mashable-User-Pic_400x400

5333c08eae9005dd7a8cdd478202c818_400x400

 


Mar
21

Mobile Madness – The Brains

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

We are going to kick off Mobile Madness 2016 with our first bracket of tech luminaries. We are going to cover some heavy hitters like Steve Jobs and Bill Gates as well as some industry innovators like Ray Wenderlich and Felix Krause.

First up: CEOs who inherited empires

Steve Ballmer vs Tim Cook

Ballmer_Cook

In one corner we have Steve Ballmer, CEO of Microsoft from 2000 to 2014. Steve is known for his…passion for software as well as his ownership of the LA Clippers.

[responsive_video link=”https://www.youtube.com/watch?v=e8M6S8EKbnU”]

In the other corner we have Tim Cook, current CEO of Apple and …fan of Pharell’s Happy

timcook

Apparently we’re not the first to make the comparison:

NYTimes: Why Tim Cook is like Steve Ballmer
Forbes: Will Tim Cook be the next Steve Ballmer?
Yahoo: Is Tim Cook the new Steve Ballmer?

However we are the first to pit them head to head. Who will be victorious? Answer the twitter poll here

[separator type=”” size=”” icon=””]

Second Bracket: Famous Founders

Bill Gates vs Steve Jobs

Bill Gates and Steve Jobs are each half of wonder duos that made modern personal computing what it is today. PC versus Mac. Generous genius versus design-centric demigod?

steve-jobs-vs-bill-gates-mac-vs-pc

Which world do you back? Answer the twitter poll here

[separator type=”” size=”” icon=””]

Third Bracket: Mobile CDOs

Jony Ive vs Matias Duarte

The men behind modern UI patterns and design. Jony Ivs has led the Apple Design-Revolution. While Matias Duarte has spearheaded Material Design – Google’s attempt to fold the diverse android platform under one unified design theory.


static1.squarespace

Matias

Has Jony Ive lost his magic “intimate” touch with the recent launch cycles? Will Google ever solve their massive design/product fragmentation issues? Who is the better design-guru? Answer the twitter poll here

[separator type=”” size=”” icon=””]

Fourth Bracket: Tools and Teaching

Felix Krause and Ray Wenderlich

We snuck these guys in here as innovators each in their own way. Felix Krause is the brain behind the recent Fastlane Tools, which we recently sang the praises of at a local Cocoaheads meeting. Ray Wenderlich is the king of iOS tutorials and guides.


maxresdefault

ray-wenderlich-tutorial-videos

 

Both are contributing to the developer experience without being the head of some mega-corp. (But who is doing it better?) Answer the twitter poll here

 

 


Feb
04

From office noob to Android czar – Building a League of Legends App

  • Posted By : Travis Smith/
  • 0 comments /
  • Under : App Advice, Coding

[message_box type=”info”] This week we have a guest post from LunarLincoln developer Travis Smith. He spent 2015 working on a side project which he finally shipped (yay, shipping!) and we wanted him to give us a breakdown of his initial foray into indie development. Enjoy! [/message_box]

Sometimes it’s hard being the only Android user in a shop full of mobile developers.  You’d expect nearly equal representation as Android currently dominates global markets, but alas, mistakes do happen (yes, mistakes). However, a positive consequence of this misfortune is the compelling urge to prove Android is the superior operating system. And what better a way to do that than to become an expert Android developer.

chart-ww-smartphone-os-market-share

Android’s Lollipop OS was released around the start of my development journey and alongside it the beautiful style guide known as Material Design. Coupled with the release of numerous support and design library features, I knew I wanted to create something awesome both as practice and for fun.

giphy-2In addition to being the only Android user in the office, I’m also the biggest video game nerd. My favorite these days is League of Legends, arguably the most popular PC video game in the world. And luckily for me, Riot Games, released a beta version of their public API just a few years ago. Being no stranger to the Riot API (I rigged up an automated system to pull in millions of game records for statical purposes back in early 2014), I knew I wanted to push both my skills and the API to their limits. But where to start? There were already a handful of League of Legends apps in the Play Store and some had hundreds of thousands of downloads.

What was a problem in League of Legends that hadn’t yet been solved?

Friends. All of the existing apps I found made it easy to drown yourself in data and statistics about any player you wanted. However, none of them made it easy to see how your friends were doing, or whether they’re actively playing a game at the moment you’re using the app. Additionally, all of the existing apps were designed before the advent of Material Design.

I could see in my mind what I wanted:

  • A name. I chose League Buddy. It’s simple, a little corny, not violating any copyrights, and unused. Works for me.
  • The home screen should be a list, or maybe cards, of summoners.  I could show their names, their profile pictures, and when they last played a game (or if they were in game that moment!)
  • A Floating Action Button at the bottom could present a popup of some sort that allows users to add new summoners to their list
  • A single swipe to refresh could update the entire list at once and let me know immediately if my buddies were playing without me
  • Tapping a summoner should do… well, something. I hadn’t figured out exactly what I wanted here yet. Maybe show some in-depth detail about the summoner?

Simple, right?

Time to learn some new tricks.

Around the time I started, Android released its ‘upgrade’ to ListView, the RecyclerView, and encouraged developers to stop using the ActionBar and instead use the new more generic Toolbar, which would prove very useful in implementing a core Material Design feature. I had my first screen laid out in my mind, but I still had a few questions.

  • What are the best practices with Activities and Fragments?
  • Does the Toolbar belong to the Activity or the Fragment?
  • What about the Floating Action Button?
  • What if I want to support multi-pane on landscape tablets? How should landscape look in general?

I spent so much time researching everything about best practices that I actually discouraged myself for a few weeks. Eventually I realized that the only way I was going to really learn what worked and what didn’t was by trying my best and fixing my mistakes.

giphy

Since I knew I only had one screen in mind, I decided to put multi-pane support on the back burner. However, I did prepare for the future and opted to implement my layout inside a Fragment (which was really just containing a RecyclerView) and put that Fragment in my Activity along with the Toolbar and Floating Action Button. Back then, I was using a library for the Floating Action Button since there wasn’t an official widget (yet). I created a small view that would slide up from the bottom when the button was pressed and that view allowed users to input a summoner’s name along with the region of the server they played on. For example, I play on the NA (North America) server, but there are about a dozen servers across the globe and I wanted my app to support them all.

unnamedNow I needed some way to persist data. On a previous project at work I had used Sugar ORM as a wrapper on a SQLite database. It worked well but I wanted to try something new. I came across a brand new tool called Realm which touted itself as being incredibly fast. Though still in beta and lacking some features (including null support and subclassing entities), I decided to give it a go.
All that was left was to set up the actual connection to Riot’s servers. Writing an API wrapper was easy, especially since most of my code from my previous Riot API project was up-to-date. I used Retrofit to talk to Riot’s server and Picasso to display profile pictures. After a few nights of work, I had accomplished my goal – an app that showed a list of summoners, with a button to add new people, and the ability to refresh the list. It was crude, not too pretty, and lacked lots of key features (like deleting summoners from the list), but it worked.

And then I stopped working on the project for a few months. Work picked up and summer meant vacations, so I halted progress.

But then, Android released some neat new tools that inspired me to resume development!

The first was an official Floating Action Button. The second was a new view called the CoordinatorLayout which allowed the Toolbar to hide as the list below it scrolled down. Last was a NavigationView class which made implementing a Material-themed navigation drawer incredibly simple.

Implementing the CoordinatorLayout proved to be very challenging. I had placed a view at the bottom of my fragment that indicated the last time the data had been refreshed, and this was throwing off the scrolling of the fragment. Despite aligning the view at the bottom and the RecyclingView above it, the scrolling did not work properly. Somebody else had filed a bug report about this exact issue and fortunately somebody had devised a workaround. However, now that the Toolbar slid out of view when scrolling my summoners list, I couldn’t imagine how multi-pane support would work at this point. My second screen was scheduled to be a scrolling list of cards containing tidbits of high-level information about a summoner, and having two scrolling views under one Toolbar would be very unwieldy for a user if that Toolbar was also sliding.

The next hurdle was the Floating Action Button. Now that Android had an official widget which directly related to the CoordinatorLayout (the button would hide on scrolling), I knew I had to replace it. However, I disliked my current implementation of adding a new summoner. A messaging app called GroupMe provided some much needed inspiration. When tapping their Floating Action Button, the button expanded outward until it filled a small rectangle. I loved it and had to have it. As it turns out, this animation is called a circular reveal animation (surprise!). Android had incorporated a utility class for performing this exact animation, but it was limited to devices running Lollipop or newer (which was a very paltry 10% around this time). Fortunately I found a library that provided the exact needed functionality to my app.

unnamed-1Along the way I encountered a new pattern I had never seen before: the event bus. While I’m still torn today over its fit as a best practice, I decided to integrate Otto into my app to help with loading and passing data. In hindsight, I regret this decision a bit, as it led to some poor coding practices and tangled dependencies. As practice, I also decided to upgrade all of my API calls to return RxJava Observables, as functional reactive programming is something I’m becoming more and more interested in.

Creating the summoner overview cards screen was fairly easy. The card styles were adapted from official examples and look very clean. I was able to use a StaggeredGridLayoutManager to allow different orientations and screen sizes to show different numbers of cards side-by-side. Because of switching to using RxJava Observables, loading all of the necessary data (since none of this data is persisted) was easy. I threw together a quick Settings screen which let users change their default region (which will be automatically selected when prompted to add a new summoner) as well as their preferred language (which all Riot data will be automatically translated to).

After a brief QA round across different devices and SDK versions, I had a working, ready app. With one problem.

Riot’s development API key is severely rate limited. To get a production level key, I’d need to get them to approve my app. And to do that, I had to follow their rules. The first rule is that no client-facing application can have the API key embedded in its code. This meant I needed a server to act as a middleman between my app and the Riot servers to append my API key and return the data. The second hurdle was that I needed a website to showcase my app and provide screenshots, FAQ, etc. I took my meager bit of Node.js and Express knowledge and pieced together a very small server application which would cache results for a few minutes and return the data to my app. I hosted this on DigitalOcean, struggled to get a free SSL certificate, and eventually got it working. I purchased the domain leaguebuddyapp.com and worked with Jennifer to set up a very simple one-page website (which is almost done, I swear!).

200

(^Jennifers reaction to this statement)

I was ready to publish.

Presenting, League Buddy! It’s small, it’s nowhere near finished, it’s got some kinks, but it’s mine. I’ve got tons of ideas for future expansions to the app. A wiki page with data on every champion and item in the game, a statistics section that lets you compare yourself to your friends (or even professional LoL players, if you dare!), and tons more cards on the summoner overview screen. Not to mention all the detailed pages for nearly every card! I’m going to be busy for a very long time.

leageulegends

 

Despite the incredibly long blog post, this doesn’t cover even half of the sometimes silly and often frustrating problems I encountered on this journey. But I feel it was completely worth it.

I’ve exposed myself to so many new communities, picked up so many new skills, successfully learned which patterns I like and which I don’t, and ultimately shown I’m capable of creating an entire application from scratch, including its server and web components. It was fun, challenging, and awesome. With 2016 under way and my routine back to normal, I’m hoping I can commit a little bit of time each week to cranking out some new features.

In the meantime, check out my app and let me know what you think! I’m open to all criticism and suggestions for improvement.

And I should offer thanks to the entire LunarLincoln team for putting up with my rambles and questions over the last year about this hobby project. Even though they’re not exactly Android fanboys and girls, they’re all brilliant and offered tons of great suggestions. I’m immensely thankful for their help and looking forward to using my new skills on upcoming Android projects.


Sep
11

Design Inspiration

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

200-2Any strong project first begins with a strong set of tools. Tool #1: Your brain – filled with all those ideas, images, and skills. But my second set of tools in the digital design world are links. What? Yep. Links. Links to great articles. Links to great inspiration. Links to great resources. Below I’ve grouped some of my all-star links into the categories that compose the beginning stages of a design project. The basic building blocks if you will. Enjoy.

[separator type=”” size=”” icon=””]

Patterns and Arrangementsui2

And by patterns I don’t mean background visual patterns like this or this, but user patterns. Should the fields have background? Should “forgot password” appear at the top or the bottom? Can I put 10 icons in the navigation bar (please don’t)? The most important question – What is the difference between iOS and Android in UI design?

 

search_3Animations

An animation adds polish, delight, and energy to your app. More than just a spinning circle, an animation can make using an app a memorable experience instead of a series of colored squares you tap your finger on.

Some great resource for animations: Capptivate.co and UIGifs.com

 

Screen Shot 2015-07-28 at 11.41.23 AMColors/Pairing

Do you want the app bright or dark? Medium blue or bright blue? But not corporate blue. Not ocean blue. You know a “bluey-blue”…
(╯°□°)╯︵ ┻━┻)

When you find yourself having this sort of conversation – hold the presses and go here: Kuler or here ColourLovers or here Coolors.

 

Landing-TeaserStyle

You can take all three of the above categories and still build drastically different apps when you implement a “style“. Do you want modern and sleek? Bright and playful? Traditional and trustworthy? Each style elicits a different combination and selection of colors, textures, and placement. I like to get an overall idea of stylistic choices from the parents of design aggregation: Dribbble and Pinterest.


That rounds out my link-tastic high-level run down of starting a design process.
Go forth and make beautiful and wonderful things!

200


Nov
14

One Design to Rule Them All – Android’s Material Design

  • Posted By : Jennifer Bennett/
  • 0 comments /
  • Under : Coding, Design

Google has debuted a new style guide for their recent OS – Lollipop. It is called Material Design and the internet is BLOWING UP with articles about this new guide. Well we’re about to jump on this bandwagon too and explain why this is such a big deal.

dogdoorThe #1 problem Android has had since its creation is also it’s own selling point. Diversity. Many different phone manufacturers made many different phones and added their own “takes”, if you will, on the Android interface. Free market! Do what you want! Anything goes!

That sounds great, right? Right!?!

One person’s “diversity” is another persons “market fragmentation”. Alot of ugly, bloated, inconsistent interfaces were made. There are over 4,000 different phones to potentially design for! Every company wants to add their own bizarro system apps. See below:

verizonbloatware

Look at all that bloatware – plus Verizon – you’re using three different icon styles. wtf.

So, after almost a decade of Android phones – Google has taken a stand on their ever growing phone market.

Enter: Material Design.

So is this just a new, shiny band-aid on a giant over-designed problem? Actually – Google has done a wonderful job.

materialdesign

It incorporates the growing trend for flat design, but most importantly, it clearly and thoroughly addresses gestures, touch, and movement. As screens become larger, interactions are critical. Consistency across devices allow users to feel knowledgable and comfortable with ALL Android devices. Moving menu buttons or changing the direction screens swipe is the equivalent to putting your wallet in the wrong pocket. It’s just wrong, and leaves the user feeling disoriented.

Fortunately Material Design sets best-practices for all aspects of Android design and development. Google is already implementing it across all of their wide-reaching features – setting the example for others. I’m excited to see developers and manufacturers begin implementing these changes and can’t wait for a newer, cleaner Android (that doesn’t require me to root my phone). It’s beeeeyutiful.

beautiful

Will this be a game changer for iOS design snobs? Open software outside of Apple’s restrictive app store PLUS beautiful interfaces? We’ll see.

e665z

PS. Wiley (who worships at the foot of the golden apple) believes I am being too optimistic about this new design spec. Rebuttal article is forthcoming.

PPS. Travis is very excited about the new elevation feature (DROP SHADOWS ZOMG) – (But I agree!!! Putting things underneath other things – what a novel idea).


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