Masterclass for Tech Accelerator, High Potential Teams

Introduction to the Create Apps Championship

Welcome and Overview

• Carmen Mateos introduces the master class on applying to the accelerator program, welcoming participants.

• The Create Apps Championship is an initiative by the Dubai Chamber of Digital Economy, now in its third edition, aimed at promoting digital innovation and mobile app development in Dubai.

• Participants include international teams as well as local UAE teams, highlighting a diverse global interest in the competition.

Purpose of the Master Class

• The session aims to clarify prerequisites and expectations for acceptance into the accelerator program.

• Emphasis on helping teams understand what is required to prepare effectively for their application and demonstrate readiness for launching their projects.

Application Process Details

Timeline and Expectations

• The master class takes place on February 2nd; participants have until February 13th to complete their submissions.

• Teams will receive guidance on requirements needed for eligibility in the accelerator program.

Introduction of Tech Team

• Fawas, tech accelerator lead, is introduced along with Antoan from the tech team who will assist throughout the process.

Accelerator Program Insights

Goals and Support Offered

• Fawas emphasizes that all processes are designed to help participants succeed with their ideas through structured support.

• An interactive approach is encouraged during discussions, allowing participants to ask questions freely.

Program Structure

• Overview includes an icebreaker followed by detailed discussions on eligibility criteria and how to submit applications effectively.

Mentorship and Development Focus

Key Features of Accelerator Program

• The program focuses on one-to-one mentorship, coaching, and hands-on technical support over a 45-day roadmap aimed at turning ideas into reality.

• Participants will receive guidance on publishing apps within this timeframe while addressing various challenges collaboratively.

Housekeeping Rules

• Attendees are reminded to keep microphones muted for focus but can raise hands or speak when necessary.

Understanding the Accelerator Program

Introduction to Q&A Session

• The chat is open for questions and answers indefinitely, encouraging participants to engage while respecting others' space.

• Participants are invited to scan a QR code or visit menty.com to share the current stage of their app ideas.

Collecting Responses

• A brief pause is given for participants to submit their responses, with anticipation for collective results.

• Clarification on addressing specific questions during the session is provided, ensuring all inquiries will be answered as time allows.

Overview of Selected Teams

• 24 teams were selected as semi-finalists based on high potential, with an invitation extended to 170 top teams for the accelerator program.

• Emphasis on pushing beyond just having an idea; teams need to demonstrate commitment and development in their projects.

Insights from Participant Responses

• Results show that 25% of participants have only an idea, while 38% report being half-built and 23% are currently testing their apps. This indicates varying stages of readiness among teams.

• Having only an idea without wireframes or user journeys poses challenges in the accelerator context; more detail is required within two weeks.

Defining "Half-Built" Apps

• "Half-built" can refer to incomplete MVP features or infrastructure; clarity on what constitutes this status will be established moving forward. Testing can involve technology or concept validation, which is seen positively by facilitators.

Eligibility Criteria for Participation

Key Requirements

• Apps must not be live at the start of the program; any version released should not include iOS or Android launches yet. Prototypes must be actively developed rather than stagnant projects from the past.

• Time commitment is crucial—participants should allocate a minimum of three hours daily or twenty hours weekly throughout the program duration starting March first week onward. This ensures adequate support and collaboration opportunities with mentors and coaches.

Financial Considerations

• Participants are not responsible for coaching fees but may incur costs related to development infrastructures (e.g., developer programs for iOS/Android). Specific tools like Azure credits may also be necessary depending on app features being developed (e.g., LLM capabilities).

Application Development Insights

Importance of Infrastructure and Commitment

• The development process for iOS and Android requires real data and live environments, emphasizing the need for proper infrastructure that must be funded by individuals or teams.

• A strong commitment to launching an app within 45 days is crucial; this should not be treated as a trial but rather as a definitive goal.

Application Submission Process

• Participants will receive a link to access the application submission form, where they can begin entering their app details.

• Key components required during submission include the app name, video pitch deck, team composition, and contact information for the team lead.

Team Composition and Technical Expertise

• It's essential to specify the technical level of the team; developers should ideally work in a proper development environment rather than relying solely on no-code solutions.

