Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
i just started coding iPhone apps on xcode and i was curious what is the best database to use? For example a database to store names emails etc, to make a sign up and login page.
Cheers
If you are talking about storing a database local to your device, coredata is the standard: https://developer.apple.com/library/mac/documentation/cocoa/conceptual/coredata/cdProgrammingGuide.html
Small amounts of data can be persisted using user defaults: https://developer.apple.com/library/ios/documentation/cocoa/reference/foundation/Classes/NSUserDefaults_Class/Reference/Reference.html
When you said the words "sign up and login page," I suppose you are talking about an online database.
Use Parse.com's BaaS (backend as a service). Its also super easy to implement. Here is a tutorial from them talking about how to make a sign in/sign up page.
Keep in mind, there are other Baas like Kinvey and StorageRoom which are also good as well.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I'm an educator and wish to build an app for my students. It will be quite basic with a login so they can find their info, invoices, ... But it would be really handy for them to have an app for this instead of using the webbrowser.
But it wouldn't be financially interesting to build an native app from scratch and since this functionality already exists op web. So I would like to use WebView instead to load this part of my website and won't have to maintain the app.
I heard Apple can give you hard time and decline your app if it only uses Webview to load a webpage. Is that correct?
If your site is responsive and within the webview it presents application appearance it becomes easier to be approved. If they refuse you can put a single native functionality to justify being an app, or try to cache the site on the local disk.
You said you have a login system for your students, and it is important to register on the site as well.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm very new to rails and have very little experience with programming in general. I was given the project of creating a simple rails app that is able to check a users Instagram when given their User ID and Password. My question in general is how do I approach this? Where do I start and essentially how do I do this?
Well, you should never ask for the user's password for an external service (no sane user will give it to you). Instead use omniauth (omniauth-instagram, specifically) to get an access_token and then simply use the Instagram ruby gem (https://github.com/Instagram/instagram-ruby-gem) to get their timeline.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm trying to determine what would be the best route to go for an app idea I have in regards to using a back-end service or not.
The app will not require any sign up / log in steps
The concept does have a part of taking a photo. For example, a photo could be taken every day, or multiple photos per day, equaling 365 + photos.
I'd like for the user to be able to view these photos at any time, and possibly export them all at once in some form (if that is possible) at any time.
What's the best way of doing this to have a good experience in the app?
I supposed you'd define a good experience in terms of photo storage by being quick. You really don't have many options. You could either write 365+ photos into your documents directory or write them into a CoreData store. I'd probably opt for the CoreData store, because I have a feeling you're going to have some metadata associated with the image.
Really though, this question is a bit too specific to your situation. See also Best way to store images in iOS
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Can Ruby on Rails be used for developing Real Time Application (similar to like Facebook, twitter, geekList ) ? What sort of database (NoSql), REST API is required ? Node.js seems to be popular for RTA. Any insight will be greatly appreciated?
You can try with Faye, but if you want development real time application, I think Node.js is the best. :)...Sorry, I'm only beginner developer :)
Ruby and Rails can definitely be used for that (twitter was originally a Rails app). What kind of db you need will depend on the specifics of your application. I am guessing from your question that you are a beginner. In that case, I would guess this is one of your first applications and you are trying to figure out which technology to you. I suggest you pick whichever one you are most interested in. You can do the kind of application you are talking about in most modern web frameworks.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am definitely going to use an authentication scheme (Devise) with 3 roles: user, admin & sponsor. The question is: should I implement authentication right away or wait until I have my other models/views in place first?
I think it is usefull to do it as first, so you can easely integrate them in other models, eg. log that a user does something, you will also be able to set weather a user should have access to a specific controller.
Unless, you have a good reason to not do it...
A rather unexpected question, but you can safely create your authentication routine right away. In any project i create, authentication is definitely one of the first things i code, most times using Sorcery instead of Devise.
IMO it doesn't really matter, but why not do it earlier than later? It's pre-built, allows early testing (and testing it often), and allows access control needs to evolve organically rather than waiting until they all pile up and you have to do it all at once.