برچسب: Prepare

  • What 8 Years in Corporate Life Did — and Didn’t — Prepare Me For as a Founder

    What 8 Years in Corporate Life Did — and Didn’t — Prepare Me For as a Founder


    Opinions expressed by Entrepreneur contributors are their own.

    As a consultant, chaos was a problem I had to solve. As a founder, it’s the air I breathe.

    I entered the startup world armed with what I thought was the ultimate toolkit: a consulting background. Years of strategy decks, stakeholder management and cross-functional collaboration taught me how to turn chaos into structure and solve problems fast. I thought I had seen it all.

    But I quickly realized that the transition from consultant to founder wasn’t so much a pivot — it was a free fall. See, consultants and founders couldn’t be more different. Consultants are trained to be perfect, founders need to be scrappy. Consultants are trained to eliminate chaos, founders need to thrive in it. Consultants have a safety net, founders don’t.

    Related: Are You Ready to Be a CEO, a Founder or Both? Here’s How to Know

    Let’s dive right in.

    This is what consulting did prepare me for:

    1. Finding structure in chaos: I am stating the obvious here, but it is essential for founders to be able to execute on their vision; and to do that effectively, founders need structure. Something as simple as creating an organized folder structure — which coincidentally was my first task as an associate — can go so far as securing your term sheet with investors when they ask for the data room during the due diligence process. Being due diligence-ready isn’t just about having your documents in order; it’s about demonstrating transparency and building confidence with potential investors.
    2. Thinking on the spot: As a founder, it feels like you’re in the middle of the ocean and you need to swim your way back to shore. Consulting prepared me for that. I remember being chucked into remote environments to explain technical workflows to non-technical people — in my third language nonetheless. Thinking fast and adapting your message to whoever’s in front of you isn’t just useful — it’s how you create openings. It’s how you pitch before your product is ready. It’s how you get a meeting before there’s anything to show.
    3. Burning the midnight oil: Let’s be real, consultants — at least, the good ones — are machines and can be extremely productive. Founders are part of a world where being busy includes attending a lot of conferences, exhibitions and the post-event functions that come with them. Consultants can rarely afford such luxuries. Crunchtime is real and forces them to converge their efforts on work. Knowing when to lock in and say no is crucial as a founder.

    This is what consulting did not prepare me for:

    1. Building and failing fast: Most founders and visionaries fall into the fallacy of building an end-to-end super solution that promises to be the holy grail of their customers — myself included. Enter the pivots. Your startup does not succeed when it builds out your vision — that is often just a very expensive dream. It succeeds when you find out what your customers are willing to pay for as quickly as possible. As Eric Ries puts it in The Lean Startup, the key is learning what customers actually want – not what you think they should want.
    2. Storytelling as an art: In my first days as a founder, I walked into a potential client’s office long before I had a product or even a live website. I took the consulting route and brought a strategy deck with me. I got destroyed that meeting. Off the bat, it sounds like a mistake — but it was the best decision I could have made. I took note of the feedback and acted on them immediately. Get out there, pitch your idea and ask for feedback! Feedback helps you figure out what sticks, what doesn’t and how to sharpen your message until it cuts through.
    3. Learning how to network: I did more networking in my first year as a founder than I did during my eight years as a consultant. Let that sink in. I thought I was networking as a consultant, but I was really just moving within the same orbit. As a founder, the galaxy is yours to explore. From day one, you find yourself networking with fellow founders from all walks of life, angel investors, venture capitals, tech builders, community leads — you name it. And the best part is, they don’t care about your CV. They care about your energy, passion and convinction. A study by Queen Mary University of London found that the quality of a startup’s network significantly impacts its chances of success, often more so than initial funding or team size.

    Related: Are You Thinking Like a Founder? 4 Principles Every Successful Team Should Follow

    In the end, the transition from consultant to founder was less about applying what I knew and more about unlearning what I thought I knew. And if you’re willing to unlearn, embrace different perspectives, take constructive criticism, to be honest with yourself and to move fast without all the answers — you will find yourself growing in ways no corporate job could ever offer.

    As a consultant, chaos was a problem I had to solve. As a founder, it’s the air I breathe.

    I entered the startup world armed with what I thought was the ultimate toolkit: a consulting background. Years of strategy decks, stakeholder management and cross-functional collaboration taught me how to turn chaos into structure and solve problems fast. I thought I had seen it all.

    But I quickly realized that the transition from consultant to founder wasn’t so much a pivot — it was a free fall. See, consultants and founders couldn’t be more different. Consultants are trained to be perfect, founders need to be scrappy. Consultants are trained to eliminate chaos, founders need to thrive in it. Consultants have a safety net, founders don’t.

    The rest of this article is locked.

    Join Entrepreneur+ today for access.



    Source link

  • Prepare your apps for Google Play’s 16 KB page size compatibility requirement



    Posted by Dan Brown – Product Manager, Google Play

    Google Play empowers you to manage and distribute your innovative and trusted apps and games to billions of users around the world across the entire breadth of Android devices, and historically, all Android devices have managed memory in 4 KB pages.

    As device manufacturers equip devices with more RAM to optimize performance, many will adopt larger page sizes like 16 KB. Android 15 introduces support for the increased page size, ensuring your app can run on these evolving devices and benefit from the associated performance gains.

    Starting November 1st, 2025, all new apps and updates to existing apps submitted to Google Play and targeting Android 15+ devices must support 16 KB page sizes.

    This is a key technical requirement to ensure your users can benefit from the performance enhancements on newer devices and prepares your apps for the platform’s future direction of improved performance on newer hardware. Without recompiling to support 16 KB pages, your app might not function correctly on these devices when they become more widely available in future Android releases.

    We’ve seen that 16 KB can help with:

      • Faster app launches: See improvements ranging from 3% to 30% for various apps.
      • Improved battery usage: Experience an average gain of 4.5%.
      • Quicker camera starts: Launch the camera 4.5% to 6.6% faster.
      • Speedier system boot-ups: Boot Android devices approximately 8% faster.

    We recommend checking your apps early especially for dependencies that might not yet be 16 KB compatible. Many popular SDK providers, like React Native and Flutter, already offer compatible versions. For game developers, several leading game engines, such as Unity, support 16 KB, with support for Unreal Engine coming soon.

    Reaching 16 KB compatibility

    A substantial number of apps are already compatible, so your app may already work seamlessly with this requirement. For most of those that need to make adjustments, we expect the changes to be minimal.

      • Apps with no native code should be compatible without any changes at all.
      • Apps using libraries or SDKs that contain native code may need to update these to a compatible version.
      • Apps with native code may need to recompile with a more recent toolchain and check for any code with incompatible low level memory management.

    Our December blog post, Get your apps ready for 16 KB page size devices, provides a more detailed technical explanation and guidance on how to prepare your apps.

    Check your app’s compatibility now

    It’s easy to see if your app bundle already supports 16 KB memory page sizes. Visit the app bundle explorer page in Play Console to check your app’s build compliance and get guidance on where your app may need updating.

    App bundle explorer in Play Console

    Beyond the app bundle explorer, make sure to also test your app in a 16 KB environment. This will help you ensure users don’t experience any issues and that your app delivers its best performance.

    For more information, check out the full documentation.

    Thank you for your continued support in bringing delightful, fast, and high-performance experiences to users across the breadth of devices Play supports. We look forward to seeing the enhanced experiences you’ll deliver with 16 KB support.



    Source link