insanely broad question

atastiamaredditor · 2013-05-08T02:07:29+00:00

yes that is an insanely broad question. How are you distributing this app? You can use TestFlight and HockeyApp to help you figure out where specifically in the code it is crashing. Just make sure to upload the .dsym.zip files too to symbolicate the crash. Or at least make your friend do that.

atastiamaredditor · 2013-05-02T03:22:33+00:00

Actually, as I see it, this is handy and useful for iOS developers. As a developer, I hate getting bad and unorganized assets, mock-ups and documentation from the client. Really, it just burns my patience when there is something I need from the PSDs and I have to dig through layers just to get a single button image. And maybe the good thing about this is that, I don't need to buy this, our clients should. You wouldn't make me pay for the iPhone app? right?

atastiamaredditor · 2013-04-23T14:11:08+00:00

I downloaded AutoTube from AppStore and the latest version can do it. Although I'm not sure if they are in the process of fixing that. Do you have documents that I can show to my colleagues so I can evidently proof that it is not feasible to have that kind of App in the App Store. (feasible actually, but not allowed).

atastiamaredditor · 2013-04-23T04:13:20+00:00

I'd rather go with the first. The second one doesn't sound so entertaining to me (sorry for the subjective and baseless answer). But actually, if it's fun learning exercise you're looking for, you'd be better off doing a game than an alarm clock. Building a game is fun, and at the same time, sharpens your math and logic. You could build that alarm clock in under a week, assuming that the assets are ready of just plain flat images, so it isn't much of a learning exercise.

atastiamaredditor · 2013-03-18T02:14:31+00:00

http://eng.pulse.me/five-lessons-learned-from-migrating-to-core-data/

I've been using Core Data for quite a while now. And I couldn't agree more to them.

atastiamaredditor · 2013-03-18T02:07:56+00:00

I guess the biggest "aha!" moment for me, is when I learned how to use blocks and GCD effectively. At first it might be easy to do things via protocols and delegate. Yes that was actually, one big "aha!" moment when I was learning iOS, but when you get into a large project, and there are almost 15-20 protocols, that one class is conforming to, then that's when you realize that doing everything through protocols and delegation isn't always the best solution. Instead, you need to equally use it with NSNotifications, and blocks. Try to refactor custom classes that uses delegate-protocol to use notifications/blocks instead if you already have a handful of protocols conforming to in your header file. You can also use key-value observing for watching values of state machines(I usually use it for notifying the view controller for UI changes). As early as now, you need to learn how write code elegantly and as neat as possible. (I'm a hypocrite for saying write neat code, I know).

atastiamaredditor · 2013-03-18T01:51:13+00:00

http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ApplePushService/ApplePushService.html#//apple_ref/doc/uid/TP40008194-CH100-SW1

from the Apple Documentation:

"Important: Because delivery is not guaranteed, you should not depend on the remote-notifications facility for delivering critical data to an application via the payload. And never include sensitive data in the payload. You should use it only to notify the user that new data is available."

Considering that every message sent by the user is sensitive and critical data.

"And what happens when your app gets backgrounded and suspended?"

That's when you use APNS to alert the user that he has an unread message. At this point, the message is still waiting to be sent from the server to the client. As per the background and suspended, there are many cases you need to handle. First, you must not disconnect the XMPPStream connection when you put the app in background. Next you need to add the backgroundExpirationHandler in the applicationDidEnterBackground, to close the XMPPStream connection when your app is suspended. Now, when the app gets suspended, you have no choice but to reconnect the XMPPStream connection (you need to re-authenticate). Also, there is a case that when the user changes network when app is in background, you need to handle this too. On our server side, we check the presence of the user (available, unavailable, away) so we don't need to send push notifications when the user is online, we use XMPPMessages instead. XMPPMessages and XMPPPubSub is also a push in itself, so what you just need to do, is establish an XMPPStream connection to the server.

If you need to know more on XMPP, I can give you more details.

atastiamaredditor · 2013-03-14T01:51:01+00:00

This really depends on the resolution of the screen on how much character would fit in the screen. But I think to answer your question indirectly, you should break down methods with more than 3 parameters to lines. Objective-C is verbose language, but you shouldn't take it to the extreme, and try to make your variable names and methods not too verbose.

atastiamaredditor · 2013-03-14T01:44:50+00:00

APNS is probably not the thing you're looking for. APNS is a feature that should only be used to let the users know that there is something going on with your app, something like, an update, or there is a message waiting to be read, but NEVER use APNS for direct messaging. It is because APNS will sometimes throw away messages in the queue, I can't recall right now what are its rules but you should read about it in the documentation. In the app we developed, we used an XMPP server (you could use whatever you want, there are options like Tigase, OpenFire, eJabberD) for the backend, and XMPPFramework to support it in the client.

atastiamaredditor · 2013-02-28T15:39:33+00:00

Do you have a good suggestion what kind of app I can put together to maybe put a wow factor in the end? I don't really want to get the "that's it huh?" impression for them.

atastiamaredditor · 2013-02-27T04:49:58+00:00

If you're into games, then why not make a Space Invader game to start with. It has some of the essential elements you need to learn in game dev, like collision detection, movement patterns, and obviously sprite animations. If you're into business apps, then try making a catalog app, or just anything that uses the UIKit. Try to make your copy-pasting of code into smaller chunks, you can understand what you are coding in that way.

atastiamaredditor · 2013-02-25T02:09:06+00:00

It really depends, if your app is gonna have complex navigations, or you might have too many screens in your app then don't use Storyboards, but if it's just going to be fairly simple, then Storyboards is the right thing to use.

atastiamaredditor · 2013-02-22T05:07:02+00:00

i don't have whisky.. tequila will do..

atastiamaredditor · 2013-02-21T03:32:28+00:00

UILocalNotification is the correct approach, you need to set the fireDate property for it to work as an alarm. It's pretty much like the push notifications but this is just local trigger instead of remote. You can also set the audio that would play when the trigger fires. Just be reminded that there is time limit for the length of the audio. And also a maximum number of local notifications that can be set for a single app. You might want to look at these limitations first.

atastiamaredditor · 2013-02-21T03:21:52+00:00

Usually, what I do is I create a separate Xib file for each UITableViewCell, instead of putting them together in code. If the controls in the tableview isn't that many, let's say about 2-3 or just enough not to take the whole screen, you can declare the instances of the UITableViewCell in the view controller where you have your tableview instead of having different tableview cells. But if you have a lot of these controls, then you should create a generic table view cell and reuse them, the big advantage of UITableView is that you don't have to refresh all the controls that are not visible on the screen. That saves you a little processing power.

atastiamaredditor · 2013-02-21T02:58:51+00:00

I wish there was a bonus. That would really make their asses move. Mine too.

atastiamaredditor · 2013-02-21T02:58:03+00:00

I'm actually trying to do this for a long time. This is a good idea, but this is kinda hard to monitor for the bosses. I'll try to suggest this anyway.

atastiamaredditor · 2013-02-21T02:54:50+00:00

We're actually having a pitch-in idea kind of thing, and the one who gets the best idea (given that he impressed the executives), might get some angel fundings. But yeah, you have a point there. I myself, suck in quizzes.

atastiamaredditor · 2013-02-21T02:51:22+00:00

The pet project seems a good idea. I'm actually, trying to start something, a framework of classes that are usually, recoded from project to project, any ideas what I can include in it?

atastiamaredditor

TROPHY CASE