• Teams must indicate their size, nationality, and specific roles within the project to clarify accountability during the accelerator program.

App Description and Core Functionality

• A concise app description (1-2 lines) is necessary to convey its purpose clearly. Competitor analysis can help refine this description.

• Detailed descriptions of core functionalities are important; participants should focus on what features will be included in their MVP (Minimum Viable Product).

MVP Features and Feasibility

• Teams should identify which features will be part of their first version while ensuring these can realistically be developed within 45 days.

• Current MVP status may vary from web apps to basic mobile implementations; clarity on what is feasible is critical for success.

MVP Development and Technical Considerations

Defining Your MVP

• Discuss the importance of clearly describing your Minimum Viable Product (MVP) and its working features, emphasizing the need for a detailed tech stack flow.

• Highlight the choice of development tools such as Flutter, React Native, Glide, or others, stressing that it's about personal choices rather than just available options.

Current App Progress Overview

• Stress the significance of transparently detailing how much of the app is built to assess current conditions realistically.

• If the MVP isn't functional yet, outline execution plans for the next 30 days to demonstrate commitment to progress.

Technical Details and Platform Requirements

• Clarify whether the app will be developed for Android, iOS, or both; recommend having a dedicated team if choosing both platforms.

• Mention the necessity of having an Android publisher account and provide evidence through screenshots showing account details.

Access and Permissions Management

• Discuss access control for testing purposes without sharing login credentials; emphasize providing necessary permissions while being aware of privacy policies.

• Explain that certain permissions (camera, storage, microphone) may require reworking to avoid future challenges with app store approvals.

Understanding Platform Expectations

• Acknowledge that Android has a 14-day closed testing period while iOS requires a stable user flow; highlight potential issues with no-code environments in meeting these requirements.

• Encourage creating a prototype walkthrough video (max 2 minutes), focusing on MVP features rather than pitching ideas.

Commitment to Iteration and Accountability

• Emphasize the need for ongoing updates post-launch and preparing necessary documentation like privacy policies and terms & conditions.

• Stress accountability in coaching sessions and taking ownership of delays or blockers encountered during development.

Planning Ahead

• Recommend reflecting on upcoming schedules or events that could impact project timelines to ensure all parties are aware when planning.

Understanding the Application Development Process

Importance of Engagement and Context

• The speaker emphasizes the need for engagement with the audience, indicating a desire to connect and clarify concepts related to application development.

• Acknowledges questions from participants, encouraging them to mark or chat their inquiries for later discussion.

Introduction to Just Life as a Case Study

• Introduces "Just Life," a digital platform designed as a one-stop shop for home needs, highlighting its relevance in the context of Minimum Viable Product (MVP) discussions.

• Describes "Just Life" as a super app that has evolved by addressing real-time user needs within the mobile app economy.

Team Dynamics in Application Development

• Discusses team size and roles, asserting that innovation is possible even as a solo founder but emphasizes the importance of what can be achieved within 45 days.

• Encourages solo founders to consider their commitments and capabilities in various roles such as infrastructure developer or tester.

Role Clarity Among Team Members

• Stresses the significance of defining roles among co-founders during project development phases, particularly over short timeframes like 25 to 45 days.

• Highlights how early-stage teams at "Just Life" were small yet focused on critical functions like service flow engineering and operations management without in-house providers.

Identifying Problems Your App Solves

• Prompts participants to articulate what problem their app addresses succinctly, fostering creativity and clarity in problem-solving approaches.

Exploring Motivations Behind Participation

Insights into Industry Trends

• Participants express motivations related to loneliness and mental well-being, identifying these issues within the broader context of companionship industries emerging in app economies.

Focus Areas for Future Development

• Mentions various sectors gaining attention such as edtech, prop tech (property technology), financial management, language barriers, teen development, maternal mental health, autism awareness, wellness industries, and cashless economies.

Cashless World and Fintech in the UAE

Importance of MVP in Problem Solving

• The speaker emphasizes the significance of developing a Minimum Viable Product (MVP) within 45 days to address pressing issues, highlighting that even small steps can lead to substantial solutions.

• The focus should be on defining what problem your MVP will solve, which reflects the next steps necessary for progress and innovation.

