“Don’t miss a party”

Is this year moto. Last year we had more than 8000 downloads in just five days of SXSW Interactive. This year app is ready for a prime time and even better than last years.

• >250 parties listed
• Directions and RSVP buttons
• Selected (“Hot”) events of our choice for each day
• Drinkups, film premieres or label showcases, the list grows by the day.
• Detailed event descriptions let you know more about the event or its sponsors and much more.

On top of this we will run a blog inside an app that will announce hottest parties for each day and also will have a wrap-up of previous nights with latest buzz, photos and videos. .

If you’re one of many with a hectic schedule, leave the rest to the Austin Party Guide, your personal party-planner.

Available for Download Now!

Be the one to confidently lead your team to the next event. Be the one who’s first in line and first to the bar. Be the one who buys ShoutEm their first drink… kidding, kidding, but seriously…

Download the Austin Party Guide today!

Austin Party Guide – iTunes

Austin Party Guide – Android Market

The post ShoutEm “Austin Party Guide 2013″ App for SXSW appeared first on ShoutEm - Mobile App Creator - Make App.

• Responsive Web Design (RWD)
• Separate HTML5/JS app (mobile web app, running on m. domain)

Let’s see what the advantages and disadvantages are for each approach. I did quite a bit of research around RWD over the last couple of months, talked to ton of people from the industry, developers, web designers and what I found was very interesting. It turned out that there is no clear winner and that it really depends on the circumstances. Some are very excited about RWD as a “one shot to kill them all” solution and will go through the effort of redesigning website with new approach, but a the same time others are concerned with the costs of redesigning a site and also see an advantage in a separate mobile solution as a way to provide different, more tailored experience on mobile/touch screens.

Quick note, before we move on. Responsive Web Design (RWD) is the phrase that is used to describe the approach of making a site look great on multiple screens – but at its core both approaches actually use responsive design techniques. HTML5/JS app will for example use it to adapt UI to different Android devices, iPhone4/iPhone5 screens or to rotate between landscape and portrait.

What are the fundamental differences?

RWD approach of redesigning your web from scratch is picking quite some buzz lately and due to fact that it is pretty much standard HTML/CSS technology, which is widely adopted and easy-to-master technology, it is gaining popularity among web developers? At the same time some are betting on HTML5/JS technology with hope that it soon should be able to provide an experience almost identical to that of a native app.  It requires little bit deeper knowledge of client side programming in frameworks like Sencha or JQuery and is more popular amongst native app developers that are looking for cross-platform solutions.

To understand the benefits and drawback of both, we need to understand the fundamental architectural differences for each technology.

As you can see right from the picture away biggest drawback of RWD is that it sends more data to the device than it ideally should. Biggest drawback of HTML5/JS app is that it needs a powerful device that can run Javascript code effectively. But there are some big advantages of each approach, too.

How RWD works

RWD technology is identical to technology that is used all over the web with difference being of requiring a little more effort in writing CSS and using responsive HTML layouts. By simplifying the website layout and using smarter CSS it is possible to dynamically adapt the page layout to different screen sizes. Most of the work is done with CSS, everything else is the same old web technology that we are already familiar with. When the user clicks a link to a new page or hits the back button, the browser will load the new HTML page from the server. In most cases the browser does not save any context or data locally between requests. It is possible to improve experience even further by adding snippets of Javascript for popup menus, photo galeries or similar more used elements in order to improve UX.

Advantages of RWD:

• Single website version to maintain. This is most likely the biggest advantage of this approach. Once redesigned there is only one version of the website that you have to maintain.
• Simple technology. RWD can be done by most web programmers, requiring just a little better CSS coding skills.

Disadvantages of RWD:

• Requires a redesign of your website. In order to implement RWD on a website we have to use a simple adaptive website layout and that usually requires going trough major redesign of existing web site.
• Full page load and larger amount of data through slow mobile networks. The amount of data exchanged between the client and server in each page load request is much greater for RWD than one of a native app and than inevitably slows down the performances and downgrades user experience when compared to a native app which app-spoiled mobile users might do.

Example:

Great example is TheNextWeb.com website. By using a simplified site structure they easily adapt the site to multiple screen sizes. I guess for them it was an easy decision to go with complete redesign of the site from scratch and showcase the latest technology since it looks like tech blogs are anyway going trough design quite frequently.

