Need advice about which tool to choose?Ask the StackShare community!
Expo vs Framework7: What are the differences?
Introduction: Expo and Framework7 are two popular tools in the world of mobile app development. Both serve as frameworks for building mobile applications, but they have key differences that set them apart from each other.
Development Approach: Expo is a set of tools and services built around React Native, making it easier to start mobile app development without the need for Android Studio or Xcode. On the other hand, Framework7 is a full-featured HTML framework specifically designed for building iOS and Android apps with a native look and feel using HTML, CSS, and JavaScript.
Ease of Use: Expo is known for its simplicity and ease of use for beginners and experienced developers alike, offering a wide range of features and services out of the box. Framework7, though versatile, requires a deeper understanding of web technologies and may have a steeper learning curve for those new to mobile app development.
Customization Options: Framework7 provides a high level of customization, allowing developers to modify and style every aspect of the application to fit their specific needs and design preferences. Expo, while offering a great starting point, may have limitations in terms of customization options compared to Framework7.
Native API Access: One of the key differences between Expo and Framework7 is the level of access to device features and native APIs. Expo abstracts much of the complexity of dealing with native APIs, making it easier to work with various device functionalities. Framework7, on the other hand, provides direct access to native APIs, offering more control but also requiring a deeper understanding of native development.
Community and Support: Expo has a large and active community of developers, offering extensive documentation, forums, and support resources to help with any issues or questions that may arise during app development. Framework7 also has a supportive community but may not be as large or well-established as Expo's community.
In Summary, Expo simplifies mobile app development using React Native, while Framework7 offers greater customization options and direct access to native APIs for building iOS and Android apps.
Hello guys, I am new here. So, if I posted without specific guidelines, please ignore.
Basically, I am an iOS developer and developing native apps for the last three years. Recently, I started learning React Native to develop apps for both platforms. If anyone out there knows any useful resources that will become a better react native developer.
#newbie
Well, the first resource I would recommend you is my upcoming book by Packt Publishing, "Professional React Native", but it's due late January next year :) . Now jokes aside (the book's real by the way :) ), the easiest way to build a iOS/Android/Web app with React Native is to do: npm install -g expo-cli expo init some-project cd some-project expo eject
You might have heard of Expo, but trust me, stay away from it. Expo highest value is that it's an already pre-configured 3 platforms environment, but if you don't eject then you're vendor-locked to what Expo has to offer in iOS and Android, which is very poor compared to going full React Native on these platforms, they can't even handle Google Sign In properly and by the way, even if your app is 10 lines of code your app size will be over 40 MB if you don't eject, yep it's that bad, plus the performance is regular and the loading times slow, not to mention that you're stuck with their build service which the free tier makes you wait for hours for a free build slot. It's important to note that when ejecting you don't lose the Web, you simply do expo start --web to start your dev environment and expo build:web to build a static website that you can serve with any web server. Regarding state management, don't bother with "lifting state up" philosophies mixed with Context API to manage your state, lifting state is a great pattern and helps your codebase, Context is great to avoid prop-drilling, but NEVER mix them to achieve app-wide state management, for that, simply go for Redux or MobX, the hype is all about Redux, but I consider MobX far better in many aspects. However, as you're getting new into this I would recommend you start with Redux AND PLEASE grab yourself npm install @manaflair/redux-batch so that you can batch updates and don't bring your app to a crawl. Forget that "connect HOC" thing with React-Redux, don't bother for a second with it, go with Hooks and useSelector and useDispatch and the likes, it will make your code SO much cleaner and smaller. Adopt clean and new Hooks philosophy, avoid writing class components as much as possible and write function components augmented with Hooks.
Our stack roughly divides into three major components, the front-end, back-end and the data storage.
For the front-end, we have decided to go with React Native via Expo. This allows us to target both Android and iOS with a single codebase. Expo provides "managed workflows" and an SDK that will simplify development and deployment.
For the back-end, we have decided to use Python. Python is the language of choice for machine learning (ML). It has extensive support for traditional ML algorithms (e.g. random forests) via Scikit-Learn and the SciPy ecosystem. On top of this, our industry partner has provided us their current solution written in Python. We decided to expose the back-end as a REST API using FastAPI. This allows us to nicely separate concerns from the rest of the codebase. FastAPIs use of static type hints, validation with Pydantic, and automated documentation allows us to build better APIs faster.
For data storage we decided to use a MongoDB Atlas, a NoSQL database. We decided to use a NoSQL database because we need to store large amounts of data (e.g data from the wearable IMUs). Moreover, due to the ever changing nature of a startup we require flexibility. NoSQL databases are schema-free which enables us to modify our schema as we see fit.
We plan on using GitHub Actions (GA) to orchestrate our CI/CD. Given GAs broad support of languages and workflows, it's hard to go wrong with this decision. We will also be using GitHub for version control and project management, so having everything in one place is convenient.
The major components of our CI/CD for the backend will consist of black for autoformatting, flake8 for linting, pytest for unit-testing, and mypy for static type checking and codecov for coverage reporting. We plan to use separate Docker containers to package the back-end and front-end components and use Docker Compose to launch the app. This allows us to better separate concerns, manage dependencies, and ensure our app is deployable anywhere.
Pros of Expo
- Free15
- Hot Reload13
- Easy to learn9
- Common ios and android app setup9
- Open Source6
- Streamlined6
- Builds into a React Native app5
- PWA supported2
- Plugins for web use with Next.js1
Pros of Framework7
- Free and open source21
- Well designed20
- Material design17
- Lots of ready-to-use ui elements, easy to customize15
- Best performance12
- Amazing documentation11
- Nice look and best performance9
- Performance and great features.9
- Rtl support9
- Easy To Learn7
- Free7
- Basic Web App Development Technique6
- Nice sample provided6
- Easy to use , transit from vanilla JS5
- Doesn't require learning a JS framework5
- Quick inital time5
- It's feels light to use5
- Easy to integrate2
Sign up to add or upvote prosMake informed product decisions
Cons of Expo
Cons of Framework7
- Not suitable for high performance in PWA. desktop apps1
