Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expo and React Native Web support for V6 and future #13918

Open
2 tasks
BuildingFiles opened this issue Oct 12, 2024 · 4 comments
Open
2 tasks

Expo and React Native Web support for V6 and future #13918

BuildingFiles opened this issue Oct 12, 2024 · 4 comments
Labels
feature-request Request a new feature React Native React Native related issue VP Version parity issues between v5 and v6

Comments

@BuildingFiles
Copy link

BuildingFiles commented Oct 12, 2024

Is this related to a new or existing framework?

React Native, Web Components

Is this related to a new or existing API?

Both if by api you mean amplify-js as a whole

Is this related to another service?

Not outside of amplify

Describe the feature you'd like to request

I was told that this feature request had been created already by aws support. But I could not locate it. So I made one of my own.

According to recent conversations with support and the dev team in other tickets. Support for expo go, react-native web and expo web while it always has been and still is being maintained in Version 5. Will no longer be supported in Version 6 and newer.

Our production application runs primarily as a web app. We've spent many years developing and to it using react-native and expo on Amplify. We love using Amplify for this.

But I have been told that the reason support is being dropped for web is because it is "a lot of work". With no regard to how much work time and money it's going to cost us loyal customers of Amplify. Making us have to completely throw out the last 5 years of development for an entirely new web framework that you currently still support.

I respectfully request that you re include support for expo and react-native web and continue to include them as full stack options for Amplifys newest and future versions.

Describe the solution you'd like

Continued support for web in expo and react-native after version 5

Describe alternatives you've considered

I'm open to suggestion that don't require a complete rewrite of our application in another farmwork, so we can continue to offer our clients our web app.

Additional context

No response

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change
@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending a response from the Amplify team. labels Oct 12, 2024
@haverchuck
Copy link
Member

@BuildingFiles We are reviewing this with the team. If needed, would you be available to meet with us?

@github-actions github-actions bot removed the pending-maintainer-response Issue is pending a response from the Amplify team. label Oct 14, 2024
@ashika112 ashika112 added feature-request Request a new feature React Native React Native related issue and removed pending-triage Issue is pending triage labels Oct 14, 2024
@rayelward
Copy link

We have been holding back on updating from v5 amplify because of the lack of support in this area.

@github-actions github-actions bot added the pending-maintainer-response Issue is pending a response from the Amplify team. label Oct 15, 2024
@BuildingFiles
Copy link
Author

BuildingFiles commented Oct 15, 2024

@BuildingFiles We are reviewing this with the team. If needed, would you be available to meet with us?

I am available if you need. I just got off a call with AWS support and some members of the development team as well.

@BuildingFiles
Copy link
Author

BuildingFiles commented Oct 15, 2024

We have been holding back on updating from v5 amplify because of the lack of support in this area.

( Had to edit this, thought you were a member of Amplifys dev team when I first read your post :) )

Its a good call it seems like at the moment upgrading to v6 will require a lot of editing for any existing application, and even after that's all said and done it may not work due to the web support issues on their end.

@cwomack cwomack added VP Version parity issues between v5 and v6 and removed pending-maintainer-response Issue is pending a response from the Amplify team. labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request a new feature React Native React Native related issue VP Version parity issues between v5 and v6
Projects
None yet
Development

No branches or pull requests

5 participants