Currently RWD seems like a great quick fix for the problem of different screen sizes and is definitely a big step forward from the lousy mobile themes that we have had for the last few years. The question is if  fast growing mobile traffic will force us to further improve UX on touch screens and if that is only achievable by using more touch screen specific Javascript libraries on clients and basically again end up with almost separate HTML5/JS mobile app. Where is the border?

How HTML5/JS app work?

So let’s take a look at the alternative. HTML5/JS app will usually run on m.yourdomain.com or touch.yourdomain.com. In general client/server architecture level HTML5/JS app is no different from native iOS or Android app. Most of the native apps that run on a client (mobile phone) side are communicating with the server through dedicated API that serves raw data. All the logic behind how the app works is implemented in Javascript code that runs on a client in a browser. HTML5 is rendered on the client; the app uses local storage to store its state and data. When the user is navigating through the app, with the right combination of Javascript/HTML5/CSS we can achieve the native app user experience – smooth screen transitions, preloading the data, animations, touch and swipe gestures – everything that those amazing devices have to offer.

Advantages of HTML5/JS

• Getting closer to native app experience. With HTML5/JS you can get very close to the user experience of a native app. Recently Sencha implemented Facebook app in pure HTML5/JS and showed  that it is possible to get performances at the same level as one of the native app. iPhone and Android phone users are spoiled for choice with the number of awesome apps that can run on their devices and they might appreciate a similar experience on a browser so long as sharing, linking and other functionality still works – and there is no reason why it should not.
• No changes to existing web site. Enabling HTML5/JS app on your site is completely separate from your desktop site. Usually your existing web site will redirect users to mobile/app version of the site which as above mentioned in that case can be 100% optimized for touch screen device.

Disadvantage of HTML5/JS

• Two different solutions to maintain. You end up with two different solutions for desktop users and mobile users. This probably sounds like a little bit of overhead, but it does open up the possibility of perfecting the user experience on each platforms separately.
• Technology that is harder to develop. It will take pretty much the same skills as for development of native apps to develop great HTML5/JS app, so it all depends if you are going for less work and a compromise or you are willing to put more effort into your mobile platform and provide best possible user experience for touch screens.

Flagship HTML5/JS app example:

Financial Times. Even after more than a year and a half, this is still a state-of-the-art HTML5 app. And it is still a big buzz among publishers where some are trying to copy that approach . The reasons for not going with native were more related to the fact that iTunes wants to take 30% of all subscriptions sold trough native apps – but anyway they made it look and work great and are able to offer an pretty good, app like experience on tablets and smartphones in a mobile browser.

My verdict

I would say RWD is a great solution for a current state of the market with mobile traffic between 15%-40% and in a long term might work perfect for a simpler content based sites. But when mobile traffic grows to the point of 50-60% or for sites where engagement is No1. metric we will need to optimize experience for high end touch screen devices further than RWD will ever be able to do. It is proven that faster slicker apps are more user engaging and if is all about that only way to stay competitive will be to provide best possible user experience. Politicly correct answer is that there will be market for both for a long time.

How do you see those two technologies compared?

The post Going mobile? Responsive Web Design (RWD) vs HTML5 app approach. appeared first on ShoutEm - Mobile App Creator - Make App.

Each new year offers new ways to latch onto emerging trends and start a business anew, or revamp your existing strategy.  For upstart app creators looking to take advantage of opportunities afforded by more devices in hands than ever, the issue many face is a vision that encompasses every opportunity possible. Vertical markets, oft-shortened as “verticals”, can help hone your focus when considering app creation as a business, saving you time and ultimately increasing your profitability.

Identifying verticals that will work for you

It’s important to separate cost-effective verticals in your app creation strategy from the types that have prohibitive entry-points. Some examples of verticals that require top-tier expertise, and in turn the monetary consideration to provide the necessary components, are rather obvious:

• Finance/banking
• Hospitals/health
• Insurance/pharmacies

Some verticals, although the idea may seem lofty, lend themselves to great opportunities with a bit of outside-the-box thinking:

• Local Government/Politics
• Schools/Academics
• Publishers/Content Producers

