iOS 7 CRUD Application - Interface to input data - iphone

guys!
I've been studying iOS development for a few days, and I wanted to create a CRUD application to make sure I am understanding the concepts.
Well, I wanted to create a interface to input data similar to the Phone app, where user can insert a new contact. In my understanding, it seems to be a table view. However, every tutorial I find about table views are related to displaying data and not inputing it. Am I right?
I'm not expecting any code sample or anything like that, I just want to know how can I provide a good experience similar to the one in Phone App.

The Contacts app on the iPhone is built on UITableViews. Apple does not provide any guideline for your question. Use them or don't, it's up to you.
It might be quicker though to use a UITableView in your case, as you may need to present/edit much information and the scrolling would already be handled by the system.

Related

iPhone :Can we add more than One application in a Single application

I do have an Idea to integrate with my application. I want to create multiple application within a single one application.
Like
and application containing Weather application as well as image processing application + camera based application.
I want to know Is this thing possible with iphone application?
Please suggest me is this possible with iPhone app development and is it allowed by apple or not.
thanks for your suggestion in advance.
Consider these things as features. Weather information is a feature, image processing is another and camera in another. You can create any number of features in your app. If that is what you have meant by application then that is technically possible and seems also OK with Apple. This is not 3 different applications, rather it's one application with three different features. No matter how many features you have, iOS will treat that as a single application(a single app bundle with a single executable file).
But if are asking whether there is any way to combine separate applications(separate projects, separate app bundles with separate executables) then that is not possible.
Note: Personally I think adding completely different features in a single app is not a good idea.
Go to App Store and search for this app, App Tool Box - All in One. It's exactly the same structure as you mentioned in your post. And it only costs $0.99.
Sure, you can do it. I don't think Apple has anything against an app that does more than one thing. As long as none of those things breaks any of their rules.

iPhone UI design...!

I have seen apps in App Store that have really attractive UI.When i make an app i use only the default set of control provided by Interface Builder and my app(even though good in functionality)does not have a UI that can attract people.Is there any ref or sample code that teaches us how to design good UIs for iPhone apps.
Also I want to place a control in my App similar to one in iPhone(i.e the way we unlock the iPhone by sliding a button and the iPhone gets unlocked)how can we do this.Please provide some ref or sample code for it.
There is no simples step by step description of how to make really attractive ui's. It takes both time, skill and a sense of esthetics. However, a good starting point is to thoroughly read your way through apples iphone human interface guidelines:
http://developer.apple.com/iphone/library/documentation/userexperience/conceptual/mobilehig/Introduction/Introduction.html

How to I make a navigation-based app?

Yes, I know, most of you are thinking I'm an idiot, butt (kidding) I'm not. I've been searching everywhere for something on how to fully make a navigation-based iphone app, but all I've found is how to set up table views or navigation controllers. I haven't found anything on how to create a data model (something simple from arrays and dictionaries, SQLite and CoreData are a bit out of my scope) or navigate it. Does anyone know of any tutorials or anything like that? Thanks.
The key phrase you're looking for is a 'drill down' pattern.
Apple has a great example (with full sample application) of a drill-down application with a basic data controller:
http://developer.apple.com/iphone/library/samplecode/SimpleDrillDown/Introduction/Intro.html
The Stanford iPhone Development Course provides good information on how to set-up a navigation based app. Specifically, lectures 7 - 9 deal with the topics you were interested in. You can find the lectures on iTunes U. The course assignments and handouts are also available on the course website.

How to show related city name according to the incoming call on iPhone?

I want to add something (eg. the related city name) into the UI view when I make a phone call or received a phone call on iPhone. However, I can't figure out a good solution for this idea. Could anyone who has experience on this subject gives me some suggestions?
My currently solution is, try to write an extension based on mobile substrate and hook functions in SpringBoard. So many difficulties existed and following are my current big questions,
How to develop such a extension? I downloaded some examples from google, unfortunately they cann't even be compiled on my toolchain.
I can't figure out which ui view for the related screen I should use to insert my own component. I get header files of SpringBoard via class-dump, but no docs and no comments about its usage. Could someone share his discoveries with me?
How to build a trusted cross-compiling enviroment on leopard? All kinds of confusing errors pop up when I try to build others's codes. I've tried Zdziarski's instrunctions in his book, it works with iPhone OS 1 and can compile common projects with open sdk, but how should I do to make it works when comipiling ms plugins?
Also, is there any other solution to translate my ideas to codes? I start iPhone development one month ago, no experience with cocoa/Obj-C before. So your suggestions are very appriciated.
~ Link Bian (卞林扣)
Email/MSN: linkou.bian#gmail.com
I think you are asking for too much. It wont be possible to manipulate incoming/outgoing call screens. Ethically, that is.
Zdziarski is a hacker and from his book, you will get many undocumented API calls which will make Apple reject your app. Same goes for Erica Sadun's iPhone Developer's Cookbook.
Something that really helped me get dylibs compiled was using SkylarEC's Xcode template and just appended an extension of '.dylib' onto the binary and sshing it into /Library/MobileSubstrate/DynamicLibraries. I suggest hooking SBCallAlert or SBCallAlertDisplay to get the id of the caller which is usually just an NSString. Play around with it a little bit, those are all the visualizing methods of a call. If you put in an nslog in your custom override method, you can view the output in iPhoneConfgurationUtilitie (windows) or the console in Xcode. From there you would most likley need an index of area codes to comare the callers to. I don't believe you can add subviews to the call, on I intercept and reissue the strings for the views already there.
But you know, apple doesn't like this :P
lemme know if this helps

Regarding iPhone Application Design Document

I am just entered into iPhone Application Development. I have to start the work on iPhone Application. And i have some Requirements Specification for particular application. Now for a starting phase i want to prepare a Design Document for that application. So, anyone can suggest me what i have to include in any mobile or iPhone Application ? If you have any same design document then please provide some link, if possible.
Or else, if you have any other idea for starting the application, then also you can suggest.
Thanks in advance.
As a first step I'd always get the user interface down on paper with some mock-ups of screens, location of controls etc.
From that, I usually write in how the transitions between views are triggered and what information is flowing between different parts of the application with regards to the user interface.
Then, I decide on how I need to store the data in my application (usually a separate class) and how this will be accessed from the rest of the application.
A 3 or 4 page document will cover most small apps. I find doing the UI mock-up and basic data is enough to get going and get a bare bones app working.