# TIP: When Shouldn't I Use Codename One

DevFeed: [TIP: When Shouldn't I Use Codename One](<https://devfeed.tech/articles/tip-when-shouldn-t-i-use-codename-one-19613.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/tip-when-shouldnt-i-use-codename-one/>)

Author: Shai Almog

Published: 2017-03-19T00:00:00Z

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [App](<https://devfeed.tech/topics/app.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [LineageOS](<https://devfeed.tech/topics/lineageos.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [apps](<https://devfeed.tech/tags/apps.md>), [developers](<https://devfeed.tech/tags/developers.md>), [framework](<https://devfeed.tech/tags/framework.md>)

## AI overview

This article explains when Codename One may be a poor fit: highly game-focused projects, device-specific utilities, and applications that require extensive native functionality. It presents Codename One as best suited to Java developers building mostly standard, portable apps, while noting that newer support for components over heavyweight widgets improves some mapping-app scenarios.

## Source excerpt

Bootcamp registration closed well and we are currently in the pre-course (more on that in another post) and already the Facebook group of the bootcamp is seeing decent activity. Being as busy as I am I thought I'd lift a question that was asked there to headline this post: "When shouldn't I use Codename One?". That's a great question. If Codename One was perfect for every use case it would probably suck. One of the biggest reasons for the complexity of the Android API is that it tries to answer every use case (device vendors, utility developers, game developers, app developers etc.).