I am new to app making, but I have a small tech review site that I am trying to grow and I want to make an app for. Its pretty simple what I am setting up. To start, I am using MySQL to have three basic things. The review's picture, the title, and the review itself. The idea of this is so I can have other users log in to write reviews and it can load easily on an app, the website, etc... The most trouble I am having is in Xcode trying to make an app for this. I want two basic screens. A list of all the reviews with the picture on the left, and the title, and when you click on it, it takes you to the second screen displaying the review itself. Does that make sense?
(I am using Xcode 5 on Mac OS X 10.9. This App is intended for iOS)
-Thank You!
*Moderators, I apologize if this is a duplicate question, I have searched and have not found an answer.
If I understand correctly what is your asking then you probably need to rephrase the question and edit the tags. Because it has nothing to do with xcode5, mysql, uitableview or even iOS.
Before you start designing your iOS app, you need to think the overall architecture for your service. The client iOS app shouldn't (and usually can't) communicate directly with a database server (mysql in your case), you need to think about a server side API layer for your iOS app to consume.
You need to outline your web API and decide what is its interface (entry points, resources, data structures), take a look at REST architecture, for example. Decide on your data exchange format (e.g. JSON, XML). Then decide what platform and framework you want to create your API layer with (e.g. PHP, Python, Ruby on Rails, Asp.net etc).
Your iOS app itself sounds like a simple classic Master-Detail pattern and what you wrote is a good start (Google for master detail examples, plenty of them for iOS as well). Your question is too broad here, you need to be more specific in order for people to be able to help you with the app itself.
Related
Imagine a social network application similar to twitter which every user is following and is also followed by some other users and whenever a user sends a message (text or photo) it is displayed instantly on the screen of users following him/her. What is the best way to make such an application for:
mobile
web
I have some web programming experience and the only way I know to do this in web is to send an ajax call every second from a user's client. My feeling tells me there should be a better way. I did some research and found webrtc. Is that the way to go? I (and probably many other users) will be grateful if you can explain the pros and cons of the solution you suggest.
Thanks a lot.
If you want to build conference app/ messaging app for web/mobile platform you can use latest web technologies.
Node.js is an Javascript framework which does efficient and non blocking IO and it works really well with applications which are not data intesive which involve lot of calculations.
Please go through Node.js and libraries associated with it, you can ahieve building efficient chat application.
First time post here, so forgive me for any bad etiquette/format.
I will preface by saying:
I have (over the last few months) been developing an iOS app for work. To be more specific, I am developing an inventory app to track bar inventory (liquor, beer, wine, etc). I can give more specifics on request if needed. I have most of the functionality done, only a couple more things I would like to implement. Eventually I will be porting it to Android as well.
At the moment, I have the model objects being archived to the local filesystem for saving and loading of data. However, my goal would be to database the model objects with the ability to display the information on a webpage. My logic is that no matter where the user is, he/she will be able to sign in to a service using a username and password, and view correctly formatted current/past inventories online. This is to allow the ability for a bartender to record the inventory, and have the bar manager view the inventory instances without having to have the physical device that recorded the inventory in his/her possession.
So here is my question:
Without being too general, what kind of service would I need to pull this off? I have a good amount of relevant front-end experience, specifically with iOS, Objective-C, HTML and CSS. However, I have ZERO experience on the back-end. I have researched around the internet, and I am aware of things such as cloud databases, web hosting and MySQL, etc. However, I cannot seem to find a definitive answer without asking my specific question. I suppose I would just like to be pointed in the right direction before investing money and time into a service that may prove useless to my cause.
Any resources and help would be greatly appreciated. Thank you!
There's not a definitive answer and you have a lot of options.
For me, the simplest is to set up a server with a database incorporated (mysql for example) and with a web service (written in PHP for example) that manages the database and queries on that.
Online you can find tons of guide on how to write a script in PHP that manages a database:
http://www.freewebmasterhelp.com/tutorials/phpmysql/2
For the iOS part you can follow also this guide:
http://www.techrepublic.com/blog/software-engineer/create-your-own-web-service-for-an-ios-app-part-one/
Good luck!
So this is more of a general question about apps and techniques rather than a specific code question...
When developing an larger app, how would a developer access lots of data from a website. The example I'll use is an app like Yelp. They have both a web-access site and an app, both share the same information. I would imagine that information like that is stored on the website via some sort of MySQL database and the iOS device access's it as needed based on the user's requests.
How might a developer writing an app start something like this? I assume you need to somehow securely tie the MySQL database to iOS and so on. I've seen a lot of techniques on the web, but they all seem very simple and not safe for a large scale app.
Any ideas would be awesome!
The key term you're looking for is "API" (Application Programming Interface).
A Yelp iOS app won't access Yelp's databases directly. There will be a layer (I simplify here somewhat) between that and the iOS app; this layer will provide a series of methods (the API) by which clients can make queries and potentially manipulate remote state.
A common API format is JSON over HTTP, and indeed, this is what the official Yelp API seems to be.
Good starting points would be the documentation for NSURLConnection and NSJSONSerialization, and the Yelp API documentation I link above.
I'm looking to develop a mobile app which is going to help people find out whether a train is going to go to a particular platform or not.It is very simple. I know the timetables. I'll be making database of train timings and compare with the timings of user, when he uses the app and tell him, if the next train coming at the station he's at, is going to this platform at location X or not.
There won't be any fancy UI. There would be a dropdown of all stations. That's it. Response from the app will be going to platform no A. I don't know if I will include any feature as of now. The requirement that I see is, app should be offline and platform agnostic.The database entries are fixed and if they change then I should be able to give a new update.I have been reading about HTML5, but I don't want people to use the Internet for this. It should be available on Nokia phones,Android phones, Blackberry,Apple in that order.
Offline and platform agnostic will be hard to combine, unless you use one of the toolkits that pretend to do this (we started that way, but reverted - cost more time to chase bugs in the toolkit than to write code). Easiest is you give up the first requirement - most people with smart phones will have data bundles anyway, a tiny query is not going to make them frown.
Assuming you're not dropping the requirement, HTML5 for the UI can still be an option as most platforms let you embed the browser in your app. That way, you'd only need to port some small wrapper code and the business logic. If it's a commercial app, pick one or two key platforms (that will give you the necessary user feedback to make your app better) and outsource porting of the rest.
This is a tough one... I'd choose native programming. Id just have all the different platforms linked so they use the exact same database. Unfortunately, they all use different programming languages. I don't know about Nokia or Blackberry, but Android uses Java (or C# through MonoDroid) while Iphones/Ipods use Obj-C (or C# through MonoTouch).
I have developed an iOS app that uses CoreData/SQLite. It works, but now I have to populate it with data.
I am wondering what the best method would be. As you can see from the title of this post, I am thinking of these two options, but maybe there is another way.
I'm not sure whether I will have multiple people entering data (that would be great), so that is a consideration..
I welcome advice.
How about a mix of both? you can upload the data to a webserver ( depending on what you want to do with it ). Offer people to have a web app for home and an iphone app for when th ey are on the go. The data they add can be stored locally so they don't need any internet when abroad, which makes the app useable on the ipod touch
Native is (almost) always better than web-only. A server is extra overhead; a mix might simplify that a bit. And in most cases, even if your server goes down hopefully users can still use the app with what data they've already downloaded.