Defining Your MVP Features

• An MVP should clearly outline its initial features; for instance, it may only include specific service categories like cleaning services to streamline user experience.

• Certain functionalities such as payment splitting or advanced cash handling are excluded from the MVP due to potential legal challenges with payment gateway integration.

Limitations and Considerations for Your MVP

• Loyalty programs and advanced personalization features are not part of the initial MVP since they require a stable market supply before implementation.

• The definition of an MVP is tied closely to understanding both the problem being solved and the capabilities of your team.

Execution Strategy for Development

• A successful execution plan involves having dedicated roles such as execution owners who manage technology access, ensuring accountability throughout development.

• Transparency in what has been built so far is crucial; sharing wireframes or user flows can help clarify current app status.

Preparing for Accelerator Participation

• Participants are encouraged to detail their partially working apps, including any evidence of work completed thus far, which could enhance their chances in an accelerator program.

• If an MVP is not functional yet, it's essential to articulate a clear execution plan over the next 30 days focused on technological feasibility rather than redefining business models.

Engagement and Commitment from Participants

• The speaker encourages audience engagement through QR code scanning as a commitment step towards participation in the accelerator program.

• A personal recommendation is made for participants without developer accounts to create one immediately, emphasizing its importance in today’s competitive app publishing landscape.

Creating an App: Essential Steps and Considerations

Setting Up Your Developer Account

• To begin your app development journey, create a developer account. This requires setting up a Gmail address and completing necessary validations, which may vary by country.

• The process is crucial for realizing your dream of app creation, emphasizing the importance of preparation in areas like privacy policy and terms of service.

Importance of Legal Documentation

• Having essential documents such as privacy policies and terms of service is mandatory; without them, your app will not be accepted on platforms like iOS or Play Store.

• Quality assurance is vital to avoid issues like online scams; clear policies help maintain trust with users.

Technical Requirements for App Development

• Specific technical requirements must be met based on the nature of your app. For instance, an autism-related app required physical servers for video storage before going live.

Break Time Reflection

• A brief 5-minute break was encouraged to refresh before continuing with the session's content.

Evaluating Your App Idea: Key Areas to Focus On

Understanding Evaluation Criteria

• Evaluation should focus on progress rather than judgment. It’s about improving ideas over time.

• Three main areas are emphasized: feasibility (can it be achieved in 45 days?), clarity (is the idea well-defined?), and fit (does it align with personal capabilities?).

Assessing Feasibility and Fit

• Feasibility involves assessing whether you have the resources and plan to develop your product within a set timeframe.

• Fit refers to personal commitment and motivation; if you lack expertise or resources in mental wellness but want to develop an app in that area, it may not be feasible.

Engaging with Technology Tools

• Participants were invited to engage in a feasibility activity using QR codes that lead to testing their project ideas through an AI-powered platform.

This structured approach provides clarity on critical steps involved in developing an application while highlighting essential considerations regarding legal documentation, evaluation criteria, and resource management.

Getting Started with the App

Navigating to the Test Page

• The speaker encourages participants to take their time exploring the app and clicking on relevant options based on their coding experience.

• A link is provided in the chat for those who couldn't scan a QR code, ensuring everyone can access the necessary resources.

Inputting Experience and Platform Selection

• Users are instructed to click "start test," input their app ID, and indicate their coding experience level (non-technical, beginner, intermediate, or expert).

• Participants must select which platform they are targeting: iOS (Apple), Android (Samsung), or both. The speaker focuses on iOS for their project.

Describing AI Features

• After selecting a platform, users should describe any desired AI features for their app. The speaker mentions wanting a chatbot for support and recommendations.

• Examples of chatbot functionalities include providing equipment recommendations based on user roles (e.g., goalkeeper needing gloves).

Generating Roadmap

• Due to high participant numbers, there may be delays in generating roadmaps; users are advised to re-log if issues arise.

• The roadmap generation process is explained as being queued first come first serve; patience is encouraged while waiting.

Feedback and Q&A Session

• The tool used is designed specifically for participants to understand their project better through feedback analysis.

