The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Bluesky, and Blogger.
Stencil v3.4.0 is now available! This was a smaller release as the team has been focusing efforts on the upcoming Stencil v4 release, but does introduce one new feature for validating core fields used when publishing your Stencil component libraries. Let’s take a look!
In Stencil v3.4.0 we’re changing how the Stencil compiler
validates fields in your project’s package.json
that
have recommended values based on certain Stencil output target
types. Historically, the output target to validate against has been
controlled by Stencil itself. Moving forward, developers will be
able to designate a specific output target to use for this
validation.
Taking advantage of this new behavior is straightforward and
only requires you to set two flags in your Stencil configuration.
Firstly, you’ll need to opt in to the validation logic by enabling
the validatePrimaryPackageOutputTarget
flag in the
root of your config:
import { Config } from '@stencil/core';
export const config: Config = {
validatePrimaryPackageOutputTarget: true,
// ...
};
Then, simply set the isPrimaryPackageOututTarget
flag on the output target you would like to validate (the list of
valid output target types can be found in the Stencil docs):
import { Config } from '@stencil/core';
export const config: Config = {
validatePrimaryPackageOutputTarget: true,
outputTargets: [
{
type: ‘dist’,
isPrimaryPackageOutputTarget: true,
// ...
}
]
// ...
};
That’s it! Stencil will handle the rest based on your output
target configuration and you’ll see warnings logged to the console
at build time if it detects a problem with your configuration or
the values in your package.json
don’t match the
recommended values.
For more information on this feature, check out the related Stencil docs.
This release of Stencil includes additional internal updates and dependency version bumps. For a full list of changes, please take a look at the changelog for this release.
The post Announcing Stencil v3.4.0 appeared first on Ionic Blog.
Read more https://ionic.io/blog/announcing-stencil-v3-4-0
Join us in Austin, TX, this October for an unforgettable Ionic community-focused experience as we bring ioniconf to you live and in-person. Explore a city that embraces diversity, inclusivity, and innovation like no other. Prepare to be captivated by the vibrant tech scene, warm Texan hospitality, and an array of exciting activities that will make your visit truly memorable.
We’re so excited about hosting you all in Austin that we decided to create this handy little guide for you. From why we picked it to what you should do while you’re there, we’ve got all the details you need to make the most of ioniconf and your visit to sunny Austin.
Inclusivity and Diversity: Austin takes pride in its inclusive community that welcomes people from all walks of life. Connect and collaborate with fellow developers from diverse backgrounds, while expanding your network and gaining new perspectives.
Thriving Tech Ecosystem: Austin’s tech scene is booming, attracting top-tier companies, startups, and thought leaders from around the globe. Immerse yourself in the innovative atmosphere that fuels breakthrough ideas, fosters professional growth, and offers exciting career prospects.
October Delights: Experience Austin at its finest in October! The weather is comfortably warm, perfect for exploring the city’s renowned outdoor spaces, lush parks, and scenic trails. Plus, October brings an abundance of exciting events and festivals, ensuring there’s always something captivating happening right at your doorstep.
Live Music Capital: Dive into Austin’s legendary live music scene, where every street corner, bar, and venue is brimming with soulful melodies. Explore eclectic genres, catch amazing live performances, and witness the city’s deep-rooted musical heritage.
Culinary Paradise: Treat your taste buds to a culinary adventure like no other. Austin boasts a thriving food scene, offering everything from mouth-watering Texas barbeque to globally-inspired cuisine. Savor the flavors, and don’t miss the chance to indulge in Austin’s famous food trucks. So, be sure to bring your app-etite to ioniconf!
Outdoor Oasis: Embrace the great outdoors with Austin’s picturesque parks and green spaces. Discover the stunning beauty of Zilker Park, hike along the trails of Barton Creek Greenbelt, or paddleboard on the serene waters of Lady Bird Lake. Take in the breathtaking landscapes that make Austin a nature lover’s paradise.
Artistic Enclaves: Immerse yourself in Austin’s vibrant artistic community. Visit the colorful street art murals that adorn the city’s walls, explore the city’s numerous galleries, and discover unique local craftsmanship. Austin’s creative spirit is sure to inspire and ignite your own creativity.
Don’t miss out on the opportunity to be part of the first in-person ioniconf event while exploring the amazing city of Austin, TX. Ioniconf will bring together some of the greatest minds in the tech space to talk all things development, innovation, and Ionic. Expand your knowledge, connect with brilliant minds, and create lasting memories in the heart of Texas.
Disclaimer: Please note that due to the ever-evolving situation, we are closely monitoring public health guidelines to ensure a safe and secure event for all participants. Rest assured, necessary precautions will be taken to prioritize the well-being of our attendees.
The post Discover the Best of Austin, TX at ioniconf 2023! appeared first on Ionic Blog.
Read more https://ionic.io/blog/discover-the-best-of-austin-tx-at-ioniconf-2023
The Appflow team recently attended Chain React, the largest React Native conference in the United States. Industry leaders shared the latest in mobile development trends and technologies, including key takeaways and learnings you can apply for your own team.
Here are some of the main mobile development trends highlighted at Chain React, along with resources for implementing these for your own React Native app development.
One of the long-standing myths of mobile development is that cross-platform apps aren’t as performant. Educator and senior engineering leader Ankita Kulkarni busted that concept in her talk, “The performance myths of React Native.”
Her presentation addressed the arguments we’ve all heard before, but from experience know aren’t necessarily true, including:
She demonstrated that React Native apps can be just as performant as traditional native apps when developed with performance in mind. This includes paying attention to when renders occur, leveraging performant animation libraries, and using performance profiling tools to identify optimizations and measure on different types of devices. You can check out the entire talk on YouTube here.
Here at Ionic, we’ve known for years that cross-platform apps provide the performance and experience that users expect from a mobile app. In a recent blog post on performance with Ionic and Capacitor, analysis showed that performance metrics exceeded Lighthouse standards, even when running a video streaming application.
Colin Gray, principal developer at Shopify, also talked about performance and the journey of moving Shopify’s native iOS and Android apps to React Native in this talk “Default to Performance.” He shared techniques for measuring performance, as well as performance best practices for state management, React hooks, and using components with built-in performance enhancements. You can view his talk on YouTube here.
Both of these talks showcased the performance capabilities of cross-platform apps – an important takeaway at Chain React. Get started building your own performant cross-platform apps using Capacitor by learning more here.
Mobile deployments aren’t easy, and deploying cross-platform to Android and iOS makes it even tougher. Another trend at Chain React was how automation and tooling can help with the complexity of mobile deployments.
Cecelia Martinez from the Appflow team (hi, that’s me ) covered how to incorporate automation into the
deployment process in “Signed, Sealed, Deployed: Shipping React
Native Apps.”
The talk walks through the entire process of shipping a React Native app, including configuration, building, testing, uploading to app stores, and even maintaining your app.
It also included how Appflow, the mobile CI/CD platform built by Ionic, can help you automate deployments. Appflow takes care of the more complex aspects of mobile deployments, including signing certificate and build stack management.
Check out the full talk on YouTube here, and get started for free with Appflow today.
Finally we come to one of the newest and most exciting emerging trends in mobile development from Chain React: Superapps.
Superapps let you integrate multiple different services or mini apps – developed and managed separately – into a single user interface. Michal Pierzchala, head of technology at Callstack, discussed how superapps can be a boon for developer autonomy and productivity in his talk “Scaling teams with federated superapps.”
In his talk, he covered the organizational issues that exist for large teams that superapps can address. These include ownership conflicts, interdependent release schedules, and shared deployment resources. Superapps allow teams to build and ship independently so they can move faster for a better developer and user experience. Michal’s talk focused on Re.Pack, a Webpack-based toolkit for superapps on React Native, built by Callstack.
Ionic’s solution for superapps, Portals, allows developers to build superapps for native Android and iOS, as well as React Native. Portals provides secure, standardized tooling for integrating web mini apps into native superapp, so developers can move fast without compromising on user experience or app performance. Get started with Portals here for your own superapp.
Capacitor developers aren’t left out either – they can use Federated Capacitor to build a new superapp or modernize an existing Capacitor application. Learn more about Federated Capacitor in the blog post here.
Check out Michal’s full talk on YouTube here.
These key trends and takeaways from Chain React show that cross-platform apps are the future of development. Leveraging the best of both mobile and web is key to building performant apps, deploying them quickly, and scaling your development teams fast with superapps.
Ionic is leading the way on all these mobile development trends with solutions for every type of team, so make sure to stay up-to-date on everything Ionic to leverage the latest and greatest for your own apps.
The post Mobile development trends from Chain React appeared first on Ionic Blog.
Read more https://ionic.io/blog/mobile-development-trends-from-chain-react
This is a guest post written by Grgur Grisogono, Director of Engineering at Modus Create.
Micro frontends have been rapidly gaining popularity in the development of modern web applications. However, while micro frontends offer several benefits, including improved scalability, agility, and faster development cycles, they also come with several security challenges. In this article, we will explore common micro frontend security issues for the web and hybrid mobile apps.
One of the biggest benefits of micro frontends is democratized development, with teams getting to choose their own dependencies. As an application team’s digital footprint grows, naturally, two or more apps will eventually share dependencies but in different versions. While modern runtimes like the ones shipped with Module Federation will have no problem dealing with versioning discrepancies, mismatches can be a major flaw of micro frontends.
In a simpler scenario, two micro applications could use different major versions of the same library. In that event, most runtimes will choose to load both versions, respectively. While this will work fine in many cases, the system is clearly not optimized and may execute vulnerable code from the outdated library. Micro frontends don’t have a straightforward upgrade path mechanism, so teams need to figure out how to stay up to date collectively.
This third scenario has an interesting twist, making it far more complex. Suppose the shared library is a singleton, meaning only one version can be loaded simultaneously (e.g., React, Styled Components). In that case, we no longer have the luxury of loading different versions in independent sandboxes. Instead, the first version loaded stays active and reused across the stack. Most singletons will break, requiring all micro frontends to run the same version. Libraries with excellent backward compatibility will work fine, but these are rare.
Running the same version across the stack wouldn’t be a significant setback had it not been for the maintenance issues. Unfortunately, updating such a library can be incredibly difficult because all micro frontends must be updated simultaneously, which is sometimes impossible without causing problems for app users.
Unfortunately, there isn’t a universal technical solution to this. The best advice is to avoid singletons and resort to the standards. Leverage your client’s powerful browser to the greatest extent possible.
Another helpful tip is to implement semantic versioning for your micro frontends. Versioned apps can help teams understand the level of changes between two deployments.
A more complex approach to managing conflicting dependencies is to integrate a custom dependency manager (i.e., a global lock file). Your build step can record and compare dependencies with other apps in the system and suggest alternatives where applicable.
Authentication in hybrid mobile apps is usually a part of the native code since there are no callback URLs in SSO. As discussed at my Building Superapps in Mobile talk at Micro Frontends Summit 2023, it’s common for apps to create secure storage for the authorization token on the native side but then provide that token for the JavaScript code to communicate with a backend. This is already an improvement from the regular mobile web, as secure storage on the native side is superior to the browser capabilities.
However, a malicious attacker can tap into the JavaScript code to access shared tokens. A safer solution is to let the native side of the app communicate with the server. While implementing and maintaining such a bridge comes at a cost, it ensures that sensitive tokens are never accessible to interpreted code.
In other words, the native application shell serves as an asynchronous service to the UI, similar to microservices. Many organizations bank on that service to secure other sensitive data.
One of the most critical (yet awkward) recommendations for micro frontend architects and engineers is to avoid inter-app communication at all costs. It comes naturally to many developers to create service points for sharing data, making it sound like a ridiculous best practice. However, as your application scales, it will undoubtedly run into severe issues if you don’t isolate apps.
Since micro frontends sport at least some independent processes like the build step, deployment, test suites, or infrastructure, there are multiple points where potential attackers could sneak in. Implementing a zero-trust policy across the board will help mitigate such issues.
One way to improve trust policies is introducing Cross-Origin Resource Sharing (CORS) and Content Security Policy (CSP) headers in places such as:
If your micro frontends are loaded from different domains or
subdomains, you will want to have at least some of the policies
mentioned above in place. However, if you don’t care for such
security hardening, then at least set the
Access-Control-Allow-Origin
CORS header to
“*
” because that will avoid opaque responses. Opaque
responses misreport response size and some headers, which can
create issues with caching and even crash mobile browsers when the
browser cache size is exceeded.
For isolation to work, micro frontends should be deployed to predictable domains. CSPs work best when Frontends have respective subdomains at the cost of maintenance, especially when there are many apps to integrate.
In addition to isolating communication, it’s a good idea to enforce a zero-trust build step where any outbound communication is restricted. That helps create solid end-to-end isolation.
Micro frontends should generally implement the same security protocols as any web application. Even though micro frontend architecture is complex, it doesn’t bring significant security challenges by design. More so, they promote security by organizing business logic into independent, self-contained modules that can be secured autonomously.
The post Best Practices for Building Secure Micro Frontends appeared first on Ionic Blog.
Read more https://ionic.io/blog/best-practices-for-building-secure-micro-frontends
Ioniconf, the event that brings together some of the most influential names in the Ionic community, is back! And this year- it’s in person.
As much as we love hearing “can everyone see my screen?” at the start of every virtual meeting, we figured that we’re all ready to meet up live and talk about all things Ionic. From what’s coming on the product roadmap to how some of the best developers are using Ionic, you are not going to want to miss this event. So pack your bags, charge your laptops, and get ready to join us in person as we celebrate the 10th anniversary of Ionic in style.
Join us in Austin, TX at the ZACH Theatre on October 10th and 11th for this epic two-day conference. These action-packed days will be filled with top-notch talks, amazing networking opportunities, and more Ionic knowledge than you can fit in a 10-gallon hat. We’re gathering the hottest names in the space to share their expertise, best practices, and latest techniques that will take your mobile app development skills to the next level. We’re talking real-world insights, practical tips, and a lot of inspiration.
And that’s not all– we’ll be taking a deep dive into the cutting-edge features and tools offered by Ionic. Uncover the secrets to harnessing these advancements and turbocharge your app development process to deliver extraordinary user experiences.
As with past Ioniconf’s, we want to hear from YOU and give you a chance to share your story. Want
to share your experience in getting your app to market? Have a cool
JavaScript library that you think others should know about? Or are
you just building some seriously cool stuff? Submit
your talk on Sessionize for your chance to be a speaker at
Ioniconf 2023.
While this conference brings together amazing minds from around the community, we didn’t want your taste buds to feel left out. We’re bringing iconic Austin food trucks to serve up some seriously delicious eats. Because let’s face it, coding on an empty stomach is just not cool.
Enjoy mouthwatering flavors while you mingle with fellow developers who share your passion for building incredible apps. It’s the perfect recipe for both professional growth and a happy tummy!
Tickets are available now, and early bird pricing is only available for the first 100 tickets purchased- so if you want to stop reading and just get those tickets asap, we totally understand. If you want to learn more about the event, you can check out the website for more information.
Ioniconf 2023 is shaping up to be an unforgettable celebration of the Ionic community and its achievements over the past decade. We say it all the time, but it’s true – we owe so much to the amazing community of developers that are constantly helping us iterate and improve on all things Ionic. This event is a celebration of that community, and we can’t wait to hang out with you all in beautiful Austin, TX.
The post Join us at Ioniconf 2023! appeared first on Ionic Blog.
Read more https://ionic.io/blog/join-us-at-ioniconf-2023