FABs

Floating Action Buttons (FABs) are an important part of modern app design. They are often used to provide quick access to primary actions within an app. In this blog post, we’ll walk through the steps to implement a FAB in an Android app.

Step 1: Add the Design Support Library To use the FAB in your app, you need to add the Design Support Library to your project. To do this, add the following code to your app’s build.gradle file:

dependencies {
implementation ‘com.android.support:design:28.0.0’
}

Step 2: Add the FAB to Your Layout To add the FAB to your layout, add the following code to your XML layout file:

<android.support.design.widget.FloatingActionButton android:id=”@+id/fab” android:layout_width=”wrap_content” android:layout_height=”wrap_content” android:layout_gravity=”bottom|end” android:src=”@drawable/ic_add” app:elevation=”6dp” app:fabSize=”normal” />

This code creates a new FAB with an ID of fab. The android:layout_gravity attribute positions the FAB in the bottom-right corner of the screen. The android:src attribute sets the icon for the FAB. The app:elevation attribute controls the shadow depth of the FAB, while the app:fabSize attribute sets the size of the FAB.

Step 3: Handle FAB Clicks To handle clicks on the FAB, you need to add a OnClickListener to the FAB. Here’s an example code:

FloatingActionButton fab = findViewById(R.id.fab);
fab.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
// Handle FAB click
}
});

In this code, we get a reference to the FAB using its ID and then add a new OnClickListener. When the FAB is clicked, the code inside the onClick method will be executed.

Step 4: Customize the FAB You can customize the FAB to match your app’s design. For example, you can change the color of the FAB using the app:backgroundTint attribute. You can also change the size of the FAB using the app:fabSize attribute.

<android.support.design.widget.FloatingActionButton android:id=”@+id/fab” android:layout_width=”wrap_content” android:layout_height=”wrap_content” android:layout_gravity=”bottom|end” android:src=”@drawable/ic_add” app:elevation=”6dp” app:fabSize=”normal” app:backgroundTint=”@color/colorPrimary” />

In this code, we set the background color of the FAB to the app’s primary color using the app:backgroundTint attribute.

In this blog post, we’ve shown you how to implement a Floating Action Button (FAB) in an Android app. The FAB is an important part of modern app design and can help provide quick access to primary actions within an app. By following these steps, you can add a FAB to your app and customize it to match your app’s design.

Preparing release of Progress Reporting Management app

General

o Introduction of “Sync on Sign out” if an app user is being signed out with unsynced data.

o Visual updates and introduction of new colour schemes across app

Measure

o Introduction of Horizontal scrolling in Measure sheets. (user based permission, can be set based on app user preference in app user setup)

o Introduction of “Company Scope” on Column setup to allow narrowing of companies from drop down lists eg on Cable schedules

Allocation Module

o User based permission to allow exceed clocked values (NAV app user setup)

o Introduction of Data limits for types of resource eg Operatives, 24 and Company, 5000 per day.

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function.

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

o The “Company Scope” of Measure columns list will obey the same setup, ie help narrow the list of systems under a resource

o Introduction of cross device sync, all app users can see previous entries from different app users for same Resource

o Introduction of complex entries, app user can add additional entries for same Resource & system, but with different WBS and System/Asset allocations

o Clock value for current day now comes into allocation view, app user can exceed this value, but not for previous days

Diary

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

Testing

o Bug fix on rejected test sheet where user could not see rejected sheet on device from which previous test sheet was completed, but could see from different device

Snags

o On WBS selection, Introduction of Tree like function to enable user quickly find value. User can search this also

o On System/Asset selection, the system list has a search function aswell as select from list function

o Both WBS and System Asset also have a feature that shows last selected entry on top of list for repetitive data entry tasks

o Changes to Mandatory fields in snag card inline with QA dept requirements

o Draft Snags (incomplete mandatory fields) will not transfer to NAV and assigned app users

o Search bar now can handle multiple search requests, so for example you can search a Discipline, an Assigned Company and System/Asset by placing a space between key words eg ELEC YR

o New Power BI visual to allow BI users interact with project layouts using assigned WBS for snag locations

Gym app . Part 2

In the previous blog post, we started building a mobile app for a gym using ASP.NET Core web app as a storage platform. In this post, we will continue building on that project and explore how we can add more features and functionality to the mobile app.