If you break down their individual moving parts, you can find needs to fill for their mobile presence. Break down local government into its individual candidates by creating apps for those seeking office or re-election. School athletics apps are a great way to provide advertising potential, keeping a vested interest in your community as a whole. Publishers are looking for new ways to promote authors individually, as well as upcoming book releases. These examples are where the difference between vertical and niche marketing becomes apparent.

Assessing local needs

Diversification of clientele is useful strategy to bolster opportunities in a local setting. Understanding the needs of your community or local businesses can edge you ahead of potential competition, especially as adoption of a mobile first strategy is relatively unfamiliar to most small business. Choose two or three areas, share with potential clients the importance of user engagement to help create return-business, and you’ve already paved the way for additional work in those verticals down the road.

• Beauty/Lifestyle (Salons, Spas, Hair)
• Events/Conferences/Exhibition
• Hospitality/Food & Beverage
• Contractors/Architects/Interior Design
• Retail
• Religious/Faith-based

There’s a reason why these verticals are a good fit to focus on, as they offer great value to your community and will expand your local network quickly.

A safe start

The importance of diversification is best summed up by the adage “don’t put your eggs in one basket”. Far too many mobile projects have started solely to replicate the success, and sometimes the exact experience of another single app which has far more market share currently than you’ll likely see. Why claw your way up the first rungs of an endless ladder when you can scale a few verticals at your own pace? When you find the ladder that’s easiest to climb, it’s a matter of time before you find yourself at the top.

Hopefully, after a year of this experience you’ll walk away with a diversified clientele and more in your coffers. You may choose to add talent to your team, approaching more ambitious projects with matching return potential, or continue to work with multiple clients at an increasing premium. It’s likely that your goal is to be profitable, and by expanding your network through targeted verticals you can have the best of either world down the line.

The post Think Vertical When Creating a Mobile Business Strategy appeared first on ShoutEm - Mobile App Creator - Make App.

On behalf of the entire ShoutEm team, we’d like to wish you a very Happy New Year in 2013!

Your support in 2012 allowed us to make quite a few positive changes, offering the most responsive and robust apps around, and your continued feedback helped us shape our vision for the coming year. Here are a few things you can expect in the coming months:

• In-app notification center – Your in-app social activity, including likes, comments on your statuses and more, will be easier to follow.
• E-commerce – Build a mobile app for your web shop, expanding your earning potential.
• More detailed statistics – We’re making it easier to track user engagement with user statistics, deal usage and location-based statistics and more.
• REST API – Our JSON-based API will provide an interface for client developers to interact with content stored on ShoutEm, allowing you to build new applications on top of the ShoutEm infrastructure.

More devices are in hands than ever before, and the new year brings fresh opportunities to create apps for clients or anyone who has a need. If you’re looking for new business opportunities, we highly suggest considering becoming a part of our Agency program in 2013.

If you’re on the fence about whether or not a “Mobile First” strategy is important this coming year, check out this piece by our CEO, Viktor Marohnić. Very simply, think of which device you spend a majority of your time interacting with. In that context it makes more sense than ever to have a mobile presence.

May 2013 bring nothing but success and good health to you and yours. We’ll see you on the other side!

The post Here’s to the New Year! appeared first on ShoutEm - Mobile App Creator - Make App.

You think we’ve escaped unscathed just because we’ve all woken up? Maybe the apocalypse is taking one last lunch break, because there’s still time for the world to end.

As a reminder, we’re offering 30% off all new, single-app plan purchases until 23:59PM EST tonight. Your app must be published by December 28th to receive this discount, as we’re counting on the fact that we will indeed live to see another day.

To receive your discounted promo code, email us at shoutem@shoutem.com, or use our handy contact form to request yours.

May humanity live on!

The post 30% off new apps before the world ends! appeared first on ShoutEm - Mobile App Creator - Make App.

Last week, we dove in to our discussion of the App Store approval process by talking about all the little details you might overlook when submitting your app. But we didn’t really delve into the timeline and what the process looks like once your app is officially submitted.

How long does the approval process take?