• As roadmaps generate, participants are invited to ask questions during a Q&A session about feasibility testing or other concerns.

Funding and Support for Tech Acceleration

Overview of the Program and Funding Opportunities

• The discussion begins with inquiries about the acceleration program's structure, specifically regarding achieving goals within 45 days.

• There is a request for information on potential funding opportunities or investor rounds to support app development in Dubai.

• The tech accelerator aims to provide technical support for launching a Minimum Viable Product (MVP) within the specified timeframe.

• Additional support is available through the Create App Championship, which offers mentorship and guidance to semi-finalists aiming to further develop their apps.

• The Dubai Chamber of Digital Economy can assist with business setup and various programs that offer mentorship and funding.

Organizing Support Calls

• A suggestion is made to organize a call with the Dubai Chamber team to discuss available support options in detail.

• Participants are encouraged to reach out via email for assistance in connecting with relevant teams that can provide necessary support.

• Acknowledgment of common concerns among participants regarding funding needs as they work on app development in Dubai.

Prototype Development Flexibility

• A question arises about whether prototypes must remain unchanged from initial submissions or if adjustments can be made before the February deadline.

• Clarification is provided that improvements are allowed, especially if they enhance viability within the 45-day timeline for MVP development.

• Participants are encouraged to make changes to navigation and user flow as long as they align with the original concept of their application.

Focus Areas for MVP Features

• Emphasis is placed on showcasing user experience in the MVP while maintaining essential business operations within constraints.

• It’s advised that teams focus primarily on MVP features rather than attempting to cover all aspects of business operations initially.

• The goal of the accelerator is not just theoretical but practical; successful completion leads towards market readiness, including trade licensing and potential funding opportunities.

Tech Incubation and MVP Development

Focus on Minimum Viable Product (MVP)

• The evaluation process emphasizes the importance of developing a minimum viable product that is publishable as part of the accelerator program.

• Post-publication, participants will be connected with relevant communities and programs under the governance of Dubai Chamber to support their startup journey.

• While technology prototyping is crucial, founders must also focus on making their startups successful beyond just app development.

Questions About Prototype Resubmission

• Participants can resubmit information or improve their prototypes without changing the core idea during the resubmission phase.

• Technical assistance is not available at this stage; improvements should be made independently by participants.

Eligibility Concerns for Published Apps

• A participant inquired about eligibility after publishing an app prior to the competition, despite it being a test version with minimal downloads.

• Clarification was provided that if the app was publicly published and met certain criteria, they could still participate in the competition.

Guidance for App Improvement

• Participants are advised to communicate specific details regarding their apps to clarify eligibility concerns with the organizing team via email.

• It’s recommended that participants reflect on any changes or improvements before submitting their applications again.

Feedback and Selection Process

Addressing Concerns from Young Entrepreneurs

• A young entrepreneur expressed frustration over not advancing to semi-finals despite having a ready MVP, seeking clarity on selection criteria.

• Due to high application volume, individual feedback cannot be provided; selections were based on scoring and judging criteria.

Encouragement for Future Applications

• The panel encouraged maintaining a positive outlook despite not advancing, emphasizing that this experience can lead to better opportunities in future competitions.

• They highlighted that completing applications effectively can enhance entrepreneurial skills and prepare participants for future endeavors.

App Development Guidance and Accelerator Program

Questions on App Development Process

• A participant inquires about the next steps for their app, which is currently in the high potential team phase. They ask whether to develop their idea using Figma or move into technical development due to a lack of development knowledge.

• The participant mentions that their app has two user flows: one for users and another for service providers, seeking advice on how to proceed with developing an MVP (Minimum Viable Product).

Clarification on Outsourcing and Development Expectations

• The response clarifies that outsourcing is not required before application submission; having a fully developed product is not necessary for eligibility.

• Emphasis is placed on coaching and mentoring rather than building the app entirely for them. The importance of having a technological member in the team is highlighted as it can expedite development.

• The speaker explains that while they will provide support, ownership of the project remains with the participants. Having a tech person can enhance scalability and speed up feature implementation.

Co-development Approach

• Participants are encouraged to view their relationship with the accelerator as co-development rather than outsourcing. Milestones will be set weekly during a 45-day period if selected.

