Distributed Web, Part 2 Questions

distributed-pt-2.md

1. What is the difference between native development (iOS, Android, OSX, Windows), websites, and web apps?
2. What are the cost differences?
3. Do you start with web apps always? When would you start with native first?
4. How do you find an agency to build what you want?
5. How do you start the development process right? What should you do beforehand to prepare?

Some randomness around cost:

Native Cost Considerations

• Number of platforms you’d like to support
• How often the OS updates
• How often new devices support the OS (screen size and hardware capabilities)
• Smaller pool of developers / more specialized
• Approval process for certain app stores

Web App Cost Considerations

• Deadlines / size of team
• General scope
• Third-party integrations
• Browser and device support
• Accessibility
• Performance

Native / Websites / Web Apps

Native

When someone refers to a native application, they're talking about a program that runs on the specific operating system utilized by the device. These are items that you’d visit the Apple App Store or Google Play Store to procure. Since they interface directly with the gadget in question, their ability to access device functionality is greatly expanded: you can take photos directly within the Instagram app and receive system notifications via the Facebook app.

Since setups of this variety operate within developer kits provided by each operating system, they typically look similar to other apps on the same device. Managing user expectations for the presentation of items like buttons and tabs can create minor inconsistencies between Twitter on Android and Twitter on iOS, for instance.

Native development can be pricey, depending on your situation. These apps will only function on the intended operating system, meaning that you’d need a separate app to be built for each. Maintenance becomes an issue as well, as you’ll need periodic updates to coincide with new OS version releases.

Websites and Web Apps

The difference between a website and a web application can be confusing--largely because there is no clear distinction. Broadly speaking, a website focuses on delivering read-only content: a restaurant displaying its menu and hours, a consulting firm discussing their expertise, the fan page dedicated to all things David Schwimmer. Businesses can certainly benefit from a website, but these most often fall into the not needed category discussed in our first article.

Web apps typically focus on users logging in and providing content. Think of the web versions of Facebook, Twitter, and that place where your employer requires you to log your time. They're usually much more complex than your standard web site (which translates to more expensive), and trend towards being unique to that product / company. Alongside the price difference, these sorts of projects often require more planning, greater focus on documentation, larger teams, and a longer build time.

Where to Start

Many feel the safe route is starting via web app, and that’s often true--it has the most expansive reach and, depending on featureset, tends to be the cheapest option. In the end, though, it's all about going to your customers. Instagram is probably the most famous app-first example: for nearly two years, users could only access the service via the iOS application.

Prepping / Kickoff

I think Tim’s post took care of this pretty well.

Choosing an Agency

• Pick a group that will challenge you--as the domain expert, the project will function smoothest if you let your consultants consult as the integration expert. Decisions reached cooperatively tend to work best.
• Ensure the agency’s methods and frequency of communication match up to your expectations.
• Price. It’s easy to only look at the values, but take into account the experience behind the price. Often, more experienced software developers charge a higher rate but can deliver more maintainable code in less time.
• Passion. If those tasked to build your application are as excited about it as you, the result is usually better for it.
• Past experience in the same / similar field. For us, this is using the lessons from Code School / Cisco / BAH / etc. when we’re writing up requirements for a new learning platform.