Although the total time required for the review and approval of applications has varied in recent years, it now takes approximately 8 days (including Saturdays and Sundays). Out of those 8 days, the application will wait for the review for around 7 of them, and once it enters the actual review, it will be approved or rejected within 24 hours in most cases. The twist is if the app gets stuck in the review process for more than 24 hours—that’s usually a clear indicator that something is probably not in accordance with the rules. The reviewer is likely seeking for help from senior staff in order to decide whether the application should be approved or not.

If the application gets rejected, and the reason for the rejection is a simple misunderstanding (e.g., you mention that you support Augmented Reality in the app description, but the reviewer can’t find the feature), the process will continue after you send an email with an additional explanation to Apple. Such a conflict is usually resolved within the next 24 hours, but depending on the complexity of the decision, or how many instances there are, it may even take several days or weeks.

The thing that will definitely set you back in time is if you send a new version of the existing application to the App Store while the old one is still waiting for its review. Then you will definitely be thrown to the back of the queue and you will need to wait an additional 8 days.

Expedited Procedure

The team at Apple is somewhat sympathetic to urgent situations when you can’t wait for the standard approval time of 8 days. If you discover a critical bug, or if you are late with the development of an app for an event, you can send a request for a so-called Expedited Review.

You will be notified by an email whether your request qualifies for the fast procedure or not. If it does, your application will usually be reviewed within 24 hours (sometimes it can take up to three days). Expedited reviews are granted on limited basis and is not advisable to rely on the fact that each request for such review will be accepted.

Filing Complaints

No matter how hard you try, there are situations in which you do everything right, but the application may still be rejected. For example, our application for the famous rapper, 50 Cent, was rejected on the grounds that it did not provide enough value to be released in the App Store. (By the way, this application currently has over 100,000 users and an average rating of 5 stars in the opinion of 300 of them.) Desperate times sometimes call for desperate measures, so in a similar situation, you will have to file a complaint.

Filing a complaint will result in a change of your reviewer. More precisely, you will get a board of reviewers. This committee will consider your comments and review the application much more carefully than during the “normal” process. Being rejected by the App Review Board, means that there is no higher authority that you can continue to appeal to. Some developers, whose appeal was rejected, tried to fight with Apple in the media, but we don’t know any case that ended up with a positive outcome for the developer. Once the decision is made by the board, it’s done.

Conclusion

Although the App Store Review Guidelines ​​helped the consistency of the review process, the fact remains that it’s still dependent on subjective assessment of Apple ‘s reviewers. The good news is that, in our experience, the situations in which applications are being unfairly rejected are extremely rare. And when things get complicated, it’s worth remembering that the folks in Cupertino are people like us. They  might make mistakes sometimes, but they want what our customers and what we want: top-quality software and a mobile application that is a pleasure to use.

The post Acing the App Store Approval, Part 2: In the Waiting Line appeared first on ShoutEm - Mobile App Creator - Make App.

I think it could happen that iPhone might quickly start loosing its advantage over Android. To be clear at the moment I see iPhone as a market leader and not buying any of those numbers about iPhone market share vs Android market share as an argument. iPhone is currently wining all important aspects like user engagement, AppStore revenue, quality of apps, amount of money that developers are making etc, etc…

Here are few reasons why this might change:

1. Hardware advantage is disappearing

For years Apple was ahead everyone else when it comes to hardware, most of the Android devices looked cheap and unpolished, definitely not something that you wanted to use with joy or to impress your friends.

But for example new Samsung Galaxy S3 is a different story. It looks very modern and fresh and is a very well done piece of hardware. Nokia Lumia (Win 8, though) is also solid looking device. Those two devices show that it is not just Apple any more that can produce high end hardware. As I discussed in one of my previous blog posts Apple hardware inovations are not that exciting for end users as they used to be few years ago and other hardware manufacturers are quickly catching up.

Think different, yes, but with Android

There is also an angle where iPhone at some point was a cool new device that made you look different. It was statement. I’m not sure if that is the argument these days. Do you really want to have exactly the same device as everyone else? Where is excitement in that or why would same old, same old iPhone be a topic of discussion while you are sitting at the bar with friends. ‘Social’ advantage of iPhone is gone. Everyone saw it, everyone has it and it is not that cool anymore.

2. Simplicity of iPhone UI is not an advantage any more

