I want to create a user login system that will eventually handle a lot of users and information linked to the users. I've looked a lot into core data but can someone tell me from experience how I should handle my data? Should I use core data? Also I'm programming in swift.
Singing in/up with an email is important for almost every app that requires a social interaction. In the past, developers often used Parse (backend-provider) as to implement a login system. But, Parse is closing down soon. So, here we have another solution, as someone mentioned, "Firebase". Firebase allows you to quickly create a login system integrated with email, Facebook, Github, Google, you name it. You are also able to store user information such as photos and personal information using Firebase's core feature known as 'Real time database' and "Storage". Here is a quick introduction for you to learn more about Firebase!
Introduction to Firebase Authentication
https://www.youtube.com/watch?v=8sGY55yxicA
Introduction to Firebase Database
https://www.youtube.com/watch?v=U5aeM5dvUpA
Login Tutorial by Jared
https://www.youtube.com/watch?v=8sRUhzgJhcY
There is a learning curve, but let me know if you are stuck,
read the documentation and "get started guideline"
https://firebase.google.com/docs/ios/setup
If you find this information useful, I would appreciate your thumbs up!
Related
I have started building a website on Laravel and I wanted to include social Login to my site.
I have a basic understanding of how this works. I used Socialite and Google API and followed the documentation and setup a login route to google and was able to get a response with token and other details.
This is where I am stuck. I wan't to build a robust user system. I need help in understanding the best concept for Social login.
For example,
when a user logs in from google, do I need to save the token. Do I need to create an entry in the database and save as a user or should I just load the user information every time from what is returned by the API.
Also, what is the difference between social login and sing up with social login?
Ultimately, I would like to build a site with user profiles and I would like to get as much information from API's as possible and setup the user system in efficient way.
Any help is much appreciated
I'm building an iOS (Swift) app that needs realtime chat as part of the functionality. While Parse works well for push, data storage, etc..., it doesn't support realtime. I would like to use Firebase for the realtime support, but need help authenticating to Firebase using a Parse user. I really don't know where to start with this. Any help would be greatly appreciated.
The question is pretty vague so a definitive answer is not possible: here's a thought.
Firebase and Parse are two different companies and therefore require separate authentications.
If your users have a username/password type authentication in Parse, you could use the same data in Firebase and authenticate through code. i.e. User creates a new account in Parse, and an account is created in Firebase via code. When the user authenticates to Parse, it also authenticates to Firebase via code.
There are a LOT of design elements to consider in going this route: how do you create a firebase user (in code) without your app authenticating itself as a 'super' user? Hard code credentials? That may be a security issue.
Are you going to keep two sets of user data? One in Parse and one in Firebase? What if a user needs to reset their password or account. As you can see, it can get out of control rather quickly.
You may want to consider sticking with one platform to simplify the entire process. By the sound of at least one of the requirements, Firebase can do much of what Parse can do but also give the real-time updates you need.
I am currently building an app where they require all their users to be able to view their feeds only.
I looked at a lot of tutorials online which talk about the new api v1.1 of twitter and now authentication is required at all times.
I see a lot of examples and even successfully followed several of them like
http://www.appcoda.com/ios-programming-101-integrate-twitter-and-facebook-sharing-in-ios-6/
I even saw a tutorial posted on the twitter dev page.Following all of these focused on a few key elements
Using ACAccount to retrieve the account settings of the current user
Using the SLRequest to encapsulate the HTTP request made to the twitter api
Retrieving the data in JSON format, parsing it and presenting it to the user
Well my question is, I do not want user specific feeds. It's like a company updates their twitter regularly, users using the app should get feeds regarding the company. So I was wondering if there was a way, the app provides some default or hard coded authentication information ?
Is there some sort of tutorial, library or anything out there to help me move in the correct direction ?
Thank You for your time and help.
Your going to want to implement the following API call to get that information:
https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline
Once your application is authorized you can make a call to,
https://dev.twitter.com/docs/api/1.1/get/statuses/MorleyGaelsGAA.json
That should give you the information you're looking for.
I'm creating a simple iPhone app. The basic premise is that the app will display some data (That I provide online) on the application. The data changes over time, so the app has to draw the data from online and display it. I don't have a significant programming background so I don't want to use my own server.
Thus, I thought it would be significantly easier to just put the data into some documents on a Google account and then access them programmatically via the Google Drive API. I could then update the data in my Drive account and it would get updated in the application. The key here is that I am ONLY accessing ONE account that I own MYSELF. The users' accounts are not being accessed. Therefore the goal is to never have to log in manually. It should all happen behind the scenes, aka, it should look like a server, not a google doc.
With this in mind, it doesn't make sense to show the Google Accounts sign-in page to my users as the standard OAuth2.0 tutorial shows here:https://developers.google.com/drive/quickstart-ios#step_1_enable_the_drive_api
I should be able to access my own data by somehow hardcoding in my username, password etc. Google agrees here: https://developers.google.com/drive/service-accounts#use_regular_google_accounts_as_application-owned_accounts
The above link mentions a "refresh token" that I'm supposed to save. However, I have no idea how to build and save that token, or even for that matter, where to find it.
I've gone through both the basic tutorial and the Dr. Edit Tutorial for iOS, but they both assume that the application is accessing USER accounts not application-owned accounts.
I'm not asking for someone to write the code for me (though tidbits are nice), but if you can point me to a step-by-step guide or related sample code that would help me get started that would be awesome. I'll even come back and post the code that I use!
EDIT: Since I realized that the Google Drive API wasn't something I could use for what I am trying to do, I eventually found Parse which is an awesome tool that handles all the server backend for me and is free at the basic level.
Google APIs objective-C client library doesn't support service (application-owned) accounts, because they are supposed to be used by a server-side apps, instead of clients -- you shouldn't be distributing your private key as a part of an app.
If you would like to distribute content from a service account, maybe you should write a server leg to do the authentication and pass clients credentials in a secure way for them to talk to the API on the behalf of the service account. Or, use Web publishing to make documents universally accessible without authorization and authentication if privacy is not a concern.
I'm trying to authenticate my user on FB with my app in a simple manner, the iOS SDK has this SSO explanation and that's pretty much it, and it seems a bit extreme since I pretty much have to wrap up my entire app in FB goodness, at least that's what they guide you through.
Is there just a simple way, be it with the SDK or some other manner, to guide the user through the OAuth process and retrieve the access token and user data, like name, email and birthdate?
One shortcut here is using something like Parse to handle it for you. They actually also include a very nicely made login view controller that does exactly what you're looking for. You can see it here.