Project for learning - react-native

For my learning project, I want to create an app with:
1.settings menu when I can store 3 values. Email, password, and car number.
1 button ( when I open the app and push that button app connects to a web page, logins with email and password after login it should go to search menu on a website enter their car number and then pushes button "pay" when the car is found.
Basically, this app is for paying for parking with 1 click.
The thing is I have the knowledge to build this simple UI and probably I need some sort of database like SQLite to store the settings but how can I do second part? When I push the button that the app connects to www.parking.com(this is not a real webpage), logins and do other staff...
Can someone give me some pointers, examples of similar apps or links where I can find any related information?
Do I need to create some kind of API to connect to the webpage?

Use expo.io to create the app and to perform authentication. Use fetch or axios to access the web page. Use expo api for firebase to store data.
Here is a link to get you started doing authentication and storing data: https://docs.expo.io/versions/latest/guides/using-firebase/

Related

link my users social media account in my mobile app, allowing native app to open

I've got an app with user profiles. On the users profile, I let them put links to their other social media accounts. I know app linking requires the correct app's schema and I know those schemas depend on the system (iOS, Android). I want the user to be able to just copy the url of their social media profile (http://www.whateversocialmedia.com/userprofile),paste it and save it. I will manipulate the string get the "userprofile" out and put it in the schema. HERE's the problem, Facebook, requires an ID for the schema, but most people don't know how to get their ID, while it's somewhat easy to get, it does require right clicking on a mouse and searching some code to get, Does Facebook have an api I can hit to send a username and get back a user ID? I feel like they would want people to link to their app easily. I've looked all over Graph API

To create an authentication system

I am new in flutter and in apps. I work on a little game for the moment and I need an identifier for each member, I have a MySQL database and php script api. I have done a signup page and a signin page too.
I have no experience in app so i would like to know how game apps works exactly. I have bravolotto a lotto game application and if i remember well when you signup you Don't need to login after that. When you open the application you are automatically connected to the app.
What are the best solutions to create an authentication system in flutter.
I need to have the user id on all members page of the app so if the user play I can save the result of his game with his user id in my MySQL database with php api.

How to make company own login button

I am working for a company. I am required to make a login button for their own server, such as google and facebook for their different applications. My question is how i will be able to create these buttons, for our different apps, e.g. android, Java servers etc. Furthermore the server has nothing in place for this (i.e. generating the app id etc.), I would be able to figure that out. Is there anyone with any guidance towards this, maybe a few links.
Just to be clear, i am not looking for a implementation for the google/facebook login buttons, I want people to be able to add a "Our Company Login" button to their apps.

hubspot api access but client_id

I am trying to parse some data using hubspot api by given demo account. To have a proper response you need client_id within parameters. It says, I can find my client_id inside app dashboard. Can someone please tell me what is the exact client_id inside dashboard or what is the client parameter for tokens.
Thanks
You would get the client_id by creating an app from the Developers dashboard, not your portal dashboard. If you haven't created an app yet, you would first need to sign in and then go here:
https://app.hubspot.com/developers/signup
If you haven't signed up yet, you can sign up there to create a Developers account, otherwise you'll get directed to the My Apps Dashboard. click the blue Create App button in the top right to create an app, and after the app is created you can click on the app name from the App Dashboard to get the Client ID.

Twitter API - get Account Details from consumerKey and consumerToken

I inherited an application that has tons of users already authorized to get twitter data on their behalf.
The problem is the guy who created is not around anymore and I am left with consumerKey and consumerToken only.
That in itself is sufficient to interact with twitter API, but I now need to know the account details ( in particular the screen_name that created the app) .
I could not find any API to get such details. Any ideas on how to get it.?
There isn't a direct way to find the app owner's screen name, but here are a few things you can do to investigate:
Use the ConsumerKey and ConsumerSecret, that you have, to start the OAuth process.
On the Twitter Authorization screen, you can see the name of the app and who created it.
You might be able to do a Twitter search for the person who created the app and get their screen name.
Continue to authorize the app - this will put it in your app list.
Visit your personal Twitter Settings tab, click on Apps, and find the App that you authorized.
Click on the owner's name, which will lead you to a Web site.
The Web site might be the company Web site, in which case, there is no further help.
The Web site might belong to the owner and it might have a link to the owner's Twitter account where you can get their screen name.
Just know that there's nothing keeping you from using the ConsumerKey/ConsumerSecret that the other guy set up. You can create your own app - preferably with an account that belongs to the company with credentials that the company can access if you're no longer around. Then use the ConsumerKey/ConsumerSecret from the new app on subsequent deployments.