Step 1: User Authentication and Authorization

One of the most important features of any mobile app is user authentication and authorization. This ensures that only authorized users have access to the app and its features, and that sensitive user data is kept secure.

To implement user authentication and authorization in our mobile app, we can use the ASP.NET Core Identity framework. This framework provides a set of APIs and services that allow us to manage user accounts, roles, and permissions.

Step 2: Enhanced User Interface

The user interface (UI) is a critical component of any mobile app. It should be intuitive, easy to use, and visually appealing.

To enhance the UI of our gym app, we can add more graphical elements, such as images and icons, and use CSS styles to customize the appearance of the app. We can also use JavaScript to add interactive elements, such as dropdown menus, pop-ups, and animations.

Step 3: Additional Functionality

To make our gym app more useful and engaging for users, we can add additional functionality, such as:

  1. Push Notifications: We can use push notifications to send alerts and reminders to users, such as when a class is starting or when they have missed a workout.
  2. Social Sharing: We can integrate social sharing features into the app, allowing users to share their workout achievements and progress with friends and followers on social media.
  3. Gamification: We can add gamification elements to the app, such as badges, points, and leaderboards, to encourage users to stay motivated and engaged.
  4. Payment Integration: We can integrate payment systems into the app, allowing users to purchase gym memberships, personal training sessions, and other services directly from the app.

Step 4: Testing and Deployment

Once we have added new features and functionality to the app, we need to thoroughly test it to ensure that it is working correctly and free from bugs and errors.

We can use automated testing tools, such as unit tests and integration tests, to test the app’s functionality and performance. We can also use user testing to gather feedback and insights from real users and make improvements based on their feedback.

Once the app has been thoroughly tested and optimized, we can deploy it to production, making it available to users on app stores and other distribution channels.

Continuing to build on our gym app using ASP.NET Core web app as a storage platform, we can add more features and functionality to make it more useful and engaging for users. By implementing user authentication and authorization, enhancing the user interface, and adding additional functionality, such as push notifications, social sharing, gamification, and payment integration, we can create a powerful and versatile mobile app that meets the needs of gym-goers and fitness enthusiasts.

Building a mobile application for gym membership.

Building a mobile application for gym membership can be an effective way to engage your members, simplify the management of their memberships, and improve their overall fitness experience. Here’s a step-by-step guide on how to build a mobile application for your gym:

  1. Define the purpose and features of the app: Before you start building the app, you need to define the purpose and features of the app. Think about what your members would benefit most from having in a mobile app. Some features you may want to consider include membership management, workout tracking, personalized recommendations, social features, and class schedules.
  2. Research and choose a mobile app development platform: To build your mobile app, you’ll need to select a mobile app development platform. There are many mobile app development platforms available, including React Native, Flutter, and Ionic. Research each platform and determine which one is best suited for your gym’s needs.
  3. Design the user interface and experience (UI/UX): Next, you need to design the user interface and experience of your mobile app. A user-friendly and visually appealing design can enhance the user experience and encourage users to engage with the app more frequently. Consider hiring a UI/UX designer to help you create a great app design.
  4. Develop the app: Once you’ve defined the purpose and features of your app, chosen a mobile app development platform, and designed the UI/UX, it’s time to start developing the app. This process typically involves coding, testing, and debugging the app. If you’re not an experienced app developer, consider hiring a developer or outsourcing the development to a third-party agency.
  5. Test the app: After the app has been developed, it’s important to test it thoroughly to ensure it’s functioning properly and meets the needs of your members. Testing should include functional testing, performance testing, and usability testing. You may also want to conduct beta testing with a small group of users to gather feedback and identify any issues.
  6. Launch the app: Once the app has been developed and tested, it’s time to launch the app. Make sure to promote the app through your gym’s marketing channels, such as email marketing and social media.
  7. Continuously update and improve the app: Building a mobile app for your gym is an ongoing process. As you receive feedback from users and gather insights into their behavior, you should continuously update and improve the app to better meet their needs and enhance their experience.

In conclusion, building a mobile application for gym membership requires careful planning, design, and development. By defining the purpose and features of the app, choosing a mobile app development platform, designing a great UI/UX, developing and testing the app, launching it, and continuously updating and improving it, you can create a valuable tool that engages your members and enhances their fitness experience.