PolinaQuickbase
Quickbase Staff
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Mobile Phone - add picture
Hi there Chuck, Polina from the Quickbase Product team here. I’d love to learn more about the issues you ran into with the new forms. Would you be open to sharing more details? Any feedback you can provide would be incredibly helpful as we continue to refine and enhance the new forms experience.New Forms Are Now Live in Quickbase Mobile!
We’re excited to share that as of April 21, the new forms experience in Quickbase is now generally available on mobile! This launch marks a significant milestone in our mission to provide a seamless, consistent, and powerful experience to users—no matter where they work or what device they use. Why This Matters Historically, building for mobile in Quickbase presented a number of challenges. App Admins often had to create and manage separate legacy mobile forms to provide a usable experience on smaller screens. For end users, the experience was often inconsistent. Legacy mobile forms came with limited layout options, lacking the flexibility to organize content using columns, or tabs. Form rules and workflows sometimes behaved differently than expected, and key functionality—like viewing embedded reports directly on the form—wasn’t available on mobile at all. As a result, mobile usage often required workarounds, compromises, or shifting tasks to desktop, slowing down teams who needed to work when they were away from the desk— until now. One Form, Multiple Devices The new forms experience is now fully responsive. Builders can design a single form that automatically adapts to desktop, tablet, or mobile, with no extra configuration required. Whether users are approving invoices, pulling up customer contacts, submitting support cases, or updating project details, the experience is consistent and intuitive across the board. What’s New for Mobile Here are a few key enhancements you’ll notice right away: 🔹 Fully Responsive Form Canvas The layout automatically adjusts to the screen size and orientation, while maintaining the structure and design you built on desktop. Forms are organized with pages, sections, columns, tabs, and steps, and Quickbase automatically adapts the layout to fit the device's screen. For instance, on mobile devices, columns stack vertically to ensure optimal readability and usability. On tablets—especially in landscape mode—forms can display multiple columns side by side, taking full advantage of the larger screen and offering a more spacious, desktop-like layout. Additionally, tabs and steps help break down longer forms into manageable sections, making it easier for mobile users to navigate complex forms without feeling overwhelmed. Users can quickly swipe through form steps or tap between tabs, maintaining focus while completing tasks efficiently. 🔹 Optimized Field Interactions We’ve reimagined how field components work on mobile. From dropdowns to date pickers, every interaction is optimized to feel natural on a smaller screen, while retaining the power of the desktop version. For example, multiple-choice fields are presented in modals, allowing users to search and select options efficiently. 🔹 Dynamic Form Rules & Workflows Form rules and formulas now behave just as they do on desktop. We’ve been on a mission to eliminate the need for mobile-specific workarounds, and this update is a step forward. Dynamic form rules now apply across devices, so the logic you’ve built for desktop users works just as smoothly for those on the go. 🔹 Embedded Reports on Mobile For the first time, embedded reports are displayed directly on mobile forms, giving users real-time access to the related data they need to make decisions and take action on the go. While some functionalities like grid edit and exporting to CSV are not supported on mobile, users can view reports, search, add new records, edit or view individual records, and delete records, depending on their permissions. 🔹 Support for Custom Workflows New forms on mobile now support more advanced and flexible workflows. App admins can confidently use table-level settings like “Auto save when redirected away”, the custom CSS class SaveBeforeNavigating, and URL parameters such as ifv=1 and hs=1 to hide native Save and Cancel buttons. These tools enable customized navigation, smoother inline saves, and fully tailored form experiences—all while maintaining mobile compatibility. Assigning Forms for Mobile App admins can assign the latest, mobile-friendly version of forms to specific user roles using the "View/Edit/Add Form (Mobile)" column from Forms Settings, ensuring that users see the appropriate form on their mobile device. In some cases, assigning a simplified, mobile-specific form may be beneficial. It allows you to reduce friction, minimize cognitive load, and create a faster, more focused experience for users – especially for those who only need to complete a subset of fields or perform quick tasks on the go. Alternatively, if admins prefer to use the same forms across desktop and mobile, they can select “Use full site forms”. A Better Experience for Builders and End Users With this release, builders no longer need to build two versions of a form, and end users don’t have to adapt to a stripped-down mobile layout. The result? Faster time to value and more efficient teams. Ready to Get Started? If you’re already using new forms on desktop and you have selected the option “Use full site forms” for mobile, you don’t have to lift a finger—your mobile experience is ready to go. Just open your app in the Quickbase mobile app (version 1.68 and above) or browser and experience it for yourself. If you’re not using new forms on desktop yet, now is the perfect time to start. By switching to new forms, you’ll not only unlock a modern, flexible form-building experience on desktop—you’ll also ensure your app is mobile-ready. 💡 Want to learn more? Check out the full documentation: Assign forms for mobile Understand the form canvas and layout on mobile Form field types and components on mobile What’s Next The launch of new forms on mobile is a big milestone—but we’re not done yet. In the coming months, we’ll be rolling out additional capabilities including: QR/Barcode scanning Next/Previous record navigation, making it easier to move between records Timezone helper, and more!Re: Mobile app - Cookie issue
Hi bharathreddy, This is a known issue currently affecting both new Dashboards and new Forms (in beta) when embedding code pages or any Quickbase page, particularly in the mobile app (accessing this dashboard from any mobile browser should result in displaying the code page without an issue). The team is aware of the problem and has been actively working on a fix. We're expecting to roll out a solution soon, so please keep an eye on the Quickbase Release Notes for updates. In the meantime, while it's not ideal, a workaround I can suggest is to use a button to open the code page, rather than embedding it directly in the dashboard. This helps avoid the cookie-related error you're seeing in the mobile app. Thanks for your patience as we work to resolve this!Re: List of Majr Mobile Bugs - Add your own?
Hey Mike, I appreciate you taking the time to highlight the importance of these issues and to keep the Quickbase community aware. Ensuring a seamless experience for all our users is top priority for us and commitment, so I wanted to provide an update from our side. While we are actively addressing bugs in the mobile app in general, our current focus is on carefully prioritizing and fixing only the most critical issues related to the legacy forms experience. This approach allows us to allocate our resources efficiently as we work towards the launch of the new forms experience on mobile. By focusing on the development of the new mobile forms, we aim to provide a more robust and comprehensive solution that not only resolves current issues but also brings forth improved functionality and user experience, as well as long-waited feature parity with the desktop forms experience, thus bringing higher value to customers in the long term. In terms of the new mobile forms timeline I wanted to share a bit more context: In Q2 we are planning different beta opportunities, where smaller group of customers will be able to see and test the new mobile forms experience and share their feedback. We will open an expanded beta program in the second half of Q2 2024, where customers will be able to sign up from the Quickbase Beta Application (quickbase.com/beta) as usual. Once we have addressed the feedback from these programs, we plan on making the new forms experience generally available in Q3 2024. We genuinely appreciate our community's patience and understanding as we navigate through this process. We know that the new forms is a strongly desired mobile feature and we are committed to delivering an exceptional experience that will greatly benefit our users. I look forward to sharing further updates and progress with you in the coming months. ------------------------------ Polina Georgieva ------------------------------5 tips for building an effective mobile dashboard
Making accurate, data-informed decisions quickly, even while you are on the go, is critical for organizations seeking to become dynamic enterprises. To achieve this, you need to have the right data available to the right people, at the right time. Quickbase’s new mobile dashboards are designed with this in mind. With their dual functionality as a home page for your applications and a comprehensive reporting tool, the dashboards enable you to gather real-time visibility into your metrics and KPIs and in the same time trigger different workflows and actions anywhere and at any time. Same as any other Quickbase mobile feature, your desktop dashboards are automatically available on mobile without any additional building required. However, given the different context and needs when users are accessing information through Quickbase mobile while being on the go, we encourage app admins to create a separate dashboard for mobile devices. This way you will ensure that your users will always have access to the right information and actions, depending on their device. When it comes to building a dashboard for the mobile devices, it's important to keep in mind that users typically have limited screen space and attention span. It's quite easy to lose the balance between the amount of information displayed and an optimised user experience. To help you avoid overwhelming your users with data, in this blog post we'll discuss five tips for building effective mobile dashboards: 1. Know Your Target Users Before you start building your mobile dashboard, it's essential to know your target users and their goals. The dashboard should be designed with the end-users in mind, so it's best to start by understanding their needs and what information and data they need to achieve their goals. You can start with answering these questions: What is the person's role in the organisation? In what scenarios will this mobile dashboard be used? What data and metrics are most important to this role? How will the dashboard help them in their daily work? Once you have the answer to these questions, you will be able to define clear objectives for what you want to achieve with the dashboard and what content you should include. 2. Consider the real estate It's essential to optimize your dashboard for mobile devices. Understanding the device specifics is important so that we know what’s the best format that we can display data, how many widgets we can have easily accessible to the target users. Mobile screens are much smaller than desktop screens, so you need to design your dashboard with this in mind. For example, the limited mobile screen sizes aren’t ideal for in-depth analysis and drilled-down data. Instead, you should consider displaying information that is easily digestible, and actionable in a small screen format. Some examples that might be suitable for a mobile dashboard include: Utilizing charts, graphs, and visual elements that are better suited for small screens; Displaying summarized data; Table reports optimized for mobile - key columns are displayed prominently first; less critical columns may be hidden by default; as a general guideline, it is recommended to limit the number of columns to around 5 to 7 columns. 3. Choose the right metrics App admins must balance functionality and data with consumer expectations for the user experience - a major challenge in the dashboard design is strictly selecting only what matters. Don't just include data for the sake of it; instead, make sure that the metrics you include are actionable and provide insights that your audience can act on. Focus on metrics that will help your audience make better decisions, improve performance, or drive growth. The following steps can help you identify the right metrics: Involve end users and stakeholders in the process: Consult with key stakeholders and users who will use the dashboard or have an interest in its data. Their input will ensure that the metrics you are selecting are relevant. Define the Dashboard goals: Start by defining the goals and objectives of the dashboard. What is the purpose? What goals will the dashboard help users achieve? This will guide the selection of the right metrics. Identify strategic objectives: Identify the strategic objectives of your organization or business unit. Your metrics should align with these objectives. Break down the objectives into KPIs: KPIs are a quantifiable measure of performance over time for a specific objective and indicate how effectively an organization or team is achieving its objectives. Identify the KPIs that are most relevant for your users. Focus on actionable metrics: Identify metrics that provide actionable insights for your users. 4. Keep it Simple When it comes to designing mobile dashboards, less is often more. Avoid cluttering the dashboard with too much information or too many visualizations. A cluttered dashboard can be overwhelming and difficult to use. Instead, use simple, easy-to-understand charts and graphs that can be quickly interpreted. Some best practices that can help you simplify your content are: A mobile dashboard should have a clear visual hierarchy with the most important information presented prominently. Including too many reports will dilute the visual hierarchy and make it harder for users to quickly understand the most important insights. Group related information together and use a clear visual hierarchy to make it easy for users to understand the data. KPI reports and charts can be an effective way to present complex data in a way that is easy to understand. Choose the right type of visualization for the data you want to show, and keep it simple. Avoid adding any unnecessary text such as long detailed descriptions, when adding elements to the dashboard. For table reports add only the relevant columns in the report and place the key differentiating column such as a task or project name first. The more elements a table has, the more the user will have to scroll left and right and the harder it will be for them to make sense of all the data. Keep the number of reports limited to the most essential ones to ensure that users can quickly understand and act upon the information. As a general rule of thumb, it's recommended to keep the number of reports on a mobile dashboard to a manageable and meaningful level, typically ranging from 3 to 6 widgets. 5. Use color effectively Using color effectively in a mobile dashboard can help you highlight important information and differentiate outliers. This way you can create a mobile dashboard that is easy to use and visually appealing: Use color to convey meaning: Leverage the psychology of colors to convey meaning and help users interpret data. For example, use green to represent positive values, red for negative values, and yellow for warnings or alerts. Ensure that the color choices are intuitive and consistent throughout the dashboard. Highlight key data points: Use color to draw attention to important data points or trends. For example, you could use a different color for a high-priority task or to indicate a significant change in a metric. ”Using color is powerful, especially when it is used sparingly and reserved to identify the most important data points. Our brains are wired to find the most salient piece of information the fastest. Keep this in mind when designing your dashboards. Rather than adding color to all charts and widgets, consider keeping a consistent and neutral color palette throughout and then reserving one or two primary colors that catch the eye for the pieces of data or actions that matter most. Reserve warning colors such as reds and yellows for calling attention to crucial data points that need the user’s immediate attention at a particular time. Remember, when everything looks important, nothing is. Avoid overwhelming your users with color and instead use it sparingly to guide their eyes where it matters.” Kaydee Gilson, Interaction Designer, Quickbase Coming Soon While mobile dashboards are now generally available, we are still actively developing the feature. Here are the next improvements we’ll work on: Improved landscape support Filter enhancements: Displaying applied filters on the dashboard screen Supporting "Allow “contains” matches" and "Allow user to choose" settings for the text filters. QR code scanner in Search widget Optimized display of column properties within a table report widget We look forward to seeing the new dashboards you are building for your Quickbase applications! If you come across any issues or need assistance, please don't hesitate to reach out to us by submitting a technical support case detailing the problem you encountered. We want to hear your thoughts, ideas, and suggestions for the future of Quickbase. How can we further enhance usability for mobile dashboards? Is there anything we can do to make your experience even better? What features would you like to see? You can share your feedback by going to to My Apps page and clicking Give Feedback. We would also want to express our gratitude to each and every one of you who contributed with feedback and insights throughout the development process. Your valuable input and suggestions have been instrumental in shaping the very features you see today. To learn more about how we use your feedback, read our Feedback policy: Giving feedback
Groups
Mobile Qrew
For your mobile based use cases, there's no better space to discuss Quickbase mobile than in the Mobile Qrew.
