Author: Michael Blood
What Happens When You Allow an App to Access Your Photos?
What Happens When You Allow an App to Access Your Photos?
When you grant an app permission to access your photos, you are enabling the app to perform specific tasks that require photo access. Many apps request this permission to enhance user functionality, such as editing images or sharing them on social media. This article explains what access you are granting, how it is typically used, and how you can manage it effectively.
What Does Granting Photo Access Allow an App to Do?
When you provide an app with access to your photos, it can:
-
Perform Core Functions
- Apps often require photo access to enable their primary features, such as editing, sharing, or backing up images.
-
Enhance User Experience
- Many apps use photos to offer personalized services, such as creating albums, applying filters, or generating photo-based recommendations.
-
Access Metadata for Features
- Photos may contain metadata (e.g., timestamps or location tags) that apps use for features like sorting or organizing images.
-
Store Photos in Cloud Services
- Apps may upload your photos to cloud storage for backup or synchronization across devices.
What Risks Should You Be Aware Of?
While most apps use photo access responsibly, it’s essential to understand potential concerns:
-
Data Usage Transparency
- Some apps might use photos or their metadata for purposes outlined in their privacy policy, such as analytics or feature development.
-
Scope of Access
- Certain apps request access to your entire photo library, even if they only need specific images. Be mindful of what permissions you’re granting.
-
Third-Party Sharing
- Apps may share non-sensitive data derived from your photos with third parties for analytics or advertising. Always check the app’s privacy policy.
How Can You Control Photo Access?
Modern devices offer several ways to manage and limit app access to your photos:
-
Grant Limited Access
- On many devices, you can choose to grant an app access only to specific photos or albums, ensuring your full library remains private.
-
Review App Permissions
- Regularly check the permissions an app has and adjust them through your device’s privacy or permissions settings.
-
Understand Privacy Policies
- Before granting access, read the app’s privacy policy to ensure you’re comfortable with how your photos might be used.
Can You Revoke Photo Access?
Yes, you can revoke an app’s permission to access your photos at any time. Here’s how:
- Open your device’s settings and navigate to the “Privacy” or “Permissions” section.
- Locate the specific app and find its photo permissions.
- Change the permission setting to “Off” or select specific photos for access.
Once revoked, the app can no longer access your photo library, though it may retain previously uploaded data if stored on their servers.
Key Takeaways
- Photo access allows apps to perform useful functions, but it’s important to understand the permissions you’re granting.
- Use device settings to limit access to specific photos and review permissions regularly.
- Always read the app’s privacy policy to ensure its use of your data aligns with your expectations.
By managing permissions wisely, you can enjoy the benefits of photo-based apps while maintaining control over your data.
Have questions about technology, apps, or data privacy? Contact us or visit our website for expert advice.
What is a Developer Account on the App Stores?
Disambiguating ‘Developer Accounts’ and the Role of a Software Agency or Developer
What is a ‘Developer Account’?
A developer account is the account required to publish apps on Google Play or Apple’s App Store. This account is owned by the person or business responsible for the app—usually the app’s owner—not by the person or agency that does the coding or technical work.
Do I need to be a developer to create a ‘Developer Account’?
No. You don’t need to know how to code to create a developer account. This account is for managing your app’s presence on the app stores, including publication, updates, and payment settings. The technical development can be handled by a software company or individual developers you hire.
Who should own the developer account?
The app owner (you or your business) should always own the developer account. Even if you hire a software company or a developer to build and manage your app, the account should stay under your control to manage ownership, payments, and app settings.
What’s the difference between a ‘developer account’ and a developer?
A ‘developer account’ is for managing the app’s store presence. A ‘developer’ refers to the person or team responsible for writing the code and building the app. You might hire a software company or agency to develop the app, but they do not own the account unless specifically transferred.
Can I give my developer access to my ‘developer account’?
Yes, both Google Play and Apple allow you to give a developer or software agency access without transferring ownership. You can assign specific roles with permissions tailored to the work they need to do, such as uploading app updates or managing listings.
What kind of access should I give my developer or software agency?
You should give your software agency or developer access to technical tasks such as uploading new app versions and managing the store listing. However, you should retain control over financial, legal, and account settings since they directly affect your ownership of the app.
What happens if I transfer my whole developer account to the developer or software company?
This is not recommended. If you transfer your account to the developer or software company, they gain control over the app’s ownership, payments, and store settings. To avoid complications, always maintain ownership of your developer account. Never share your credentials or password – instead use the tools in the App Store to invite your developers to work with your app.
How do I add a developer or software company to my Google Play Developer Account?
In the Google Play Console, you can add users from your hired software company or developers and assign them specific roles. This allows them to manage updates or other technical aspects without giving them access to sensitive areas like payments or legal settings.
How do I add a developer or software agency to my Apple Developer Account?
Through App Store Connect, you can invite your hired developers or software company and assign them roles such as ‘App Manager’ or ‘Developer.’ This allows them to manage app-related tasks while keeping account ownership in your hands.
Do Software Companies have their own Developer Account?
Yes, typically a software agency or the developer(or freelancer) will need their developer account to manage certain parts of your app’s store listing, particularly if they are handling multiple clients or apps. This account used by the software agency or the technical developer account is separate from the Developer Account, which remains under the control and ownership of the App’s owner
Do I need to take action even if I’ve hired a software agency?
Yes. Even with a software company or developers helping with the technical work, you will still need to manage certain aspects of your account. This can include legal updates, financial settings, and sometimes even specific actions related to the app’s publication that the hired company cannot perform on your behalf. Where possible the Software Agency is able to direct you to make changes in your account.
How do I, as an app owner, validate my developer account?
As the app owner, when the App Store asks you to validate your developer account – they are asking for you to confirm that your company is a real entity. (they are not asking for information on who your technical team is that is doing work on your application). Your Developer Account with the App Store represents your ownership and management of the app on the platform. To validate your account, ensure:
- The account is registered in your or your company’s name.
- The payment and legal details match your business information.
Remember, even though your software agency can assist with publishing and managing the listing, ownership and account details in your Developer Account (like agreeing to new terms or legal agreements) must be performed by you.
Marketing Firms in Boise, Idaho
For web and mobile application companies
Stoltz Marketing Group
Address: 101 S. Capitol Blvd., Suite 900, Boise, ID 83702
Phone Number: 208.388.0766
Website: https://www.stoltzgroup.com/
We help your business get to better through brand building, internal and external communication, and intangible magic.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
CLM Marketing & Advertising
Address: 588 W. Idaho Street, Suite 200, Boise, ID 83702
Phone Number: (208)342-2525
Website: https://clmnorthwest.com/
Compete and win. Again and again. You never stop #winning because we never stop learning.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
c308 Marketing
Address: 1404 W. Idaho Street, Suite 103 Boise, ID 83702
Phone Number: (208) 286-3380
Website: https://www.c308.com/
We build and maintain virtual assets that positively impact the real world.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
Bear Fox Marketing
Address: 6225 N. Meeker Place, Suite 250 Boise, Idaho 83713
Phone Number: (208) 820-1932
Website: https://bearfoxmarketing.com/
If you are a business-to-business company wanting to get the biggest bang for your marketing investments, we recommend you start with our ‘Rankings to Revenue’ SEO strategy.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
WebMarkets
Address: 999 W Main St 200 Boise, Idaho 83702
Phone Number: (208) 514-1634
Website: https://webmarketsonline.com/
Creating unique competitive advantages to sustain long term profits. Expert digital marketing strategies to improve brand awareness, lead generation, and growth.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
116 & West
Address: 805 W. Idaho St. Ste. 300, Boise, ID 83702
Phone Number: 208.472.2129
Website: https://116andwest.com/
New Clients Page: Contact Us
Your adventure awaits. Let’s go. We’re your travel buddy, tour guide, and pilot all rolled into one.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
BrandCraft
Address: 223 N 6th St Ste 50, Boise, ID 83702
Phone Number: (208) 343-1664
Website: https://brandcraft.com/
New Clients Page: Contact
Motivated to grow? Let’s work together. We provide creative services and marketing lead generation.
Services:
- SEO: Yes
- PPC Website Marketing: Yes
What is a user story?
User stories are a valuable tool for capturing software requirements in an easily understandable format. They help communicate the needs and expectations of users, allowing software developers to deliver targeted solutions. Here’s a description of how to format a user story and what should be included:
Format: A user story typically follows a simple template known as the “As a, I want, so that” format:
“As a {type of user}, I want {a feature or functionality} so that {a reason or benefit}.”
Components:
- Role/Persona: The user story begins by identifying the type of user or persona for whom the feature is intended. It provides context about the specific user or group of users who will benefit from the feature.
- Feature/Functionality: This part describes the desired feature or functionality in clear and concise terms. It should focus on what the user wants to accomplish or the problem they need to solve.
- Reason/Benefit: The reason or benefit section explains why the user wants the feature or functionality. It provides insight into the underlying motivation or desired outcome.
Example: As an online shopper, I want to view my order history so that I can track my previous purchases and quickly reorder items.
In this example, the user story identifies the persona (online shopper), the desired feature (view order history), and the reason/benefit (tracking previous purchases and reordering items).
Tips for Writing Effective User Stories:
- Keep it concise: User stories should be brief and focused. Avoid including technical details or implementation specifics. They should capture the “what” and “why,” leaving the “how” to the development team.
- Use a common language: User stories should be understandable to both technical and non-technical stakeholders. Avoid using jargon or technical terms that might confuse or exclude others.
- Collaborate and iterate: User stories are not set in stone. They should be a collaborative effort between stakeholders, product owners, and developers. Refine and iterate on user stories as you gain a deeper understanding of the user’s needs.
Using user stories can help transition to a more structured and effective way of describing software requirements.
Closing your AWS Account
There are a few reasons you may want to close your Amazon Web Services (AWS) Account.
Most of the time it is because you had some level of service with AWS – and now you no longer want these services.
Before you close your account, it may be a good idea to do a survey of all of the services to confirm that they are no longer needed.
The best way to see what you have , is to open the AWS Account – and go to the billing dashboard – and then look through your monthly bill. This helps you identify which services you have, you can use this list to open each of the sections in the AWS Console – select the correct region and review the service.
If you no longer need the service you can delete it.
If you are unsure whether you need it, contact your developer (contact-us)
If you are positive that you are ready to close your AWS Account, you can follow these instructions (these instructions are from this AWS Support Page)
- Sign in as the root user of the account that you want to close, using the email address and password that are associated with the account. If you sign in as an AWS Identity and Access Management (IAM) user or role, you can’t close an account.
- Open the Billing and Cost Management console at https://console.aws.amazon.com/billing/home#/.
- On the navigation bar in the upper-right corner, choose your account name (or alias), and then choose My Account.
- On the Account Settings page, scroll to the end of the page to the Close Account section. Read and ensure that you understand the text next to the check boxes. After you close an AWS account, you can no longer use it to access AWS services.
- Select the check boxes to accept the terms, and then choose Close Account.
- In the confirmation box, choose Close Account.
How to Protect Your Intellectual Property
In the beginning phases of developing an application, there are many things to keep in mind in order to protect an idea and the process through which the idea is implemented. One important first step is setting up possession of code. By setting this up at the beginning of the process, you can confirm ownership which will give you ultimate control over what happens during the project process.
What is Possession of Code?
Possession is defined as, “the state of having, owning, or controlling something.” This is no different within the world of software development. To avoid issues down the road, setting up access to the current code base is best practice. To understand this process, it can take a bit of training and research but it is well worth it to protect your project.
Time and time again, individuals run into the issue of obtaining their code from a previous developer when switching to a new freelancer, internal developer, or third party development firm. If you have possession of your code, you have access to invite new developers or revoke past developers if there comes a time when you no longer want a developer to make changes to your project.
NDA
Another way to protect your code is through an NDA (non-disclosure agreement). While ensuring that you have obtained possession of your code is important, an NDA is an equally important next step.
What is an NDA?
An NDA is a non-disclosure agreement. Its purpose is to create the legal framework that protects you and your application idea from being shared with anyone else. This article is a great resource that will tell you everything you need to know when it comes to non-disclosure
Do I need an NDA?
It is best practice to have an NDA in place when dealing with anything pertaining to intellectual property. An NDA ensures confidentiality and protection. Without an NDA, you are at risk of your idea being leaked.
Your ideas are an extension of your creativity and keeping them protected is of utmost importance. Ensuring possession and ownership and signing an NDA are two ways that you can ensure protection and have peace of mind and you dive into the world of software development.
Agile and Waterfall Methodologies in Software
Waterfall and Agile are well known approaches in software development. They are two unique methodologies providing different directions for various types of projects.
Agile Software Development – a type of development framework that expects the need for flexibility and applies a level of efficiency to the delivery of the finished product through consistent deliverables & communication.
Agile
- Frequent meetings
- Works well in conjunction with MVP
- High flexibility
- Short term deadlines – quick deliverables
- Collaboration between parties
- Reduced risk
- Cost effective
This graph shows the flow of an agile timeline. There is constantly a new deliverable and after each deliverable, there is communication between parties to review what is working and what needs to shift in order to continue improving the product. The time between each deliverable is typically two to four weeks, although it can be shorter. Due to consistent communication between parties, agile is more cost effective because the project can shift easily and frequently.
Waterfall Software Development – With a waterfall methodology, the scope and requirements of the project are defined upfront. The client receives large batch deliverables at the end of each development phase.
Waterfall
- Goals set from the beginning
- Requirements are clear and fixed
- Infrequent meetings
- Complete deliverables before moving onto next phase
- Low flexibility
- Higher cost
Looking at the graph to the right, you’ll see that Waterfall project timelines are longer than Agile. While working on a Waterfall project, there is often less communication as the requirements are less flexible in the beginning phases of the project. Due to this, there is more risk associated because of less flexibility to change the product. In Waterfall, each stage of the project needs to be completed before moving on to the next step.
Agile is more commonly used today because of the flexibility, cost efficiency, and reduced risk associated with this methodology.
Onshore vs. Offshore Development
The Difference Between Onshore & Offshore Development
When deciding to develop a new app, there are many choices to be made. A large decision is deciding where your app will be developed. This article will go over some of the nuances of onshore vs. offshore development. By the end of this segment, you should have a better understanding of which direction would be best suited for you and your company.
Offshore: Offshore development is hiring out your development needs to an individual or a company that does not reside in your same country.
Onshore: Onshore development is hiring out your development needs to an individual or a company that resides within the same country your business is located.
Onshore Development
In Person Connection
Meeting in person can cultivate relationships between two companies or individuals that are harder to cultivate online. The ability to meet face to face can help clearly communicate the needs of your business.
Clear Communication
Being able to clearly communicate can make the difference between project successes and failure.
Cost
Something to be aware of when dealing with onshore companies, is a term called “backdoor offshoring”. This is essentially when you hire a team in your country, and they hire out the work to an offshore freelancer or company. You can ask to meet with your developer in person and know exactly who is going to be assigned to your project and be in tune with the entirety of the project.
Offshore Development
Cost
Typically, offshore companies offer their services at a lower cost than those within the United States. Offshore companies have more employees that are ready and willing to work which in turn creates a faster turnaround time on projects. Many companies in the US are very popular and busy which may cause a delay in project startup. Many offshore companies have workers that are ready to work as soon as the next project comes up. Because of these factors, turnaround times can be much faster offshore than onshore. Although, this can vary between projects and their specific needs.
Availability
The world is vast and so is the talent pool outside of where you live. Offshoring means that you have access to many brilliant and talented individuals worldwide. Offshoring can be a great way to access developers with a wide range of skills.
Time Zones
One issue with offshore development is the difference in time zones. Very practically speaking, it can make it very difficult to find time to connect when questions arise, or you just simply need to get in touch with your developer. On the other hand, different time zones can be positive for founders that have a day job and are working on their software idea at night. An offset schedule can be a project advantage.
Communication
When working with individuals in other countries, it is safe to assume that English will not be their first language. Even if spoken with proficiency, there can still be unique challenges that present themselves.
No matter if you choose onshore or offshore development, it is wise that you know where your code is being stored and be sure to have access to it. If you choose the offshore route, looking up the law pertaining to code ownership and possession in that country is beneficial.
Does Your Business Need a Mobile App?
Mobile apps have increasingly become an integral part of the digital landscape. For many businesses, they are an indispensable asset and for others, the question still remains: “Should my business be utilizing a mobile app?” This article discusses a few things to consider before jumping into the world of app development and will give a better understanding of things to consider when deciding if an application is necessary for your business.
- Your audience
- The value of your app
- Your competitors
- Long term app support
- Current website
Your Audience
Consider who your audience and ideal customers are. Here is a great article from HubSpot that breaks down exactly how to figure out who your target audience is.
The Value of Your Mobile App
An app should add inherent value to both a business and its customers. Here are a few ways an app can add value:
- New Revenue
- Selling goods and services
- Process payments, track orders, and manage inventory
- Sell a new product
- Offer follow-up goods
- Build Relationships
- Connect to your customers through push notifications about new products, services, special offers, and events.
- Collect customer feedback and build relationships
- Better customer service
- Reduce Expenses
- Can help save time
- Answer questions
- Automate processes
Long Term App Support
Apps require maintenance of follow-up features and updates. Once an app is developed, there may be bug fixes to keep up with along with improving basic functionality of the app as time goes on. Consider the time commitment and cost associated with keeping an app updated.
Current Website
When deciding if you need a mobile app, consider whether you are able to accomplish what you need by adding small changes to your website. A well optimized website can provide many of the same functions as a mobile application. If you already have a website, think about the additional benefits a mobile app will provide and ask yourself the question, “Should my business be utilizing a mobile app?”
All in all, developing an app can be a very positive addition to your business when it adds value and helps you connect with your consumers. If you are interested in looking at the next steps, talking with a professional app development company is a great place to start in order to assess your business needs and determine if an app is right for you.
Your software developer is quitting: now what?
So the truth is out! The developer that knows everything about your project is not going to be around to finish it.
You may have cursed a bit under your breath and tried to quickly maneuver to keep them on board – however, you are reading this article because you now know it is up to you to confirm you have possession of your project. It is up to you to take control of the software so you can direct it and secure the future of it. Here is how you do it.
- First of all, don’t freak out, a calm and professional response to the news is the best way to encourage a smooth transfer of all project assets and assistance identifying ‘forgotten’ assets.
- Second, create a shared ‘offboarding’ document and / or folder where you can coordinate the process of collecting information about your project.
- Request information from your developer – Let them know that the most important part of their offboarding is to help you understand the project – so you can help the next person take it over.
- Confirm that you have the information you are looking for – it can be tempting to just assume you have it, but by taking the time to verify it, you will identify things that are missed and save headaches later.
Don’t Freak Out
Why is this a step? Because we have found that some of our past clients needed this reminder. Too often we hear of hasty hire or poorly orchestrated offboarding while the manager spends time realizing that the project was not going to be done the way they had previously assumed. Often, the decision will be made to try to ‘get it all done’ in the next two weeks. They drive the developer to spend every moment of their last two weeks getting writing code. This should not be the first priority! The first priority should be to ensure that the possession of the project is fully in the control of your company and the company can continue development of the project in the future.
One of the reasons that we see managers ‘Freak Out’ at this stage is because they have not previously recognized that they should have set their project up in a way that made sure that the project was already in the possession of the company. Ultimately, any project that was going to be owned by your company had to be in company possession anyway, right? So this is a good thing – we are going through the process of putting your project in your control – so your project will survive this ‘developer change’ and any ‘developer changes’ in the future.
Your systematic and practical approach to offboarding your current developer will result in a strong understanding of your project and an improved ability to select the ideal replacement when you restart your project. The possession you end up with will give you the confidence to restart and finish the project in the future.
Create a shared offboarding folder
Create a shared folder where you can work with your developer over the next days and weeks to collect information about your projects. You will want to create the area yourself and setup the structure to have the information you want.
I use Google Documents because the ability to collaborate is better than any other tool, but what is important is that it works for you and your developer and you are able to see each other’s work. Create several documents and give your developer access so they can make changes where you can see them. I recommend that you create the following documents at a minimum – be sure that each of the folders has permissions which allow your developer to make changes:
- Document: Offboarding Checklist / Instructions
- Document: Offboard TeamMemberName – MM/DD/YYYY – Projects / Assets / Credentials
- Folder: Project Asset Uploads
- Folder: Recordings
I have created an example (with some sample entries)
Request the following from your developer:
- Fill out the offboarding document with credentials and links to each project and project source
- List all code repositories and transfer ownership to me
- Provide me with access to your workstation
- Record a video of you working through opening, making a simple development change and then deploying
- Record a video showing the workstation and development environment and configuration
- Record a video explaining for each project what your next steps and recommendations would be
Confirm possession and control of your code
- Understand and confirm your understanding of all project assets
- Test credentials and confirm owner level access to all project assets
- Confirm project source links and documentation, add notes and request updates
- Review recordings and request additional recordings.
- Time permitting: Request a review / audit of code / transfer confirmation from a third party