When first iPhone got out it was amazing how simple an easy to use it was. Four year old kids were able to use it. Remember all those phones before iPhone and how you had to read the manual to actually start using it. It was terrible. And than came iPhone, with its simple, limited and therefore very easy to use UI. Not sure if that is the advantage any more. Why?

Everyone is a tech geek today

Recently I sat down with my friend who is a medical doctor and always had the cheapest feature phone on him to used it for calls only. He didn’t even use email and still don’t have a Facebook account, he is very different from most people I hang out with. But just few weeks ago he bought new Android phone. All of the sudden he started asking me questions about mobile operating systems, Android vs iOS, Windows, data packages etc. I was shocked him asking me all that stuff and where all of the sudden he came up with all those informations. Also I’ve seen some of my family members that just a year ago opened Facebook accounts, people that were never interested in technology, commenting the acquisition of Instagram and opening up Instagram accounts to check it out. News about the acquisition reached them before they even heard about Instagram from friends. That tells me that technology have gone completely mainstream and absolutely everyone is into it deep.

With above in mind I believe average user is no more satisfied with limited and simple device and UI. They are  ready to take on new, bit more complex UX, more features and flexibility. Android had that angle from start and appealed more to geeks, than ‘normal’ people. So if today everyone is becoming a geek, that might make Android more appealing to the masses than iPhone. Maybe users are ready for home screen widgets, few more hardware buttons, maybe they want to customize their home screen layouts and such.

3. Android is becoming more appealing to developers

High end and more expensive android devices mean users with higher buying power and that means more money for Android developers. Lot of developers got burned in early days of Android and move on to iPhone because they weren’t able to monetize their apps easier. With Google Wallet and Carrier payments that is changing for better. If first two assumptions above are correct than Android is gaining advantage here as well.

iTunes AppStore process is a frustration for most of the developers and it looks like Apple has no plans to back up. Enough said.

Google is committed to HTML5/js technology and time of HTML5 apps is definitely coming. Even if you decide to go native Java language you have much more developers out there that can start coding Java Android apps than ObjectiveC developers.

I even heard from one developer that for them is so much easier to develop and push Android apps live to the Google Play and iterate than doing the same for iPhone, that they decided to do Android first in order to test the UX/UI and fine tune the app, before they publish anything to the AppStore.

What do you think? Android has much bigger market share in numbers but it many peoples eyes (including mine) iPhone is still a leader. How soon we will see Android starting to really threaten and tap into iPhone customer base?

The post 3 things why Android might disrupt iPhone market share appeared first on ShoutEm - Mobile App Creator - Make App.

It’s easy to view apps as a simple commodity in which one app download equals one unit of success. Most app creators approach the process with stars in their eyes, that their app will be the next million download hit. Sorry to say, but there’s a 99% chance that’s not going to happen. It’s important to let this mindset go when building your app or creating strategy, as it allows you to focus on what really matters, user engagement.

App download numbers fall off

The first two weeks your app is in the store is a critical time for acquiring users. This is when most app creators will realistically get a majority of their downloads. If you play your marketing strategy right, you can carry this upswing another month or even two. According to a 2010 Localytics study, one out of every four apps downloaded is never opened. While these numbers may be a bit dated, it’s safe to assume this percentage hasn’t deviated wildly. HTML5 app adoption can be even more difficult if not properly marketed, as you don’t have the power of the traditional channels for users to find your experience.

Simply put, if you attribute success to download counts you’ll end up disappointed in the long run. This is where many app creators decide their app is a failure.

Don’t give up, abandon your investment and call it a day unless you’ve utilized every avenue to engage the user base you’ve built up until this point. There is a point where sustaining and engaging the users who’ve been kind enough to try your app out becomes the key to your app’s success. There is hope, and it’s now time to shift your focus.

Leading by example

Being a part of your own experience is a key strategy to building a bond with your users. If you have social features, be a part of user discussions or start your own and invite others to contribute. Showing faith in your own product by using it actively reflects positively on the experience you’re providing. Use the power of your app’s niche to discover what is truly relevant to your user and find ways to expand on that value. Have you created an app just to have an app, or to solve a problem/provide a solution? If it’s the former, you’re not doing anyone any favors. Your user isn’t just one download, they’re a real person who happens to need, or at bare minimum have a curiosity for what you’re providing them.