• There will be ongoing support from mentors, including troubleshooting issues like crashing features during testing phases.

Distinction Between Programs

• A participant seeks clarification regarding different paths within the program: semi-finalists competing for funding versus those entering the tech accelerator without access to funding prizes.

• It’s confirmed that only announced semi-finalists can compete for funding, while others can still benefit from guidance through the tech accelerator program aimed at launching an MVP within 45 days.

Technical Partnerships and Requirements

• A final question arises about collaborating with local departments (e.g., UAE Pass). The need for proper contacts to facilitate this integration into their app is expressed.

• The response indicates that partnerships are possible but require pre-eligibility criteria such as being locally registered and having access to necessary APIs.

• It’s noted that once officially registered as a trade entity, accessing services like UAE Pass becomes straightforward, emphasizing regulatory compliance as essential.

Technological Integration in App Development

Importance of API Services

• The app requires integration with the Dubai Land Department's services, specifically through an API called Hijari, which manages land lease agreements.

• Access to the Hijari API is contingent upon being a registered entity, emphasizing the need for eligibility before integration can occur.

Prototype Submission Guidelines

• Participants are encouraged to submit either the same pitch or a new one; however, focus should be on presenting a prototype within a two-minute limit.

• Clarity and conciseness are crucial; improvements to existing pitches are welcomed but not mandatory.

Wireframe vs. Prototype Clarification

• A question arises regarding the difference between wireframes and prototypes; participants seek guidance on submission requirements.

• Submissions should include user flow diagrams or wireframes that detail application functionality while maintaining confidentiality for evaluation purposes.

Evaluation Criteria for Accelerator Selection

• Winning teams will be evaluated based on feasibility, commitment over 45 days, and clarity of purpose—these factors will determine selection for advancement in the accelerator program.

• The feasibility assessment includes reviewing prototypes and wireframes submitted by teams as part of their commitment demonstration.

Post-MVP Support Inquiry

• Selected teams may receive additional coaching and advice post-MVP development to enhance their applications further.

• Emphasis is placed on maximizing support if teams can deliver their MVP ahead of schedule, encouraging proactive engagement during the accelerator phase.

Tech Accelerator Insights

Focus on iOS and MVP Development

• The current roadmap emphasizes the Swift programming language for iOS users, recommending a platform-specific approach for MVP development within 45 days unless a scalable team is available for both platforms.

Deadline and Financial Support

• The deadline for submitting entries to the tech accelerator is February 13th.

• There will be no financial support or funding provided during the accelerator; participants must explore funding opportunities independently.

Self-Funding Requirement

• All expenses related to launching the MVP must be covered by participants, as stated in the commitment letter that participants will sign.

• The program offers technical support but does not provide any financial intervention or assistance with costs associated with launching an MVP.

Investor Connections and Program Goals

• The primary goal of the tech accelerator is to provide technical support rather than business model reviews or financial forecasting.

• Participants may receive guidance on connections within Dubai's Chamber of Digital Economy but should not expect direct investor meetings during this phase.

Challenges in Fintech Startups

• A participant expresses concerns about their fintech startup's complexity due to regulatory requirements, needing multiple approvals from entities like IFC and QIC.

• It’s emphasized that fintech is heavily regulated, especially when involving blockchain or crypto features, necessitating local registration and compliance with regional regulations.

Regulatory Considerations for MVP Development

• Achieving an MVP in fintech requires navigating significant regulatory hurdles; without proper licensing, certain features cannot be implemented.

• The program can assist in identifying an MVP that fits within regulatory frameworks but cannot expedite approval processes with government authorities.

Presentation vs. Market Readiness

• Participants are encouraged to view their MVP as a presentation tool rather than a fully functional product aimed at customer acquisition.

• While presenting ideas through an MVP is valuable, having investment backing remains crucial for market entry beyond initial presentations.

Discussion on Technical Team and Accelerator Program

Importance of a Technical Team

• The speaker emphasizes the necessity of forming a technical team to achieve project milestones, particularly in a highly regulated industry.

• They offer assistance in identifying required skills for the team and suggest mentoring or coaching during the hiring process.

Milestones and Goals

