[HELP WANTED] software architect/ UI UX/ AWS react-native skills. I have a partnership with an preaccelerator and need help.
I'm working with an accelerator in Atl, Ga and provide development services. I want to be able to assist all businesses in getting their idea off the group but need more assistance in building beautiful designs and someone who knows how to design AWS serverless apps with react-native. I already have a team of developers I'm working with and just need some extra help. My business is very scalable and just need some help with the areas I'm weak in.
Hey I am a UX/UI designer with 10 years experience. I would like to learn more about what how the whole thing works.
Hey @andreflores thanks for reaching out. Go ahead and go to my profile and send me an email I'll be able to send you documents on how the current structure works.
AWS amplify would pair well with your existing serverless architecture and potentially help you ship your mobile app faster: https://aws-amplify.github.io/
Thanks for the link @nwpointer I did some reading but it seems like I create my backend and frontend in the same repo can I separate it? ideally, I only want to push the front end code to the app store so no API key is exposed
Those are good questions. Regarding API keys, Amplify provides a couple ways of doing user authentication so generally speaking, including secrets such as an API key in the app should not be necessary.
Even though they are in the same repo, updating your cloud resources and updating your mobile app are separate steps so the mobile app should not include code for cloud resources such as lambdas for example.
That said, if you do want to keep backend and frontend code separate, amplify has some support for this - for example you can define a custom graphql api resolver that executes lambdas defined and deployed outside of the amplify project.
@nwpointer ok that helps out ALOT. So even though I'll be pushing an aws-exports.js containing a Cognito poolid, region id, and API endpoints having those pushed is not that big of a deal because in order to obtain access the user still needs the API keys at the end of the day. Then at that point, if I want to do local development I can use AWS SAM for local lambda development to build the REST endpoints defined in the amplify folder within react-native right right?
yeah you should be able to get that working. At this point I feel like an amplify fan-boy but amplify also supports creating and running lambdas locally so if you're not all ready invested in using SAM that might be easier.
eg:
amplify function addcli will ask some questions and create the lambda for youamplify function invoke <function_name>will run function locally and log outputamplify function pushwill deploy function to the aws cloudAre you looking for a UX/UI designer or Mobile/Full-Stack engineer?
Hey, @TangoKilo honestly the UX/UI designer is of higher priority.
I can help you with aws stuff .. what kind of help do you need ?
Hey @Raiyanyahya I'm starting a React native project I have 5 developers on the team and our website backend is all on aws lambda console. However I want to move the backend to AWS SAM so they can build and test locally then deploy to cloud.
How are you deploying your lambdas now ?? As i understand you want to use sam templates to facilitate the creation of serverless resources like lambdas with your code . Let me know and i can help you .
So far we've been building directly through the console for the react website. However, The mobile will have a different set of API and to keep it organized I want to use SAM for the mobile before we get too deep and can't go back.
so what you basicallly need a sam template that creates the below :
1.Lambda
2. Api Gateway
3.Lambda permission reource
Then you need an auto ci cd task which zips your code puts it on an s3 bucket and which will be used to unzip the code to your lambda. (i am assuming a python lambda).
Hey @Raiyanyahya that's the gist however I'm doing it via Node.js lambda.