If you’re not 100% sure that your users know how to utilize your app or why it’s advantageous to use it, it’s up to you as the creator to offer resources explaining these points. Users truly appreciate guiding materials such as a video walk-through of your app, self-hosted support/FAQ or a prominent email address for questions. This shouldn’t take you more than a day, considering you know your app inside and out. You may learn a thing or two about your app’s user behavior this way, and be able to adjust to needs accordingly.

Utilizing incentive

The most successful apps consistently offer added value to the daily lives of their users. Apps with large built-in networks, such as Facebook, Twitter and Instagram, have inherent return they base on your personal social ties. An app with a smaller user-base needs to find ways to keep users not just in the app, but connecting with its purpose and utilizing the incentive you’ll provide.

There are a multitude of apps that don’t utilize push notification functions for any number of reasons. Given the proven engagement boost this offers app owners, this is a huge mistake. If you are at all reserved that your push notification campaign would be viewed as spam or a nuisance to the user, you don’t have a true campaign in place. We’ve touched on this topic in our previous piece on push.

Although this doesn’t apply to all app-types, Deals and loyalty programs are another proven way to provide a lasting incentive for users. Taking a local tourism, or chamber of commerce-type app as an example, there are endless opportunities to connect local businesses with app owners to benefit the community and keep that business local. If you’re providing your community enough incentive, with minimal effort to discover that incentive, they’re more apt to appreciate the value you’re offering to their daily lives.

Changing your outlook

This type of thinking: the user as a person rather than a single digit, the user as a part of your community (whether it be geographically or tied through common interest), the user as your partner in this venture, makes all the difference going forward.

Sure, you can give up on numbers, but don’t give up on the people who are helping you make your mark.

The post Why App Download Numbers Don’t Matter appeared first on ShoutEm - Mobile App Creator - Make App.

The situation now is much better than in the early years of the App Store, when in the absence of an official review guidelines document, developers relied on sparse and often contradictory pieces of advice found on quasi-professional websites. Although information can be found much more easily these days, we are still seeing a decent number of rejected applications, often because of trivial reasons that could have easily been identified in advance.

Given the hundreds of published applications, there’s probably no team with more experience in the App Store approval process than we are at ShoutEm. We’ve seen everything: The Good, the Bad and the Ugly. It encouraged us to write this blog series about rarely mentioned, but no less important reasons why apps may be rejected and how you can make your apps successful.

The Obvious

Applications must not have bugs (at least the prominent ones), must not crash, or leak memory. The user interface should be developed according to Apple’s Human Interface Guidelines (HIG) and network unavailability should be detected and appropriately displayed to the user. Using an undocumented API method is strictly prohibited.

The Less Obvious

1. Application name

• The name of the application must not be identical or similar to the name of another application that is already in the Store. Also, use of the word “trial” or “beta” in the title is not allowed.
• The name of an iPad app must not be the format “iPad [app name]” or “[app name] iPad”. You are allowed to name the application “[app name] for iPad” (note the “for”), or “[app name] HD” or “[app name] XL”. This implies that “[app name]” is also yours, otherwise your submission will be rejected for violating the first rule above.
• Contrary to popular belief, if you ever decide to change your mind about your app name, you will be able to change it later, even if the application is already in the Store.

2. Application Icon

• If you create an application icon that is too different from its iTunes artwork, Apple will reject it. Of course, no one expects that your icon and artwork must be identical, but they must be similar to one another, use the same branding and a similar color scheme.
• Just note that if you plan to offer a free and paid version of the application (e.g. “lite” and “pro”), icons for these two apps must not be same.

3. Application Description

• The description must report the app’s purpose, as well as its functionality, from the perspective of your customer. Make sure that the description is accurate because the reviewers will check that it really relates to your app’s features!
• Example: if you write that your application contains a video review of the latest action movie, and a reviewer finds an empty list of videos (because you didn’t have time upload one yet) the application will certainly be rejected.
• Description of features or bug fixes for future versions of the app will also be reviewed. In order to reduce the risk of rejection on new app versions, some developers utilize minimal descriptions such as “Minor bug fixes.” Although this description is perfectly legal as far as Apple is concerned, it won’t provide sufficient incentive for many customers to download the new version. It is always better to make your descriptions more attractive and comprehensive.

4. App functionality

