Economy models in iOS apps use In-App purchases become very popular. Lots of developers pick iOS environment because of the flawless payments through iTunes.
If you’re planning to have a monetization model in your app, it has to go through Apple system and you have to use in-app purchases. There is no other way to accept payments from your iOS apps. There are pros and cons of using Apple in-app purchases. I’ll try to explain some of them.
The biggest con is Apple takes 30% of your sale. And another con is, there are difficulties and grayed areas in the integration of in-app purchases to your app and back-end. But the pros make all even. Because delegating whole payments to Apple is gonna affect your sales because Apple makes it so seamless that it reduces all money related steps to only one confirmation box. So it changes the purchase experience and makes it what it supposed to be. Most of the checkout or payment experiences on web, faces lots of drops because of unnecessary and boring steps like putting your credit card info, trying to give the trust to user that you’re a legitimate company and have legitimate payment system that you will not sell their info out or you won’t let hackers to pick your customer info up. All those buying experience changed in iTunes payments. So this is why you should want to integrate in-app purchases. Continue reading “Integration and verification of iOS In-App Purchases”
I dropped my iPad mini this morning, it somehow flipped in my hands, fell and kissed the floor from the back side. I did similar with my MacBook pro 5-6 years ago, just a week after I bought it. That’s the only device I dropped until now.
I am usually very careful with my mobile devices but except this last incident, I never dropped my stuff. I’ve been using my iPhone 5 and I dropped it 3 times in the first week. I got my iPad mini last month and it also is lighter and thinner than they were.
I commute using the subway on a daily basis and I usually read on my iPad, I wasn’t carrying my regular iPad but I started to have the new one almost every day. I use a crowded subway line in the mornings and this morning, I was hustling with the crowd to get in and after I got in, I was stabilizing my position and somehow iPad flipped in my hands and I dropped it. It was between stress moment and playing cool 🙂 Nothing happened anyway.
We used to have heavy devices usually and after last ones, I still couldn’t get used to hold them. But it’s obvious that these lighter and smaller devices tend to fall more easily and often. I see cracked screens everyday. Probably screen replacement become cheaper and easier and there are more companies providing these services, i’m assuming this is the case, even if it isn’t, it will be soon.
You may wanna check these durability videos: http://youtu.be/pMvE0lkunBg and http://youtu.be/T4kBn-GRw1M
I’ve put my efforts on making mfyz.com responsive and mobile compatible last week. After 4 days work, now you are able to access mfyz.com from your tablets and phones (small screen devices).
I’ll write about coding responsive layouts following weeks. There are lots of CSS frameworks that allows you to build responsive layouts but I didn’t use any CSS frameworks when I coded current interface. I could transition to twitter bootstrap but I didn’t see any need to do so. Also the current layout is simple enough to not require any complex structure. Anyway, let’s get back to the subject.
Desktop version (as you can see above) is displayed for 800px and wider screen resolutions. For smaller screens than 800px, interface turns to mobile compatible fluid layout. As you know, fluid layouts are resolution independent because they are fitting the screen they’re in. That’s the reason most of the mobile compatible pages built in fluid layouts.
Tablet devices are usually 800px and wider when they are held landscape, so you will see mfyz.com’s desktop version for landscape orientation on most of the tablets.
Also, most of the tablets have below 800px wide screen resolution for portrait orientation, so the site becomes fluid and mobile compatible version. The mobile compatible version is optimized for better readability and optimized navigation.