• Achieving specific milestones is crucial; merely forming a tech team is not sufficient. The focus should also be on developing an MVP (Minimum Viable Product).

• The primary goal is to complete a 45-day roadmap, with ongoing support provided throughout the process.

Application Submission Deadline

• Clarification is given regarding the application deadline for the accelerator program, which is set for February 13th. This date marks when applications must be submitted, not when apps will go live.

• Once selected, participants will work closely over 45 days to launch their MVP.

Questions from Participants

• A participant asks if they need to submit an MVP product by February 13th; clarification indicates that only a clearly defined MVP feature list is necessary.

• Transparency about current build status (e.g., idea scoped or developed) is encouraged in applications.

Accessing Application Forms

• Information about where to find application forms is shared; links are provided in chat and via email due to some technical issues faced by participants.

Benefits of Participation in Accelerator Program

• A question arises regarding benefits beyond mentorship for teams capable of launching independently within 45 days. The response suggests that recognition may be limited if teams already possess necessary skills.

• Emphasis on how this program primarily supports those needing guidance rather than those who can deliver without assistance.

Support Offered During Accelerator Program

• Clarification on how selected teams will receive hands-on training, mentorship, and access to resources during their time in the accelerator program.

Create Apps Championship Overview

Support and Resources for Participants

• The technical team will provide support to ensure the success of the app, which will be showcased at the finals as part of the Create Apps Championship.

• Participants will not receive funding for prizes in the semi-finals but will have access to resources and mentorship during the program.

• Being selected as a high-potential team is an achievement worth celebrating, highlighting visibility among attendees at the final showcase.

Clarifications on Participation

• Questions about invitations to Dubai or showcases for all 36 accelerator teams are addressed; expenses for attending finals must be covered by participants themselves.

• All costs associated with attending the finals are borne by participants, emphasizing financial responsibility.

Technical Development Queries

Migration and Platform Compatibility

• A participant inquires about migrating their prototype from a logical platform to Android or iOS, indicating that their application is fintech-related.

• The use of no-code solutions is discussed as a way to avoid licensing issues while transitioning platforms.

Technical Feasibility and Requirements

• It’s confirmed that migration from Lavable (a no-code platform) to Android is possible but requires creating a mobile front-end due to specific regulations on no-code environments.

• Developers may need additional subscriptions if they want full functionality when moving from Lavable to Android, including compliance with Play Store requirements.

Support Structure During Accelerator Program

Coaching and Guidance Offered

• Selected teams can expect structured support through mandatory coaching calls tailored to individual progress and milestones throughout the program.

• Mentorship includes live problem-solving sessions where dedicated mentors assist teams in overcoming challenges related to their applications.

Focus Areas of Support

• While technical aspects are prioritized, there is flexibility in exploring other areas if teams advance beyond initial expectations.

• Teams without back-end developers can utilize services like Appite or Firebase for database management, emphasizing solution-oriented approaches over personnel availability.

Discussion on Team Roles and Program Details

Clarification on Team Structure

• The speaker emphasizes the importance of addressing deficiencies within the team, indicating a focus on improvement and collaboration.

• A participant inquires about the possibility of changing team roles, particularly the team leader, due to personal commitments such as children's school schedules.

• The response confirms that roles can be adjusted, highlighting flexibility in leadership based on individual circumstances and expertise.

Communication and Application Process

• There is a discussion about ensuring all team members receive important communications; participants are encouraged to provide their email addresses for updates.

• Participants are reminded they have until February 13th to submit applications for the tech accelerator program, with instructions to modify submissions as needed.

Resources and Support

• The speaker reassures participants that any remaining questions can be addressed via email or through an active forum, promoting ongoing support.

• A video recording of the session will be available for review on the Create Apps Championship platform, allowing participants to revisit discussions.

Final Remarks and Encouragement

• Participants are encouraged to check FAQs and utilize a chatbot for additional queries, reinforcing resource availability.

• The speaker expresses gratitude for participation and wishes everyone success in their submissions before the deadline.

Closing Sentiments

• A final message conveys encouragement regardless of outcomes (semi-finalist or high potential), emphasizing that this experience is a step towards realizing dreams.