Apple doesn’t have anything against non-native applications, i.e. apps that have some or even all of their functionality implemented through a web browser using HTML/JavaScript technology. Gmail is one example of such an app, as is LinkedIn for iPad. However, it often happens that people, who desperately want their own application in the App Store, go with the path of least resistance and submit an app that doesn’t provide any real functionality other than displaying their website. Such applications will certainly be rejected, and the content is probably a better candidate for a mobile-friendly web site than for downloading.

5. In-App Purchases

• Apple takes a 30% cut of any content, functionality, or service sold through your application and does not allow the sale of books, music, articles, additional game levels, or other virtual goods by any other method except the iTunes Store. An application with links such as a “buy” button that leads to a website selling a digital book will be rejected for sure, so it’s best to stay clear of such experiments.
• Understandably, giving away 30% of your earnings may be unacceptable in many business situations. If you don’t want to use in-app purchase for your business, you’re not alone. If you decide not to use iTunes to sell your stuff, the best thing you can do, and still stay within the limits acceptable for Apple, is to set up a message in the application similar to this one: “If you want to buy a subscription, go to our web site.” (Without the link to the site, and without mentioning the web address!)

Like we said at the beginning, there are many different parts to think about, both big and small. And taking care of these sticky points before submission is only half the battle. In Part 2 of our series next week, we’ll fill you in on all the things that can happen after you submit your app for review.

–

Want to know more about the appeal process or expedite review? Read on in Part 2 of this series.

The post Acing the App Store Approval, Part 1: Understanding the Nitty Gritty appeared first on ShoutEm - Mobile App Creator - Make App.

Vibhu got all the points right about why mobile is hard and all the barriers that startup will face if they decide to embrace a Mobile First approach:

• Closing viral loops is hard.
• Onboarding is harder than on web.
• Building your business on mobile is hard.

But he has the game plan all wrong.

It is a mistake to run from these problems, rather than attacking them.

Yes it is hard, but Vibhu forgets that you need to skate to where the puck is going to be. At the end, all this just sounds like another story that fits well in the RWW piece above: another startup that raised millions and all it does now is pivot like crazy. Fred Wilson had some good objections on why this thinking is flawed, and here’s my take on what they are missing:

• If you go web first these days, there is a good chance that a startup which nails it on mobile will put you out of business in next year or two.
• Smartphone penetration is less than 50% in US and below 30% in most of the world. The Web 2.0 revolution only started when Internet penetration went over 60%.
• Most of the publishers we are working with are reporting that their mobile traffic is closing in on 50% much faster than they thought it will.
• Mobile is the place where you can disrupt existing players because they will have hard time fitting their bloated web based software on the small screen
• Moving away from mobile to web is like developing a Windows based software in time when Web 2.0 was taking off and justifying it with the fact that more people have Windows compared to Broadband internet.

We like mobile, not because it is easy, but because it is hard.

We believe solving technical challenges is the way to go. As much as I admire Twitter or Facebook or similar companies, I was never a fan of trying to replicate that model because the risk of failure is much higher. For every success story we have thousands of failures and millions of dollars spent. The challenges are more social than technological. I’m a much bigger fan of companies like Intuit and Salesforce or Squarespace and WordPress, who all developed great technology over many years and keep launching one great product after another, slowly but steadily building great companies.

All those platforms, fragmentation, and the fact that all this is new to most of the people in the IT industry, makes it very hard for them. That is why we are attacking this problem. We believe that taking hard and complex problems and trying to make them disappear for end users is where you can build a long-lasting business and not to be threaten by some new hit service that’s getting all the attention in Silicon Valley and Alley.

By persisting with Mobile First you will see a huge payoff.

Imagine this: Instead of changing strategy on a dime, you’ve raised enough money, stayed on plan, and perfected your product. Then a year or two from now, when mobile dominates Internet traffic, your service will be fine-tuned and primed to go through the roof. And the icing on the cake is that you will be a great target for acquisition from tons of companies that couldn’t or didn’t want to focus on mobile when it was time.

Ten years ago mobile startups were failing because they were too forward thinking. Today that is not the case. It is time to persist.

The post Mobile First: It is time to persist, not pivot. appeared first on ShoutEm - Mobile App Creator - Make App.